Application Scenario 1: a task is completed by a and B (or more people). After the task starts, the two can process the task at any time. Only one person can process the task, this is the end of the process.
Application Scenario 2: a task is completed by a and B (or more people). After the task starts, the two can process the task at any time. If a processes the task first, B cannot see this task at this time, and vice versa. The task can be completed by only one person.
Scenario 3: a task is completed by a and B (or more people). After the task starts, the two can process the task at any time. If a processes the task first, B cannot see this task at this time, and vice versa. If a finds that the task cannot be processed by itself, it should be handled by B, then release the task. At this time, B can see that the task is processed, and vice versa.
There are also many derivative scenarios. For example, in scenario 1, an exclusive function can be added when processing a task, so that the task can be exclusive when necessary, and others cannot see it. Multiple users can process tasks at the same time. There are multiple implementation methods: instantiate multiple tasks and one instance for each user. You can also instantiate only one task and use multiple slots (which can be understood by the concept of a swimming track). Each person has a swimming track and does not interfere with each other. For example, in a two-person swimming competition, you can arrange two swimming pools with the same length (multiple instantiation of a task) and send an order to start swimming. Who wins first, you can also divide two swimming paths in a swimming pool, one swimming lane for each person, and send an order to start swimming. The difference is that the resources used are different.
Scenario 4: a task is completed by a and B. After the task starts, the two can process the task at the same time. When a last night, you must wait for B to finish the next task, and vice versa. This is the end only when both parties have completed the process.
Tasks that can be processed by multiple users:
- If there is a competition between these people (only one person can process at a time), options of K2 destination rule must be set to plan just once and slot is 1. That is to say, the task is only instantiated once. In other words, there is only one swimming pool, one swimming pool, and the first person who jumps down will come to the game. When one person jumps down and occupies the swimming pool, no one else can jump. If a person who jumps down first gets cramps, he needs to make a statement (realse). other talents can compete for this swimming pool.
- If there is no competition between multiple people, K2 destination rule can be set in a variety of ways: Options of K2 destination rule can be set to plan just once, and slot can be set to create slot for each destination. You can also set options of K2 destination rule to all at once, and slot to be set at will. Destination rule's options is set to plan just once, that is, it is solved by multiple swimming channels in a swimming pool, the options of K2 destination rule is set to all at once, that is, multiple swimming pools are used to solve the problem. It doesn't matter how many swimming pools each swimming pool has.
For more information about K2 bpm, visit www.k2software.cn.
Review the process from the perspective of K2 -- exclusive and release of tasks