Execution order

In SimpleOne, execution of business rules, workflows, notifications, engines is bound to database operations. 

The execution order is shown and described below:

Before insert/update/delete

 The processing of the following elements is bound to the transaction BEGIN SQL statement:

1. ACL
2. Domain events: filling the Order and Number field in relevant records, adding column prefixes where appropriate.
3. Business rules:
   1. Rules with When = before and Order <=1000.
   2. Rules with When = before and Order >1000.
4. Validation (is skipped for delete).
5. Database transaction (insert/update/delete).
6. Save REM.

In SimpleOne, business rules, workflows, notifications, engines all run relatively to database operations. Generally, the execution order is important.

The execution order is shown below and listed as follows:

1. Before business rules (where When is Before and Order is less than or equal to 1000).
   1. Assignment rules
2. Before engines.
3. Before business rules (where When is Before and Order is greater than 1000).
4. Database transactions (insert / update / delete records).
5. Record field changes logging (to the History (sys_history) table).
6. Configuration pack engine operations.
7. After business rules (where When is After and Order is less than or equal to 1000).
8. After engines:
   1. Approval Engine
   2. Workflow
   3. Notifications
9. After business rules (where When is After and Order is greater than 1000).

After insert/update/delete

 The execution of the following elements is bound to the transaction COMMIT SQL statement:

1. Infrastructure events (include processing of History, Activity Feed, Create VCS Records, Execute REM After Scripts).
2. Engines:
   1. Business rules with When = after and Order <= 1000.
   2. Approvals
   3. Workflow
   4. Notifications
   5. Business rules with When = after and Order > 1000.