Workflow Structure
Cascade Server ensures that content entered into the system is quality checked by mandating that the entered content go through a series of approval steps. These steps can be configured through the web interface.
A workflow is simply a grouping of these steps. A step might have a name such as "Managerial Approval", "Final Approval", and/or "Re-Edit". These steps are connected by actions that provide a pathway for moving from one step to another step. Note that one step may have multiple actions leading out of it.
Once the workflow moves to a step with no other actions leading out of it, the workflow is considered to be complete/finished. The asset associated with the workflow is then no longer to be considered in workflow and is returned to a normal state.
- Steps
The steps that make up a workflow are divided into Ordered Steps (steps that will be executed in the order they are listed in the XML), and Unordered Steps, which must be explicitly indicated by an action. - Actions
Transitions between workflow states (or steps) are enabled by Workflow Actions. An action is defined as a directed path from a source step to a destination step. - Triggers
Actions can be enhanced by attaching one or more workflow triggers. The trigger executes code while the transition is occurring from the source step to the destination step.