...
The Request created trigger 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 (see below example).
...
Request ordered
This Trigger will cause a rule to run when an Agent submits an Order from a customer (see below example).
...
Request completed
This Trigger will cause a rule to run when all Items in the order have been marked as received (see below example).
Request canceled
This trigger will cause a rule to run when any Item which has been ordered is canceled by an agent (see below example).
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 (see below example).
Request updated
This Trigger will cause a rule to run when the Checkout Order is updated.
Issue Pending Approval
This Trigger will cause a rule to run when the Order Issue has entered the Pending Approval status.
Issue Approved
This Trigger will cause a rule to run when the Order Issue has received an approval.
Issue Declined
This Trigger will cause a rule to run when the Order Issue approval has been declined.
Vendor Triggers
Unapproved vendor created
This Trigger will cause a rule to run when an agent
...
...
Vendor requested by a customer (see below example).
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 (see below example).
...
Asset Triggers
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 updated
This Trigger causes a rule to run when an asset has been updated.
Asset deleted
This Trigger causes a rule to run when an asset is deleted from the system (see below example).
| Table of Contents |
|---|