Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-08-2019 01:57 PM
It's not really well shared.
Is a link to the old wiki with what I knew about them;
The order of execution is as follows:
Before business rules: Scripts configured to execute before the database operation with an order less than 1000.
Before engines. The following are not executed in any specific order:
Approval engine (for task and sys_approval_approver tables)
Assignment rules engine (for task tables)
Data policy engine
Escalation engine
Field normalization engine
Role engine - keeps role changes in sync with sys_user_has_role table (for sys_user, sys_user_group, sys_user_grmember, and sys_user_role tables)
Execution plan engine (for task tables)
Update version engine - creates version entry when sys_update_xml entry is written (for sys_update_xml table)
Workflow engine (for default workflows)
Before business rules: Scripts configured to execute before the database operation with an order greater than or equal to 1000.
The data base operation (insert, update, delete).
After business rules: Scripts configured to execute after the database operation with an order less than 1000.
After engines. The following are not executed in any specific order:
Label engine
Listener engine
Table notifications engine
Role engine - keeps role changes in sync with sys_user_has_role table (for sys_user, sys_user_group, sys_user_grmember and sys_user_role tables)
Text indexing engine
Update sync engine
Data lookup engine inserts or updates
Workflow engine (for deferred workflows)
Email notifications. The following are executed based on the weight of the notification record:
Notifications sent on an insert, update, or delete
Event-based notifications
After business rules. Scripts configured to execute after the database operation with an order greater than or equal to 1000.
I note this in a visual I refer to for checking things here;
https://workflow.jacebenson.com/?flow=BusinessRuleOrderSequence