Create an Approval Model

Approval Model

You can create an approval model workflow in ShareDo Modeller.

Approval Type	Description
Jump to Phase	Specifies an approval process for when the supervisor process 'jump to phase' is used. Once your approval process is defined, you will need to link it to the appropriate phase jump. See the jump to phase feature.
Budget Phase Transition	Used specifically for budget phase transitions.
Phase Transition	Used where a work type moves from one phase to another. This option also includes the approvals process for documents.
Fees	An approval process used in the authorisation of fees.

Field	Description
Approval Type	As described above
System Name	A unique system name for the approval model
Name	A meaningful name that describes the purpose of the approval model
Description	A description of the purpose of the approval model
Icon	A font awesome that represent the approval flow
ShareDo type context	The work type to which the approval will apply
Always approve	Used for approval processes which will automatically approve an item (frequently used in document templates)

The approval model canvas is displayed. Basic settings are displayed on the left of the screen and can be edited using the edit button. The right-hand side of the screen allows you to add in approval steps.

Ensure that you set your approval model to enabled.

You are now ready to add your first approval step. Click the plus button at the top of the screen
Enter the system name for the step. The system will prefix this automatically with the name of your plan.
The first thing to add is the Approval Task details. This configures the nature of the task that appears when an approval is triggered.

Field	Description
Task Type	Specifies the task type that will be triggered for the approval. This appears in the approvers worklist.
Title	Determines the title of the approval task - note that tags can be used to insert items such as the work type title. The available tags are listed in the use interface for guidance.
Description	The description that goes onto the task to be read by the approver. This can include tags that describe the work item e.g. title. Available tags are shown in the approval step user interface for reference.
Due Date Offset	The number of calendar days / hours until the approval task is due for completion.
Process Tags	Process tasks are used within execution engine plans to identify specific instances of tasks and trigger workflow. For example, when a specific thing is approved, it may trigger another action to occur.

Approval Assignment allows you to configure to whom an approval is sent. For example, an approval could be sent to the current users supervisor or to a supervisor team. Approval assignments use allocation rules.
In the assignment rule field, select the allocation rule you wish to use for your approval. You can use an existing rule or create a new one.

If you cannot see a new allocation rule, refresh your modeller cache by clicking the recycle button at the bottom left of the modeller home page.
The Auto Approval section defines scenarios where the item up for approval should automatically be approved. For example, all low-priority service requests do not need to be approved before closure, or automatically approved if the originator of the approval is themselves a valid approver. If auto-approval occurs, no approval task is created, and the item will automatically move to its approved phase.

Use a business rule to define when an auto approval should occur. If you do not wish to use an auto-approval, leave Auto approve off.

If the approval is a multi-step approval, then an auto approval would only skip the relevant step and any further approvals that did not meet the business rule. This is an effective way of implementing a tiered approval process, for example, based on value.

The Manual Reassignment section deals with any rules around the manual reassignment of an approval in the scenario where the person to whom the approval is sent reassigns or delegates it. This could be a common scenario where you are using the auto delegation feature. Enter here any users or teams who should or should not be assigned the approval in the event of a manual reassignment.

For more information, see the article Security Barriers.

Multi-step approvals can be created by adding more than one step. The steps will be executed sequentially.

You are now able to create an approval rule and configure manual approval security barriers.