For modelling a process you have to configure your Jdeveloper 11g like shown in this posting. Then you can create easliy a process like this one:
[The behaviour of the tool palette is a little bit weird, because you can not use drag&drop. You have to click an item and then move the mouse inside the graph. Then the item is beneath the mouse cursor and you can place it with a second click.]
The start event can be changed via right mouse click:
[The start event with the envelope is called "message start event"]
Here an excerpt from the official documentation about the start events:
The start event can be changed via right mouse click:
Here an excerpt from the official documentation about the start events:
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. 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:The following end events can be used: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.
- Receive task. The receive task must have the Create Instance property set to true.
- User task implemented with the initiator pattern
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.
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 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.
- None end event
like start event - Error end event
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. - Message end event
like start event - 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.
