Compound Activities
Compound Activities are Activities that contain subordinate Activities.
They enable Workflow creators to model organisational processes and sub-processes hierarchically.
For example, a Workflow modelled around the systems development lifecycle may have Requirements Definition as the first Activity and within this Activity, the process of defining requirements is mapped out.
This Activity may contain a sub-process of customer consultation, feasibility analysis and requirements formalisation Activities.
- Click the Subordinate Activities button
on the Activity title bar to move to the next level down in the Workflow.
If there is no sub-Activity on that level, Content Manager will insert a copy of the parent Activity there.
-
Click the Jump To Parent button
in the toolbar or Jump in a right-click shortcut menu to go one level up
- In the Workflow design view, select the Activity you want to create sub-Activities within.
This will become the parent Activity for the sub-Activities.
- Select the Activity you want to create a sub-Activity or process for.
Make sure it has a result that you can use to start the Activity on the next level.
- Click the
button or the Subordinate Activities button
on the Workflow toolbar.
This will move you down one level and create the last Activity in a new sub-process.
- Create as many additional sub-Activities as you need and link them.
NOTE: You must create at least two Activities in a sub-process.
- To get back to the parent Activities level, either right-click and select Jump or click the Jump To Parent button from the toolbar.
NOTE:
- The sub-Activity you are creating first on the new level is the same as the parent Activity. Performing an action on one will automatically update the other. The parent Activity will contain all the details of the last sub-Activity and will also contain aggregated details from all the sub-Activities contained within the parent Activity. It will contain aggregated details for all the documents in the sub-process, time spent and cost of the sub-process.
- The last sub-Activity has a red border outline.
- Every sub-process must contain at least two Activities
- The first created sub-Activity will be the last sub-Activity in that sub-level.
Users cannot delete this Activity unless it is the only sub-Activity.
- When users navigate to an upper level, Content Manager checks the design for more than one start/end Activity.
If the design is invalid, a message appears and the navigation fails.
- The last Activity in the sub-process is indicated by a red box around the Activity
NOTE: Upgraded datasets: Existing Workflows need to be modified and saved before the above behaviour is evident.