Introduction to the Complex Gateway

6-32 Modeling and Implementation Guide for Oracle Business Process Management ■ Configuring a deadline for an activity. ■ Configuring a deadline for a process. ■ Triggering additional activities after an elapsed time. Figure 6–40 shows the default notation for the timer catch event. Figure 6–40 The Timer Catch Event The timer catch event is represented by a two concentric circles with a clock icon in the middle. You can use timer event as boundary events on an activity. Timer events can be defined as either interrupting or non-interrupting boundary events. When an interrupting timer event fires, the token leaves the main process flow to follow the flow the timer defines. The flow that an interrupting can return directly to the main process flow. When an non-interrupting event fires, a copy of the token is created and passes through the flow the timer event defines. The flow that a non-interrupting event defines cannot return to the main process flow.

6.8.3 Introduction to the Error Catch Event

Error catch events are intermediate events used to handle an error that occurs within your process flow. Error catch events are always used as boundary events and can be attached to the following: ■ Service Tasks ■ User Tasks ■ Send Tasks ■ Receive Tasks ■ Script Tasks ■ Rules Tasks ■ Event Subprocesses ■ Subprocesses Error catch events are always interrupting, meaning that they interrupt the normal flow of a process. Figure 6–41 shows the default notation for the error catch event attached as a boundary event on a service task. Figure 6–41 The Error Catch Event as a Boundary Event on a Service Task Modeling Business Processes with Oracle BPM 6-33 This figure shows a service task with the error catch event as a boundary event. The service task is represented by a rectangular box containing two gears in the center. The error catch event is represented by two concentric circles with a lightning bolt in the center. When a service or process fails with an error, the error catch event triggered. This causes the process flow to follow the path of the outgoing sequence flow of the error catch event. You can use this flow to define how you handle the error. This is generally handled in two ways: ■ The process flow returns to the main process flow. Any work that must be performed is handled within the error process flow before returning back to the main flow. ■ The process flow from the error ends in an error event. The process is terminated immediately. Process control is passed to the service or process that initiated the process.

6.9 Using Subprocesses to Organize Your Process

In Oracle BPM, subprocesses are embedded subprocesses. Subprocesses are contained as part of the parent subprocess. Subprocesses must begin with a start none event and must end with a none end event. Subprocesses can be expanded or collapsed. Figure 6–42 shows how a collapsed subprocess appears within a process. Figure 6–42 Example of a Collapsed Subprocess This figure shows an example of a collapsed subprocess. It shows three flow objects in a straight line: A service task, a subprocess, and a user task. Each is connected by a sequence flow. The collapsed subprocess displays a plus icon that expands the subprocess. Figure 6–43 shows how an expanded subprocess appears within a process. When a subprocess is expanded, you can edit the flow objects within. You can also click and drag the edge of the subprocess window to make the window larger or smaller. Note: If the boundary event is non-interrupting, the boundary flow cannot return to the main flow.