SHARK workflow implementation and comparison of WMFC & OMG specifications
----- Part 5: Installation of Workflow
Keywords: Shark workflow WMFC OMG specification
Learn so many open source frameworks, ready to achieve one. Don't start, let's talk about how to use XPDL to describe the information you need to include and how to instantiate a process.
There is a piece of package-business_example in Shark. Where Customer Service - Request for Partial Shipment is described as follows:
Processheader>
Datatype>
Formalparameter>
Datatype>
Formalparameter>
Datatype>
Formalparameter>
Datatype>
Datatype>
Formalparameter>
Formalparameters>
ImpLementation>
Startmode>
Finishmode>
ExtendedAttributes>
Activity>
ImpLementation>
Startmode>
Finishmode>
ExtendedAttributes>
Activity>
Activities>
ExtendedAttributes>
Transition>
Transitions>
WorkflowProcess>
WorkflowProcess>
Explain as follows:
This process has only two activities:
1,
Ask the user, you need to dispensed
2,
Tell customers to sell
Transfer of two activities:
The above description is just a basic XPDL implementation, and the information required in the real world is insufficient.
such as:
1. Once the user A is logged in, it is necessary to know those activities related to User A have started and prompting users a to operate this activity. This requires information including the participant in the instantiated process.
2. The above description is only information containing the workflow itself. It is clear that the specific finals of the workflow task must finally implement the business process, then in the instantiated workflow data, the minimum should be included. Can find connection data for this service.
3, the status of the workflow specific state business status should be saved in the instantiated process.
As can be seen from the above comparison, the workflow engine should be different on how to instantiate work information and business information, because this is not the content in the WMFC specification.
to be continued
Tian Chunfeng
Accesine@163.com