A stage in a process may require that a number of other activities are performed before the process can be deemed complete and the process can move to the next stage. As previously mentioned, it is therefore possible to create any number of sub-processes within a process. Use this procedure to add a process within a process.
To add a sub-process:
In Process Designer, select the process to which you want to add a sub-process.
On the Process tab, click Add Process.
When the Additional Information pane opens, complete the following details:
Name. Specifies a name for the sub-process.
Description. Specifies a brief description of the sub-process.
Workflow. Only available when a process does not have a sub-process. Specifies the contact- or matter-level workflow to run when the sub-process is reached. Select Contact or Matter from the drop-down and then choose the desired started. You can also click the Plus sign to create a new workflow. Note the workflow is not automatically selected. Clicking the Edit button opens the associated workflow.
Role type. Only available when the Workflow option is set to Contact. Specifies the type of contact that the workflow will run against, e.g. Client. This enables processes to be run against all the contacts that are associated with an enquiry or matter. At run-time, when the process starts, the contact process is duplicated for each contact associated with the enquiry (or matter) with the specified role type. The duplicated processes appear under the contact process. A process completed condition is attached to each duplicated process to ensure they run one after the other.
Auto-run process. The process automatically moves to In progress when it is Ready. When this option is switched off, a task is created for the user to start the process.
User role. Specifies that a user with the selected role in relation to the matter (e.g. Matter Supervisor) will be automatically assigned any tasks that are created by the process or the workflow associated with the same process. Defaults to Matter Fee Earner.
Automatically transfer tasks to runtime user. When the process runs against an enquiry all tasks are assigned to the run-time user. When this process becomes available to run as a consequence of running earlier processes, this option specifies that its tasks will automatically transfer ownership and run for the currently logged in user, regardless of the user they are initially assigned to.
Due date. Specifies a due date for any tasks created by the process or the workflow associated with the same process. This is the result of a formula. When left empty the task will be due on the date the process became Ready.
Date can be modified. The due date can be modified in the task list, e.g. to defer a process.
Override condition. Specifies a condition that if met before the pre-condition is met, then the process is overridden and does not run. Where this is the case, the Process Overview shows a blue tick to indicate that it is not required. See Process override conditions.
Label. Only visible when you've specified an override condition. Specifies a friendly description that is displayed for the override condition at run-time.
Click Save.
Notes
There is no limit to the number of levels you can create with sub-processes. For example, sub-processes can also have sub-processes attached, and those sub-processes can have their own sub-processes too.
When there are a succession of tasks for the same process (e.g. the associated workflow has multiple attended activities) and another user takes ownership of a task:
All the tasks for the same process go to the new owner.
All tasks are assigned the same due date (the formula is not re-evaluated for each task).