A ticket rule only defines a name. A ticket rule by itself does not cause any processing to occur. To affect processing, a flow rule must reference a ticket and define the processing that is to follow ticket activation. While the names of tickets suggest their purpose, you control whether, where, and how they are used.
Use the Records Explorer to see a complete list of the tickets available to you.
Your system includes a several standard tickets. A few standard tickets of general interest are referenced by standard flows. Other standard tickets not listed here support the various built-in accelerators and tools.
Ticket
|
Purpose
|
| Work-.SkipFlowStep
|
By convention, this ticket is used in a flow as the destination when part of the flow can be bypassed or skipped over. |
| Work-.Status-Resolved
|
In the standard Work-.OverallSLA flow, this ticket is set — turned on — each time a work item is resolved. You can include it in your flows if there is a possibility that a second flow could be affected by the resolution of a work item. |
| Work-.Withdraw
|
By convention, use this ticket name to mark processing that is to occur if the work item is "withdrawn" by its originator. |
| Work-Cover-.AllCoveredResolved
|
This ticket is available to alert a flow in process on a cover work item when and if all covered work objects become resolved. |
About Tickets
Standard rules index
Open topic with navigation