Using Multiple End Events in a Process

6-8 Modeling and Implementation Guide for Oracle Business Process Management

6.2.3.2 Using Process Input and Output Arguments

The message start event enables you to specify input and output arguments to a process. These arguments define the message that other processes or services must send to the process during invocation.

6.2.4 Introduction to the Signal Start Event

The signal start event is similar to a message start event in that it is based on communication from another process or service. However, the message start event responds to a message sent to a specific process. In contrast, the signal start event is a response to a signal broadcast to multiple processes. Signals can be broadcast from a BPMN process using the signal throw event. Using a combination of signal throw and signal start events, you can invoke multiple processes simultaneously. The signal start and throw events are generally added to a process by process developers. For information on implementing the signal throw event, see Introduction to Communicating Between Processes Using Signal Events in the Oracle Fusion Middleware Modeling and Implementation Guide for Oracle Business Process Management. Figure 6–7 shows the default notation for the signal start event. Figure 6–7 The Signal Start Event The signal start event is represented by a single circle with a triangle in the middle.

6.2.4.1 The Signal Start Event in Context

The signal start and throw events are generally added to a process and implemented by process developers.

6.2.5 Introduction to the Timer Start Event

The timer start event triggers the creation of a process instance based on a specific time condition. You can configure the timer start event to trigger a process instance based on the following: ■ A specific date and time. For example, a process could be triggered on December 31, at 11:59 PM. ■ A recurring interval. For example, a process could be triggered every 10 hours, 5 minutes, 32 seconds. Figure 6–8 shows the default notation for the timer start event. Figure 6–8 The Timer Start Event Modeling Business Processes with Oracle BPM 6-9 The timer start event is represented by two concentric circles with a clock in the middle.

6.2.6 Introduction to the None End Event

The none end event is used to mark the end of a process path. When a token reaches a none end event, it is consumed. If there are no other tokens within the process instance, the instance is complete. The none event is used when your process is not required to perform any action after it completes. It can also be used as a place-holder by process analysts, to be changed later during implementation by a process developer. Figure 6–9 shows the default notation for the none end event. Figure 6–9 The None End Event The none end event is represented by single circle. The none end event is always used to mark the end of a subprocess and event subprocess.

6.2.6.1 The None End Event in Context

Figure 6–10 shows an example of the none end event within the Sales Quote example process. In this example, the Sales Quote service task is used to perform the task of saving information about the sales quote to a database. Figure 6–10 The None End Event within the Sales Quote Example Process This figure shows an example of the none end event. It shows three separate flow objects: a user task, a service task, and the none end event. Since no other work must be performed when the token reaches the end of a process, a none end event is used. After all process tokens reach the none end event, the process instance completes.

6.2.7 Introduction to the Error End Event

The end error event is used when your the end of a process is the result of some error condition. Errors end events are normally used with the error boundary event. The error boundary event is used to alter the process flow based on a specific error. This flow usually ends using an error end event. See Section 6.8.3, Introduction to the Error Catch Event for more information on using the error intermediate event.