WWF <Article 3>

WWF classifies workflows into two categories:

• Human-oriented: When a workflow is running, the user's operations on external applications affect the workflow's business flow.
• For system: application control process.

Workflows and applications can exist independently. Therefore, data interaction between them must be implemented through interfaces. Data Interaction Models between workflows, applications, and interfaces are as follows:

　　

The workflow instance exists in the runtime container when the workflow is running, but the interface project and application used for data interaction do not exist in the runtime container of the workflow. WWF provides "system. workflow. Activities. externaldataexchangeservice" for data interaction. You can load an external application to the "externaldataexchangeservice" service, and then load the service to the runtime container when the workflow is running, then, the workflow instance and the external application are both in the same container, so that data interaction can be performed.

　　

I. handleexternalevent
Handleexternalevent is an event-type activity. The Calling relationships between callexternalevent and handleexternalevent activities and applications are as follows:

　　

Handleexternalevent registers an application to the container runtime when the workflow is running through an "externaldataexchangeservice" service, an interface project that inherits "externaldataexchange" is used to call a workflow by an external application. However, the handleexternalevent activity defines Event Events in the interface rather than common functions or methods. After the workflow is executed to the handleexternalevent activity, it enters the "idle" state.

 

WWF <Article 3>