Adding Roles and Swimlanes to Your Process

6-6 Modeling and Implementation Guide for Oracle Business Process Management process. See Section 6.2.7, Introduction to the Error End Event for more information. ■ Terminate end event: The terminate end event causes all work on a process to stop immediately. There is no error handling or other clean up of the running process. See Section 6.2.9, Introduction to the Terminate End Event for more information.

6.2.2 Introduction to the None Start Event

The none start event is used when no instance trigger is defined. Process analysts can use the none start event as a placeholder when the necessary start event of a process is unknown or is defined and implemented later by process developers. Figure 6–3 shows the default notation for the none start event Figure 6–3 The None Start Event The none start event is represented by single circle. None start events are also used to specify the beginning of a process where the process instance is created by another flow object. Although the none start event does not trigger the creation of a process instance, it is required when triggering a process instance using the following flow objects: ■ Receive task. The receive task must have the Create Instance property set to true. ■ User task implemented with the initiator pattern Like other start events, the none start event cannot have incoming sequence flows. It can only have default out-going sequence flows.

6.2.2.1 The None Start Event in Context

Figure 6–4 shows an example of the none start event within the Sales Quote example project. In this example, the none start event defines the start of the process. Additionally, since the process contains a user task implemented with the initiator pattern, the none start event triggers a process instance. Figure 6–4 The None Start Event within the Sales Quote Example Process This figure shows an example of the none start event. It shows three separate flow objects: a none start event, a script task, and a user task implemented with the initiator pattern. Note: None events are always used to define the beginning of subprocesses.