Difference between revisions of "Features/Workflow engine"

From TempusServa wiki
Jump to navigation Jump to search
Line 1: Line 1:
== Usage ==  
== 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 actions below)
* What permissions do the users have in this step
* What fields should be shown or hidden


== Automated actions ==  
== Automated actions ==  

Revision as of 09:04, 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 actions below)
  • What permissions do the users have in this step
  • What fields should be shown or hidden

Automated actions

Notification

Webservice callback

Process performance