Creating Delegate Actions

Peter Campbell Updated by Peter Campbell

Although they are used in conjunction with Process Templates, Delegate Actions have their own section within the Configuration module.

Delegate Actions contains three tabs, Templates, Action Types and Roles.

Templates are what you would select from within the Process Template. It defines and pulls together the order in which different actions have to happen, the type of action that has to happen, and the role that can perform the action.

Action Types is what defines the details of the action such as possible outcomes and what the pending status looks like.

Roles are what you will assign to users who need to complete the prescribed action. This is done from within the Team Management module.

Roles

When creating a role, the Name is required and Description of the role is optional.

The role is what will appear in the list of Delegate actions that can be assigned to a user in the Team Management module (Assigning Delegate Roles has its own article that follows this one). Its corresponding action/purpose is defined by the Template for the Delegate Action being completed.

Action Types

The Action Type lets the user define what the type of action will be called, what the status of the artefact will be while the action is pending, and also options for the possible response.

For the response, the action taken is the first field, the status shown to the user is what’s in the second field and whether this action corresponds to the action being completed (And allowing progress) or not is determined by the third field.

Templates

Finally, templates bring together the actions required and assigns them to the roles created. There can be multiple actions within a Delegate Action, and these can be set up to be required in a specific order or in any order.

When all the actions have been added, you can drag and drop them to change the order easily.

Was this article useful?

Creating a Process Template (Contracts)

Assigning Delegate Roles

Contact