Basic Operation
From the viewpoint of the user, the task workflow appears as a seamless flow of task interfaces in My webMethods. As the user completes each task in the workflow, the next logical interface appears, thus eliminating the need for the user to locate each new task in My Inbox and then open it manually.
Operationally, this behavior is implemented with the following:
A process component that waits for the next task of the business process (or for completion of the workflow). Upon notification, the waiting component then executes a user interface action, such as open the next task in the workflow, or transition to the next post-workflow activity in the process. The waiting component uses a Java API to wait for the next action to occur.
A process step that notifies the waiting component. Within the workflow, the next workflow task uses a Java API to notify the waiting step. When the final step in the workflow completes, it waits for notification from a following step that invokes an
Integration Server flow service to provide the notification. In both cases, the waiting step can then transition to the next activity.
Related Topics