Difference between revisions of "Features/Workflow engine"

From TempusServa wiki
Jump to navigation Jump to search
Line 29: Line 29:
* Delete data (GDPR compliance)
* Delete data (GDPR compliance)


=== Notification ===
Learn more about [[Status_actions|Status action configuration]]
Notifications can be either based on fixed or dynamic recipient values.
 
Variants dependening on recipient field type
* CPR field: Message will be a PDF sent by eBoks
* Phone field: Message will be sent as an SMS
 
=== Webservice callback ===
 
=== Execute code ===
 
== Process performance ==

Revision as of 11:06, 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

Actions include

  • Notifications
  • Task creation
  • Code excution (this can do anything)
  • Change status
  • Export data
  • Delete data (GDPR compliance)

Learn more about Status action configuration