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

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

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

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

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

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.

Decline order items

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

Disable submit/fulfill order button

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.

Enable submit/fulfill order button

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

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

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:

Code Block

{
  "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": []
}

Additionally, if the trigger for the rule is Order Updated or Asset Updated, the JSON body will contain a changelog property.

The changelog for orders have a few different formats depending on what happens. If an item or unlisted item request is added or removed by an agent, then the changelog will look similar to this:

Code Block

  "changelog": {
    "order details": {
      "total": {
        "from": 10746.99,
        "to": 10646.99
      }
    },
    "items": [
      {
        "name": "Toshiba Canvio Flex",
        "action": "DELETED",
        "item": {
          "items": null,
          "itemId": 20214,
          "quantity": 1,
          "price": 100,
          "itemTitle": "Toshiba Canvio Flex",
          "itemDescription": "Large portable HDD from Toshiba",
          "vendorId": 3159,
          "type": "PRODUCT",
          "status": "NEW",
          "backfillQuantity": null,
          "creatorRole": "SERVICEDESK_AGENT",
          "backFill": false
        }
      }
    ]
  }

However, if an item or unlisted item is edited, or the order details are edited, then it may look more like this:

Code Block

"changelog": {
    "order details": {
      "total": {
        "from": 16046.99,
        "to": 21145.99
      },
    },
    "items": [
      {
        "name": "Apple iPhone 11 Pro",
        "action": "MODIFIED",
        "price": {
          "from": 999,
          "to": 500
        }
      },
      {
        "name": "Apple Macbook Pro 16\" - Space Grey",
        "action": "MODIFIED",
        "quantity": {
          "from": 1,
          "to": 3
        }
      }
    ]
  }

The asset data changelog will be a similar format to when an item has been modified.

For example:

Code Block

  "changelog": {
    "serialNumber": {
      "from": "1234",
      "to": "123456"
    },
    "98d8bdac-7ced-4c88-8454-8029563fee91": {
      "from": null,
      "to": "5f0f341bce15e800264bf95d"
    },
    "9e9109c4-fcc2-4723-8c61-5320b05ae80a": {
      "from": null,
      "to": "123"
    },
    "dateAssigned": {
      "from": null,
      "to": "2024-05-24"
    }
  }

To extract Checkout webhook datawith Jira automation, see our how-to article here!

Send Slack Message

The Send Slack Message action allows Automation to send a Slack message to a specific channel when the rule is triggered.
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
The Transition issue action allows Automation to transition the issue from one status to another.
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.
Approve issue as Checkout addon
The Approve issue as Checkout addon action allows Automation to approve an issue.
Vendor Actions
Create Jira Issue
(see above)
Send webhook
(see above)
Send Slack message
(see above)
Asset Actions
Create Jira Issue
(see above)
Edit asset attributes
The Edit asset attributes action allows Automation to customize asset attributes when the rule is triggered.
This action can set values for asset attributes when run. Status, Vendor, and User Picker attributes are not supported.
Send webhook
(see above)
Send Slack message
(see above)