Page Comparison

There are three types of Actions that can be used with their respective trigger types: order, vendor, and asset. Available Action options are filtered based on the type of Trigger selected.

Order Actions

Create Jira Issue

Image Added

The Create Jira issue action allows Automation to create an issue of a specified issue type in a specified project.

Available for Triggers:

Administrator must specify a Summary along with any other custom fields which are required for the issue type in the project they are creating.

The create issue action also comes with the Add additional metadata checkbox. This feature will be used to surface Checkout information on linked tickets, but the components to show the information are still under development.

Edit request Issue

Image Added

The Edit request issue action allows users Automation to modify fields on the request action.

Available for trigger types:

• Order Triggers

Details:

This automation action works very similarly to the Create issue action. Administrators can use the Edit issue action to set custom fields on a ticket once the rule is triggered.

Create request comment

Image Added

The Create request comment action allows Automation to automatically comment on the Order Issue that triggered this rule. Administrators can set the comment to be public or internal. The comment will be made as the user Checkout.

Image Added

Decline order items

Image Added

The Decline order items action allows Automation to decline all items in an order.

Image Added

Disable submit/fulfill order button

Image Added

The Disable submit/fulfill order button action allows Automation to disable the Submit Order button on a ticket to prevent the agents from generating a purchase order to send to the Vendor.

Image Added

Enable submit/fulfill order button

Image Added

The Enable submit/fulfill order button action allows Automation to enable the Submit Order button on a ticket to allow the agents to generate a purchase order.

Send Webhook

Image Added

The Send Webhook action allows Automation to connect to a webhook through a URL when the automation rule is triggered.

Available for trigger types:

Details:

Administrators can set up a webhook to fire when the automation rule is triggered. The following information is required:

• HTTP method (GET, POST, PUT, PATCH, DELETE, HEAD)

• Webhook URL

Administrators can also define custom headers for authentication purposes or other custom requirements.

If the HTTP method is POST or PUT, the body will be a JSON containing the Checkout Order information.

Example:

{
  "items": [
    {
      "itemId": 307,
      "quantity": 1,
      "price": 229.99,
      "itemTitle": "Portable SSD T7 TOUCH USB 3.2 1TB (Black)",
      "itemDescription": "SSD with fingerprint and password security",
      "vendorId": 194,
      "type": "PRODUCT",
      "status": "NEW",
      "items": null,
      "backFill": false
    }
  ],
  "unlistedItemRequests": []
}

Send Slack Message

Image Added

The Send Slack Message action allows Automation to send a Slack message to a specific channel when the rule is triggered.Available for trigger types:

• Order Triggers

• Vendor Triggers

• Asset Triggers

Details:

The administrators will need to provide the following:

• Webhook URL (Incoming Slack URL)

• Message

• Channel or User

Information about setting up the integration on the Slack side can be found here.

Transition Issue

Purpose: Allows the user to transition the issue from one status to another.

Available for trigger types:

• Order Triggers

Details:

Administrators can choose which status the issue will be transitioned to when the Checkout automation rule is triggered.

The transition will still respect any validators or conditions present on a transition.

Purpose: This action allows admins to put automated comments on a ticket when triggered.

Available for Trigger Types:

• Order Triggers

Details:

• Administrators can customize a comment which will be left on the ticket when the automation rule is triggered.

• The comment will be made as the user Checkout.

• Administrators can choose whether the comment is Internal or an External.

Image Removed

Decline order items

Purpose: Decline all items in an order.

Available for trigger types:

• Order Triggers

Disable submit order button

Purpose: Disable the Submit Order button to prevent the agents from generating a purchase order to send to the Vendor.

Available for Trigger Types:

• Order Triggers

Enable Submit Order Button

Purpose: Enable the Submit Order button on a ticket to allow the agents to generate a purchase order.

Available for Trigger types:

Vendor Actions

Create Jira Issue

(see above)

Asset Actions

Create Jira Issue

(see above)

Edit asset attributes

Purpose: Allows administrators to customize asset attributes when the automation rule is run.

Available for trigger types:

• Asset Triggers

Details:

• This action can set values for asset attributes when run. Status, Vendor, and User Picker attributes are not supported.