Complex Human tasks are cumbersome using simple forms
Attaching business’ documents result to workflow’s tasks is OK and makes sense in many process scenarios. It is common also to integrate legacy applications exposing their functionality through a webservices layer or make the process workflow listen to a database event.
What do you think if you have some users having their task list embeded in their custom daily app which redirect the task execution links to a proper app complex ui view? Once the user is done, she hits a complete task button to inform the app to bring the scenario result to the owner process apart from the old custom application’s behaviour.
Advantages (from user’s perspective):
- Transparent workflow integration for the business user. She just use the same old application.
- Application task’s user scenarios driven by external workflow process execution.
- Complex business tasks which can not be done using a simple form can be done using the proper application ui devices.
- … do you see another?
Dissaventages ( or difficulties from IT perspective):
- Task list integration.
- Necessity to develop Application components for workflow integration.
- Filter tasks in order to present just those available to the current application.
- There is no current Designer tooling support so it is needed a workaround to change task’s execution links.
- … many more you are thinking about … for instance?
Here you can see part of a complex task which involve preparing a product list for a contract attachment. Product Selection from an enterprise portfolio arranged by categories.
Best Regards.
