|
|
More about Tickets
As best practice, define the names of tickets through this rule form. Thereafter, developers can then use SmartPrompt to choose from the list of tickets, rather than typing in a value. You can also enter a display name for the ticket, so that the ticket name that appears on the flow is different than the actual ticket name.
However, ticket rules are optional; a ticket rule defines only a name. When completing the ticket Properties panel, you can reference a ticket rule that is not defined (that is, no ticket rule has that name). This does not prevent the flow from being saved and executing correctly.
How tickets are raised
Any of various events can "raise" or turn on a ticket:
- Users can select the standard Work-.SetTicket or @baseclass.SetTicket flow actions when processing an assignment.
- Processing can call a standard activity @baseclass.SetTicket.
The Status-Resolved ticket
When a work item becomes resolved (the status changes to a resolved status), PRPC automatically turns on (or "raises") a ticket named Status-Resolved. Every flow execution in process for the work item that contains a ticket with this name is interrupted and control transfers to the ticket shape in the flow.
|
ticket |
|
Flow form — Editing in Process Modeler — Tickets
|
|
Atlas — Standard Tickets |
About Tickets