The None Start Event in Context

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. 6-10 Modeling and Implementation Guide for Oracle Business Process Management Figure 6–11 shows the default notation for the error end event. Figure 6–11 The Error End Event The error end event is represented by two concentric circles with a lightning bolt in the middle. For information implementing the error end event, see the Oracle Fusion Middleware Modeling and Implementation Guide for Oracle Business Process Management.

6.2.8 Introduction to the Message End Event

The message end event is used to send a message to another process or service when the process is completed. The message end event is always used with either a message start event or message catch event. Figure 6–12 shows the default notation for the message end event. Figure 6–12 The Message End Event The message end event is represented by single circle with a yellow envelope in the middle. For information on how implement message throw events, see Communicating With Other BPMN Processes and Services Using Message Events in the Oracle Fusion Middleware Modeling and Implementation Guide for Oracle Business Process Management.

6.2.9 Introduction to the Terminate End Event

The terminate end event is used to immediately terminate a process. When a terminate end event is reached, the process ends immediately. There is no error handling or additional clean up performed.

6.3 Adding User Interaction to Your Process

Most business applications require interaction from process participants within your organization. This interaction can be as simple as entering information into a form or can involve multiple work flows and multiple users. This section describes the BPMN flow objects that are used to model how process participants interact with your business processes. Note: When creating a process that has multiple end events, you must ensure that any tokens that reach a message end event were created by a message start. For example, you cannot use a message end event to end a process instance initiated by a timer start.