Difference between revisions of "Features/Workflow engine"
Jump to navigation
Jump to search
(→Usage) |
|||
| Line 8: | Line 8: | ||
== Automated actions == | == Automated actions == | ||
Entering, leaving or staying in a certain status can trigger certain actions in the system. | |||
Trigger summary | |||
* Enter | |||
* Leave | |||
* Timed | |||
Timed actions are defined as an amount of time, relative to som date fields. | |||
Send an email 1 day before the date defined in the BIRTHDAY field | |||
Execute code 7 days after this status was reached | |||
| Line 14: | Line 25: | ||
=== Webservice callback === | === Webservice callback === | ||
=== Execute code === | |||
== Process performance == | == Process performance == | ||
Revision as of 09:08, 9 November 2024
Usage
All entities in the system have workflow / lifecycle model attatched to them. In addition all records will have a status field, indicating the records place in its workflow. Each step in a workflow is called a status, and influences how records behave in that step (status).
- What new status can be assigned from here
- What automated actions should be carried out (see below)
- What permissions do the users have in this step
- What fields should be shown or hidden
Automated actions
Entering, leaving or staying in a certain status can trigger certain actions in the system.
Trigger summary
- Enter
- Leave
- Timed
Timed actions are defined as an amount of time, relative to som date fields.
Send an email 1 day before the date defined in the BIRTHDAY field
Execute code 7 days after this status was reached