Workflow mode description-Process Control Mode (1) -- sequence

1. Theoretical Model

This theoretical model is very simple, just a unit of work is completed, followed by the unconditional execution of the next unit of work. Every workflow system directly implements this mode, which is an important cornerstone for workflow operation.

2. Application

This mode is clear, but it is most widely used.What is interesting is that many different forms of branches can be degraded into sequential models in business practices.. If a job unit A can generate B and C concurrency later, it can be converted into A, B, and C sequential execution, and the merge is also the case.

However, it is clear that the Branch Mode degrades to the sequential mode, which is less efficient. There are two main situations I have encountered: first, the level of the process designer may be insufficient, and the process designer will not turn when thinking straight lines; secondly, the workflow system cannot implement complicated branches, or the implementation cost is very high.

The result of this operation is that the customer has to change its original business process, and such a bounce change usually slows down the business process. However, the developer easily avoids some difficult implementations, and when the system implementation encounters setbacks, the responsibility can be easily transferred to the failure of customer process reengineering.

Therefore, when you are the owner, if the owner needs to "flat" the existing processes with several branches on the premise that the owner advertises standardization ", if the result seems to be in the order mode, it is likely to be compromised by the other party.