SOA Integration - Implementing the Workflow Business Pattern

In this scenario, additional user interaction is added to the integration process scenario. As a result, the integration process is no longer fully automated. It is interrupted at a specific point by interaction with the end user, for example, to obtain confirmation for a certain procedure. This scenario is shown in the image below.

Trigger:

An application places a message in the queue.

Primary flow:

1. The message is removed from the queue by the JMS adapter and a new instance of the integration process is started.
   .
2. The user interaction takes place through the asynchronous integration of a task service. It creates a new task, which is displayed in the user’s task list.
   .
   
   Ads
   
   
   ..
3. As soon as the user has completed the task, the task service returns a callback to the relevant instance of the integration process, and by that, informs the process of the user’s decision.
   .
4. The integration process responds to the decision and executes the remaining steps.