You are here: Case management > Modeling a workflow > Capturing business exceptions in a flow

Capturing business exceptions in a flow

A ticket in a process flow marks a location or starting point for business exceptions that may arise at any point in a flow. When an external event, such as a cancellation, interrupts the planned progress of a work item through the process flow, the ticket marks the point in the flow where processing should resume whenever the ticket is activated. The scope of a raised ticket includes all flows on the current work item.

Standard tickets are available. For example, the SkipFlowStep ticket can be used in a process flow as the destination when part of the flow can be bypassed or skipped over. Withdraw can be used to mark processing that is to occur if the work item is withdrawn by its originator.

Use the Tickets gadget (Designer Studio> Process and Rules > Work Management > Tickets) to verify which tickets are in active use, and by which flows or activities, in the current application.

Include tickets and utility tasks to accommodate cancellations, rollbacks (sometimes called compensating transactions), errors, and similar exceptions.

To set or raise a ticket, you can:

In Process Modeler, specific shapes have the ticket functionality built into the properties panel. The symbol appears on shapes that have an assigned ticket. Assigned ticket names appear beside this icon on the flow. Assigned ticket names appear beside this icon on the flow. The following shapes allow tickets:

  • Assignment
  • Decision
  • Subprocess
  • Utility
  • End
  • Split For Each
  • Split Join
  • Integrator
  • Assignment Service

Adding a ticket to the flow

The shapes listed above may have tickets assigned. On the Tickets section in a shape's Properties panel, complete the field according to the table below.

Field

Description

Ticket Name

add rowOptional. Select one or more tickets that are to be available at runtime from this assignment. Add a row for each ticket. Use SmartPrompt to display all tickets available to flows in this work type.

Display Name Optional. The Ticket Name appears by default. Enter a name to display other than the ticket name.

Example

Processing is connected to a ticket to respond to a business exception, error flow or event. For example, if a mortgage application is withdrawn after some, but not all, of the application processing is completed, a mortgage processing flow can:

Work Items with Covers

If a work item is covered, and its status becomes Resolved:

Limits on looping

A flow execution can loop back to a task completed earlier, either through connector or a ticket. The system enforces maximum limits of 500 executions of a task (on a single work item), to detect and prevent infinite looping. In addition, a flow execution can be resumed (such as through a specific ticket) a maximum of 500 times. If necessary, you can adjust these limits by overriding standard System Settings rules Pega-ProCom.MaxFlowEnteredCount and Pega-ProCom.MaxFlowLoopCount