Automation

Overview

Checkout provides an automation module used to automate actions in a Checkout project. Once the rules have been configured, Checkout Automation will perform standard and repeatable actions for the Agents in order to reduce Agent workload and improve consistency.

To get started with Checkout Automation, click Add Automation.

Open

Rules

Checkout Automation is structured around Rules. Every Rule defines which actions will be performed, and when. Every rule has a Trigger which defines which actions cause a Rule to run, Conditions which determine whether the Rule runs for an issue, and Actions which define what is performed on a Rule.

Open

Triggers

Each Rule will begin with at least one trigger, controlling when the rule will be executed. Checkout Automation has three categories of triggers relating to :

• Order events, such as an Order being canceled,

• Vendor events, such as a Vendor being requested, and

• Asset events, such as an Asset being assigned.

Choosing a trigger contextualizes the type of conditions and actions you are going to be able to use in your automations.

Conditions

Conditions are used to check if the automation actions should be performed on a ticket which triggered an automation. Currently, Checkout allows conditions based on the Order status, Order total, Asset Type, and Asset Assignee. For example, if a rule is triggered, we can perform an action if the order total is above $500. Automation also has the ability to do IF/ELSE branches. So the automation could be configured to perform one action if the total of an Order is less than 500, and a different action if the Order total is greater than 500.

Actions

Actions are what cause the actual changes to the Jira system. Actions are the final portion of the rule, and define what should be done in the system if the conditions were met.

For example, using Checkout automation, we can automatically alert Checkout administrators in Slack when their attention is required to approve a Vendor.

Audit Log

Checkout Automation comes with an audit log so that administrators can get information about which automation rules have run, and what the result of those automation rules were.