Sharing Roles Between Business Process Composer and BPM Studio

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. Modeling Business Processes with Oracle BPM 6-7 In this example, the process instance is created by the Enter Quote user task. This user task is implemented using the Initiator pattern.

6.2.2.2 Data Associations

The none start event does not accept process input arguments.

6.2.3 Introduction to the Message Start Event

The message start event triggers a process instance when a message is received. This message can be sent from another BPMN or BPEL process or from a service. Messages are types of data used for of exchanging information between processes. Just as data objects are used to define the data used within a project, messages are used to define the data used between processes or between a process and a service. Figure 6–5 shows the default notation of the message start event. Figure 6–5 The Message Start Event The message start event is represented by a single circle with a yellow envelope icon in the middle. Like other start events, the message start event cannot have incoming sequence flows. Message start events require a default outgoing sequence flow. You can exposed a BPMN process as service which enables other processes and applications to invoke the process. To expose a process as a service, your process must begin with a message start event. For more information see Communicating with Other BPMN Processes and Services in the Oracle Fusion Middleware Modeling and Implementation Guide for Oracle Business Process Management.

6.2.3.1 The Message Start Event in Context

Figure 6–6 shows a modified version of the Sales Quote process. Here, the process begins with a message start event which initiates the process instance. Figure 6–6 The Message Start Event within the Sales Quote Example Process This figure shows an example of a message start event. It shows two separate flow objects: a message start event which initiates the process instance script task which is used to initialize the values of data objects passed to the process.