Business rules in Blackpearl K2 (rules)

In a K2 process system, any one of the execution nodes in the process (one node can contain multiple events) can contain client events, server-side events, and subprocesses (Ipc,inter process Communication) events, or other events. Typically, we need to include a lot of business logic in the process node, such as who is the performer of the process node. Which prerequisites must be satisfied before the performer initiates the process node task, and so on. A process node is a key element in a process in which a task performer approves, enters, or extracts data from a process node.
To implement a variety of complex business logic, K2 provides the following business rules:
1. Preceding rule (predecessor rules)
Preceding rule is a logical expression in which a process node can begin execution when the expression is true. In other words: If the condition is true, the process task can be generated. K2 provides 3 logical identifiers, such as And,or and XOR, that enable logical combinations.

2. Start rule (start rules)
Start rule is a time principle that represents when a process task begins. For example, you can wait 2 hours to start the process task after the process is initiated, or wait 2 hours to start the process task when a process variable is true.

3. Destination rule (Executor rules)
Used to specify who will perform the task. By default, K2 's user information comes from active Directory, so it is easy to submit tasks to the user's manager. If you have more than one possible task performer, we can first add all possible actors to destination rule and then set the criteria for each rule, such as when a is true and send it to originator manager, when B is true, Send to Generalmanager, or you can define a destination queue and assign the destination queue directly to the task performer.

4. Escalation rule (expired rules)
If you want certain tasks to be completed within a certain amount of time, for example, 8 hours, if more than 8 hours of work is still not performed, we must perform certain actions (such as forcing the task to expire, or force the task to expire and flow the process to a certain process node, etc.), in which case We can then define the expiration rules for the task. Expiration rules are used to specify when and how to perform such an operation.

5. Succeeding rule (post rules)
Succeeding rule is a logical expression that can be completed by a process node when it is true. In other words: what happens when a process node can end. For example: There is an approval task, need to be issued to 5 department managers for approval, we hope: as long as one of them does not agree, the process will take the next step (after the operation of the veto); At least 3 department managers agree that the process will flow to the next step (agreed upon operation). This is K2 a very good rule, because each department manager's approval opinions are kept in their respective slot, the variable values in the process are not overwritten with each other, so it is easy to query each manager's approval opinions without having to define variables for each manager. K2 provides 3 logical identifiers, such as And,or and XOR, that enable logical combinations.