Workflow mode description-Process Control Mode (8) -- Multi-Merge

1. Theoretical Model

This pattern is actually a homogeneous situation of the same branch

Note: When branch a and branch B arrive at the merged node, it does not merge, but continues the same subsequent branch. For example, if a completes the task first, it triggers C1 (we call it C1 When C is triggered for the first time). After B completes, call C2 again (the second C is called C2 ). So it actually triggers C twice. According to the theoretical model, when both A and B are completed in a timely manner, two C s are still triggered, but in reality there is no such situation, and there is always a sequence of computer processing.

2. homogeneous

In fact, this mode can be understood:

This mode is only a simple form of business. In a general workflow system, different branches use the same unit of work.Code.

3. Application

All the details of business operations are the same. This mode is undoubtedly a good simplification method. However, note that the xpdl standard can directly support this mode, but it cannot be supported by BPEL. However, as a service-oriented approach, you can use the configuration method to achieve this effect (the same entry is used in the configuration, or a proxy is used, the two activities are directed to the same business code), but this expression cannot be found in the flowchart.