You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Whilst the filter feature in ost 1.xx is useful, it's still quite limited. It would be great to be able to have a more workflow oriented experience automating the flow of a ticket from inception all the way to closure. Ideally ost should expose relevant parts of its entity and event model to the workflow engine thus making it possible to create a rich experience for users and agents. The icing on the cake would be if the WF engine exposed an API that made it possible to insert custom workflow tasks (preferably implemented as plugins) into the flow.
In any case we're really looking forward to see how the new 2.0 develops!
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hi,
Whilst the filter feature in ost 1.xx is useful, it's still quite limited. It would be great to be able to have a more workflow oriented experience automating the flow of a ticket from inception all the way to closure. Ideally ost should expose relevant parts of its entity and event model to the workflow engine thus making it possible to create a rich experience for users and agents. The icing on the cake would be if the WF engine exposed an API that made it possible to insert custom workflow tasks (preferably implemented as plugins) into the flow.
In any case we're really looking forward to see how the new 2.0 develops!
Cheers,
Peter
Beta Was this translation helpful? Give feedback.
All reactions