By Juergenkress-Oracle on Oct 10, 2015
End events define how a process should finish and just like with start events, processes can have more than one end event.
As you can see from the sample process below, we are provided with a plethora of end events that include a “None End” event, a “Message Send” event, a “Signal” event and a “Terminate End” and “Error End” event.
The “None End” event is the default end event in a manual and reusable process and as it’s name implies, it is used when your process doesn’t need to perform any action upon completion. When all process instance tokens reach the “None End” event, the instance is completed.
The "Message End" event, as the name implies, will send a message before an instance completion and is especially useful when you want to trigger another process or instance. The "Message End" event has one unique particularity, it can only be used with either a message start event or a message catch event.
The "Signal Event" will publish a signal before completion.
The "Terminate End" is used to terminate, immediately, without any error handling, a process.
The "Error End" will throw an error before completion. This type of end event is used most commonly in subprocesses to trigger an exception to a main process.
Let's see how you can use these end events in practice.
Create the basic BPM application and BPM project (named both application and project "EndEventsDemo") and select "Composite with BPMN Process" in step 3. Read the complete article here.
For regular information on Oracle SOA Suite become a member in the SOA & BPM Partner Community for registration please visit www.oracle.com/goto/emea/soa (OPN account required) If you need support with your account please contact the Oracle Partner Business Center.