Workflow model analysis - Multi-instance model
The so-called multi-instance model refers to the same activity in the process, and there is a plurality of instances.
1) After asynchronous multiple instances, these instances are each polite and does not affect each other. Since it does not affect each other, the number of instances generated by asynchronous multi-instance models is arbitrary. When it comes to the number of instances that can be generated, we are said to be synchronized, just below three points. 2) Determine the simplicity of the number of instances to determine the number of instances, that is, in the JAWE, you can define the number of instances that can be generated. 3) The number of runtime decision instance is dynamically determined by the number of instances that can be generated during the process run. 4) The thickness of any example is: an activity, you can generate an instance.
The general standards only support the first two models, including XPDL standards.
Workflow model analysis --- polymeric model
1) M I-polymer only When the M item is over, the A activity enabled2) n item aggregation 1 <= n <= m, in fact, a discriminator, after the N item is completed, the condition is satisfied, A activity Enabled3) Single aggregate Any event end, A activities enabled
There is a problem with N items and individual polymeric: A activity can be enabled? According to the answer to this question, the aggregation model can continue to classify.
Basically all of the workflow standards support M item aggregation and single polymerization, and N items are aggregated, and each standard support is different. The XPDL standard does not support N item polymerization.
Workflow model analysis --- Dissive model
In the divergence model, after the event A, M (2 <= m <= 9999999999 ..) a direct successive optional activity
1) M term divergence
Laid M IMA activities at the same time, official name is Parallel Split
2) 1 dispersion
Behind only one event enabled, official name is Exclusive Choice
3) N items divergent
There may be N items in the back, which is enabled, (1 <= n <= m), formal name is Multiple Choice
At present, the general workflow products and XPDL standards only support the first two, and the N items are not strong, but there are already direct N items that support N items such as MQSeries / Workflow.
