Humanworkflows in BPM - Post 5
In continuation with my earlier post, the second type of Human workflow pattern in Task execution is termed as Asynchronous task.
* Asynchronous task with inbox: A human participant interacts with a long running business process, where the subsequent task might be time consuming or require another human participant involvement e.g. any approval process. In this mode of interaction a human participant executes a task and subsequently gets the next set of tasks via an inbox/ task list.
While modeling a business process it should be possible to define task flow mode for individual human activities i.e. if the subsequent UI should be provisioned immediately or will the UI be provisioned at some later point of time in Inbox. Also If a Task is initially declared as Synchronous however a Human participant does not work on it immediately it should be moved to a Inbox (i.e. treated a asynchronous task after some given duration.)
Asynchronous task flows are used frequently to handle most of real life human workflows involving multiple human users, long running process and intermediate steps which are run as scheduled tasks or batch tasks.