F2 the intersection, split, and detach calculation rules for a workflow engine contributor type member

Calculation Description: The calculation rule refers to the calculation between the other "participant type members", the rule calculation must be solved in case the handler is not empty, and the individual "contributor type members" are executed in ordinal order.

Calculation algorithm: Set (lowest weight), intersection (weight), split (highest-weighted, and exclusive)

Rule highlights:

1. Perform calculation results in ordinal order
2. Participants are not empty to participate in calculation between members
3. Weight

Example explanation

For example, there are a total of three contributor type members: SQL contributor, specified user participant, role contributor.

So let's use the example to explain the main points in the rules:

1. 1. perform calculation results in ordinal order

There is an ordinal number in front of the participant: 1 is a SQL contributor. 2 is the specified user participant. 3 is a role participant. Then the execution of the engine will execute this order to solve the respective handlers.

The order can be adjusted by the upper and lower head of the right.

Example if:

1SQL participants solved ABC

2 The specified user participant is a BD

3 role participants are EFG

Condition hypothesis

hypothetical Condition One : 1 is a set, 2 intersection, 3 and set

So the execution process is this:

Engine Execution 1 The result must be ABC, because 1 is the first participant, and then put ABC into a temporary result set we call temp, because 1 is a set, then continue to execute (note as long as not all of the types of disassembly continue to execute), 2 is BD, then BD intersect in TEM, execute BD∩ Temp=b, put B into temp=b, then continue to execute 3EFG, with EFG and set in temp, execute EFG∪TEMP=BEFG into the temporary result set TEMP=BEFG, because there is no, so the end result is: BEFG.

hypothetical Condition Two : 1 is a set, 2 is split, 3 intersection

So the execution process is this:

The engine executes 1 result temp=abc, because 1 is the set so continue execution (note as long as the type is not the same as all continue to execute), 2 is the BD, then the BD is split in the temp, the new result is BD, because 2 is the highest inter-split weight, so the next 3 no longer perform to calculate, The final BD is put into the temp=bd, so the end result is: BD

Setting conditions 2 What would be the implementation of the man who was found to be empty?

1SQL participants solved ABC

2 Specifies that the user participant is empty

3 role participants are EFG

According to the above situation two, the result of execution is 1 temp=abc, the first execution 2 because of the empty (although the weight is an inter-disassembly but no processing person so do not participate in the calculation), so 2 do not participate in the calculation, continue to perform 3EFG intersect at temp, the result is empty temp= empty

1. 2. The participant type solves the handler without being empty to participate in the calculation

This refers to the type of participant who has been asked to be a handler who cannot be empty to participate.

For example: 1 of SQL participants, if the solved handler is empty, then this SQL participant does not participate in the intersection between the members, and set, the computation of the disassembly.

1. 3. Weights

Union (lowest weight) Merge with Temp

The intersection (in weights) with the same handler as Temp

The split (highest-weighted and exclusive) replaces temp as a new result, and all subsequent participants are ignored.

F2 the intersection, split, and detach calculation rules for a workflow engine contributor type member