Context-bound workflows
A context-bound workflow can be opened in the context menu of a tree element using the general “Start Workflow” function.
All context-bound workflows from the project's Template Store are listed under this context menu entry.
If the entries are inactive the person dealing with the task does not have the necessary permissions to start the workflow on the tree element. |
Depending on the template developer's settings, workflows can also be started by means of a user-defined keyboard shortcut. |
After a workflow has been started an action window appears. Various settings can be made or read in this action window. The dialog box can be used to switch the selected object to the next state within the workflow, for example, from the start state to a following state (for an example, see Requesting a release via the task list).
At each node within the tree structure, only one workflow can ever be active at any one time. It is therefore not possible to start a further workflow for an object without ending the already started workflow first or unless the workflow has reached the final state.
If a workflow has been started for an object, the context menu entry changes. Instead of “Start Workflow”, the menu now shows the “Workflow Action” entry:
All actions that have to be executed to switch the active workflow to the next state are listed under this context menu entry.
If the entries are inactive, the person dealing with the task does not have the necessary permissions to switch the workflow to another workflow state on the tree element). |
Depending on the template developer's settings, workflows can be switched to another workflow state by means of a user-defined keyboard shortcut. |
After an action has been opened an action window appears again in which the various settings can be made or read.
Started schedules can also be switched via the task list.