Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Each Rule will begin with at least one Trigger, controlling when the rule will be executed. Checkout Automation allows 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.

Request created

This will cause the rule to run whenever an order is placed by a customer.

Request declined

This Trigger will cause a rule to run when an Agent declines a request from a customer.

...

Image Added

Request ordered

This Trigger will cause a rule to run when an Agent submits an Order from a customer.

...

Image Added

Request completed

This Trigger will cause a rule to run when all Items in the order have been marked as received.

Image Modified

Request canceled

This trigger will cause a rule to run when any Item which has been ordered is canceled by an agent.

Image Modified

This automation can run on a ticket each time an Item is canceled. For this order, the automation could run twice if each Item is canceled.

Request returned

This Trigger will cause a rule to run when any Item on an order is returned.

Image Modified

Request updated

This Trigger will cause a rule to run when the Checkout Order is updated.

Unapproved vendor created

This Trigger will cause a rule to run when an agent fills out information for a Vendor requested by a customer.

Image Modified

Unlisted vendor created

This Trigger will cause a rule to run when a customer requests a new Item and fills out a new Vendor name.

...

Image Added

Asset assigned

This Trigger causes a rule to run when an asset is assigned to a user.

Asset created

This Trigger causes a rule to run when an asset is created.

Asset retired

This Trigger causes a rule to run when an asset is deleted from the system, or when the status of an asset is marked as “Retired”.

Image Modified

Table of Contents