We have made the Order Approval process really simple in Checkout. To turn on the approval process, all you need is an Approval Workflow in your project that is tied to the Checkout issue type. This guide lays out how an administrator can set up a required approval in a Checkout project.
We have made the Order Approval process really simple in Checkout. To turn on the approval process, all you need is an Approval Workflow in your project that is tied to the Checkout issue type. This guide lays out how an administrator can set up two different kinds of approval process - a required approval, or optional approvals.
Setting up a Required Approval Process
The screenshot below shows the Approvals workflow which is automatically generated when an IT Service Desk template is used to create a project. Any workflow can be used to set up an approval process, but this one is a great starting point if you aren’t too familiar with constructing workflows.
If the Checkout project was created with the IT Service Desk template, this workflow should be created, but not in use on the Checkout project. It will be named in the form of project-key: Service Request Fulfillment with Approvals workflow for Jira Service Desk. To use it on the Checkout issue type, modify the project Workflow Scheme and assign that workflow to the Checkout issue type.
Any of the statuses can be turned into an approval status by selecting the status and checking the Add approval check box. The key for this workflow is that the create transition leads to the Waiting for Approval status, which we will set up to require an approval.
The Waiting for Approval Status has special configurations that allow you to set the Approver fields. Leave it at the default Approvers field. Checkout adds the Department owner to this field - which in turn turns on the approval process.
Automations
Next, you will want to
For example, if you want to inhibit further processing of the order until approval process is complete, you can disable all checkout buttons.
Once order is approved, you can enable the buttons via automation.
If approval is declined, then the Checkout order can be declined as shown below.
Setting up an Optional Approval Process
We can also set up an Optional approval process. For example, we may only require an approval on a Checkout order if the total cost is over $500. To configure an Optional approval process is very similar to the approval process outlined above. We will use all the same concepts, but an additional Checkout automation will be introduced to decide whether or not the ticket requires an approval.
Creating the Workflow
The first step would be to create a customized workflow which will be used to facilitate optional collection of approvals. A simple workflow will suffice. In this example I’ve created a workflow called Optional Approval and tied that to the Checkout issue type.
The key to this workflow is that the status which we configure for approval is NOT going to be the first one in the workflow. Instead, we introduce a temporary Open status. The issue will only remain in this status while the automation decides where it will move.
As with the previous example, be sure to configure the approval to use the Approvers custom field if the Department lead is that one who will be approving tickets.
Automations
Next, you will want to turn on automations in the project. To do so, navigate to Project Settings > Automation > Legacy automation. In this section, we have added some actions that work with the approval process.
As detailed above, we can stop further processing of the order until approval process is complete by setting up an automation rule as follows:
If approval is declined, then the Checkout order can be declined as shown below.
Additionally, Checkout provides some special automations which allow us to perform actions based on information found in the Checkout order. To access, navigate to Project Settings > Checkout > Automation.
Click on Create Rule and configure it with the following settings:
This automation will transition a ticket to Waiting to Approval if the total of the order is over $500, otherwise it will move to Waiting for Support. When it does move to Waiting for Approval, the automations we configured in the other section of administration will help us require an approval. These automation rules will disable the Submit Order button until a request is approved, re-enable the Sumbit Order button if the request is approved, and automatically decline all Items if the request is declined.
To create the automation rules, navigate to Project Settings > Checkout > Automation > Create Rule.
Let’s take these one-by-one:
Disable the Submit Order button when an approval is required. Create a new rule with the following configurations:
Re-enable the Submit Order button once the request has been approved. Create a new rule with the following settings:
The final automation rule we want to create will mark all Items in an Order as declined if the approver declines the request. Set up a rule as follows:
| Note |
|---|
Please be sure to check that the trigger you are using is “Request Declined” with a capital “D”. we have a known issue with triggers being named similarly right now. |
| Table of Contents |
|---|
| Filter by label (Content by label) | ||||
|---|---|---|---|---|
|
Write into our Support Desk with any questions you have.