Arbor Workflows: Adding a Decision

Decisions are workflow steps where recipients approve or reject requests. Approval triggers the next step; rejection halts the workflow, though rejection-triggered automatic actions still run. Configure decision details, messages, automatic rules, approval requests, outcomes, and optional updates or reminders.

 

Decisions are available to MIS users on a Comms and Perform Tier at School-Level.

 

What is a Decision?

A decision can be used as a step in a workflow to ask for approval for something or confirmation that something has happened. The recipient will be provided with the option to either approve or reject the request.

One example would be that a leave request may be sent to a line manager or business manager to ask for approval for a period of leave. The recipient will be provided with the relevant information and will be given the option to approve or reject the request.

Approving the request will result in the next step being triggered.

Rejecting this decision will halt the workflow.

It is important to understand the outcomes of these decisions. Rejecting a decision will halt the workflow, with no further steps triggered. Any Automatic actions that are triggered when a decision is rejected will still run.

 

How do we add a decision to a workflow?

Adding a decision to your workflow is super simple. 

Upon clicking on the + Add Step button, you are able to select from a range of options, as pictured below. To add a decision step, you are going to select Decision from the options provided.

Within the Decision step there will be 5 areas to configure:

  • Decision details
  • Message to decision maker
  • Automatic decisions
  • Approval request
  • Outcomes

 

Decision Details

Upon selecting Decision you will complete the Decision details:

  • The Decision name
  • Who makes the decision
  • Due date

 

 

In the example below, you can see that we are asking the Business Manager to authorise a leave request. Instead of typing the names of the decision makers, we are using the role data for these individuals. This is really important as it ensures that all of the steps integrate with one another properly.

 

Message to Decision Maker

Once you have added a title, a decision maker and due date you can then use the Message to decision maker to add some additional context to your request. This information will be visible to the user when they open the decision. 

Within the Message to decision maker, you can add a message that will be presented to the decision maker when they make their decision. It is integral, therefore, that the approver has all of the required information in order to make their decision.

This information will most probably have been collected as part of the workflow. Using Dynamic data you can pull this into this message box. In our example, you can see that we are providing the Business Manager with some additional context as to who is requesting annual leave, along with the period of time that they require. 

All of these pieces of information have been gathered elsewhere in the workflow, so we are referring back to them using Dynamic data.

 

Automatic decisions

You may want to add 'Automatic decisions', formally known as rules, to your decision step when certain conditions are met. For example, you might want to auto-approve any decision apart from the Line Manager if cover is not required. 

Alternatively, you may want to set a specific decision maker dependent on the person making a request. 

By selecting the 'Add automatic decision' button you can configure these. 

Once selected a slide over will appear with options of what you would like the decision to do. 

Automatic decisions can be used to Auto-approve when certain conditions are true, Auto-reject when certain conditions are true, Set Decision Maker for the decision is there is not one decision maker for all possibilities relevant to this decision and Skip the decision when certain conditions are met. 

Lets take a look at each of these.

Auto-Approve:

Once you select Auto-Approve and whether you want this action to 'Do right away' or 'Wait a while' you can begin the build the automatic decision. Select 'Add when it happens' to start this. 

Depending on your process, you may not want this to auto approve start away. This is when you would select 'wait a while' and be prompted to add the duration of the wait.

From here we configure the behaviour, for the automatic decision to use. The easiest way to think of this is by using the approach of 'if this happens / is true, then, do this'.  

Clicking into the bar under 'IF' will open the available dynamic data from the information within your workflow up until this step. 

For this example of planned absence, we want to get the condition to auto approve this decision for School staff as these requests go another decision maker, who in our example will be the decision maker at the next step. If this wasn't the case it would also be appropriate to use the 'Set Decision Maker' option. This information is not automatic and was collected as part of an earlier form.

Once you are happy with the condition, select 'Save Condition'. This will collapse the view. 

From here you can set other conditions that apply to that same rule or 'Save Rule' to finalise the process. This will again collapse the view and from here you can continue to add rules as needed.

 

Auto-Reject:

This process for adding an Auto-Reject mirror that of Auto-Approve above. By Selecting the Auto-Reject option and the delay option. 

 

 

 

Set Decision Maker:

By selecting the 'Set Decision Maker' option within Automatic decisions you are able to route the decision to different recipients based on conditions you set. These conditions are built from information that appears prior to this step in the workflow. This may be information collection as part of a form or be about the workflow in entirety such as the school within a group it is running for. 

A popular use case for this option is if different departments within your organisation require different approver. These departments would be need to collected as part of your workflow but can then be used in the 'conditions' to control the route of this decision. Another may be choosing decision makers dependent on the leave type requested.

You will need to configure the decision maker. This will be the person the decision is routed to if the condition is met, rather than the default decision maker found at the top of the decision step. 

in this example we have configured the HR Administrator to be the approver when the reason for leave is medical. 

 

Once configured the rule can be saved.

This will collapse the view and you will see the rule within the list, if you have multiple.

Automatic decisions work from a 'top down' approach meaning the first rule that is met will steer the workflow direction. 

If no automatic decisions can be met than the decision will always be sent to the decision maker by default that is attached to the decision at the top of the step.

 

Approval Request

 

What about Automatic action?

Should you choose to, you also have the option to use automatic actions to add updates to this step.

These are additional steps which will be triggered, depending on which decision is made by the approver.

If you’d like to add updates or reminders to your decision, This video will show you how and you can use our helpful article What is an Automatic Action? to find out more about this.

 

 

Was this article helpful?
0 out of 0 found this helpful
I'm still stuck!

Comments

0 comments

Article is closed for comments.