You can change the path of a process, or flow, to support out-of-sequence events. By adding different structures to your flow, such as loops and branches, you can improve the flexibility of the cases that you create.

• Adding decisions to processes

  Make your business processes flexible and responsive by providing conditional paths that a case can follow to reach a resolution. By adding a decision point to your case, you support more than one outcome for your business process, and adjust the case to changing business needs and circumstances.

• Adding a conditional path to a flow

  You can use a connector to add a conditional path to a flow. By defining the events that cause your flow to follow different paths, you can create cases that support more than one outcome.

• Adding a conditional path to an assignment

  You can use a connector to add a conditional path to an assignment. By defining the events that cause your flow to follow different paths, you can create cases that support more than one outcome. Your application assigns a task, or flow action, to a user only when it cannot find a connector on the Assignment shape with conditions that return a true value.

• Adding a results-based path to a flow

  You can use a connector to add a results-based path to a flow. By using run-time values to determine which path a flow follows, you can create cases that support more than one outcome.

• Adding asynchronous processing to a flow

  You can use the Split Join shape to call two or more subprocesses that later rejoin the parent flow. By dividing your independent business requirements into multiple processes, you can model different types of dependencies in your flow.

• Responding to business exceptions in a flow

  You can use a ticket in a flow to respond to business exceptions, errors, or events that you define. By moving a case to a specific point in a flow, you can ensure that additional processing occurs so that the case is not left in an incomplete state.