Workflow Manual / Version 2204
Table Of ContentsActions are used to automate or semi automate tasks. To do so, arbitrary actions can be invoked at the start or end of a user task, during an automated task, or at the very end after a process was completed or aborted.
User Task
Element
<EntryAction>This kind of action is invoked after the task is accepted, but before the user starts to work on the task. Typical start actions are the initialization of resources.
Element
<ExitAction>These actions are invoked after the task has been completed by the user and after the postconditions are checked, but before the workflow continues. A typical exit action might complete the users work and set some calculated properties, approve resources in the name of a user, show up a publication window etc.
Automated Task
Element
<Action>An automated task is not performed by a user. The task duration is exactly the duration of the invoked actions plus preconditions and conditions. If preconditions or postconditions are violated, the task is aborted.
Final Action
Element
<FinalAction>Final actions are invoked after the process completed successfully or was aborted. Typical use cases are cleaning up used resources or archiving data from the process before it gets deleted. Compared to actions running in a task, these actions use a different interface and cannot modify the process itself anymore.
User task actions are executed with the rights and on behalf of the user who accepted the task. Actions in automated tasks and final actions run with the Workflow Server's "user" account at the Content Management Server.
