Page Comparison

A business process is typically a collection of related and structured activities or tasks, that depicts a business use case and produces a specific service or output. For example, a banking customer requesting a bank load and getting loan approval is a simple process. An instance of this process is a specific example of this process workflow. So, Mr. Smith requesting for 50,000 USD and getting approval for it is an instance of the "bank loan approval" process. Every time a banking customer makes a request for a loan, that request triggers a new process instance in the BPM system, which flows through the elements of the process workflow according to its design.

...

The second column specifies whether an event is associated with the process itself or with one of its scopes. The event type is used for filtering events.

Filtering Events

Process-Level Filtering

Using the It is possible to tweak event generation to filtrate which ones get created. First, events can be filtered at the process level by having filters in the process deployment descriptor inside the <dd:deploy> element.

Process-Level Filtering

Process level event filtering can be done using one of the following stanza:

...

This configuration allows the generation of all the events of an execution. This can be achieved by not adding any event filterings also since this is the default behavior.

<dd:process-eventsgenerate="all"/>
    <!-- Default configuration -->
    

With this configuration, no events are generated. This configuration provides a performance gain also.

 <dd:process-eventsgenerate="none"/>
    

This form allows you to define types of events that are generated. One or more following event types are allowed here: instanceLifecycle, activityLifecycle, dataHandling, scopeHandling, correlation

<dd:process-events>
        	<dd:enable-event>dataHandling</dd:enable-event>
        	<dd:enable-event>activityLifecycle</dd:enable-event>
</dd:process-events>

The first form just duplicates the default behavior; when nothing is specified in the deployment descriptor, all events are generated. The third form lets you define which types of events are generated. The possible types are: 

...

Scope-Level Filtering

It is also possible to define filtering for each scope of the process. This overrides the settings defined in the process. In order to define event filtering on a scope, the scope activity MUST have a name in your process definition. Scopes are referenced by name in the deployment descriptor:

...