Common Base Events for scope activities

IBM BPM, V8.0.1, All platforms > Measuring and improving business processes > Monitoring > Event catalog > Business Process Choreographer events > BPEL process events overview > Business process events
Common Base Events for scope activities

Common Base Events are emitted for scope activities if monitoring is requested for these activities in IBM Integration Designer. A list of all the events that can be emitted by an activity scope can be found here. These events are also written to the audit log.

State transitions and events for scope activities

The following diagram shows the state transitions that can occur for a scope activity and the events that are emitted when these state changes take place.
Figure 1. State transitions and events for scope activities

Scope activity events

The columns in the following table contain:

Code

Contains the number of the event. For Business Monitor 6.0.2 format events, the value is written to the Common Base Event as an extended data element with the name BPCEventCode. For Business Monitor 6.1 format events, the value is written to the xs:any slot of the Common Base Event.

Event name and extension name

This column contains two values. The name of the event and the value that is set in the extensionName attribute of the Common Base Event. The extension name identifies which event specific information is contained in the Common Base Event, and it is also the name of the XML element that provides additional data about the event.

Situation

Refers to the situation name of the BPEL process event.

Event nature

A pointer to the event situation for a BPEL process element in the EventNature parameter, as they are displayed in IBM Integration Designer.

The following table describes all scope activity events.

Scope activity events
Code Event name and extension name Situation Event nature Description
42020
SCOPE_STARTED

BPC.BFM.ACTIVITY.
STATUS
Start ENTRY Scope started. This event is emitted when the navigation enters the scope instance.
42021
SCOPE_SKIPPED

BPC.BFM.ACTIVITY.
STATUS
Report SKIPPED Scope skipped. The event applies only to scope activities that have join behavior defined. The event is emitted when the join condition of the scope evaluates to false. The navigation of the process continues at the end of the scope with dead-path elimination.
42022
SCOPE_FAILED

BPC.BFM.ACTIVITY.
FAILURE
Fail FAILED Scope failed. This event is emitted when the process navigation leaves the fault handler of the scope.
42023
SCOPE_FAILING

BPC.BFM.ACTIVITY.
STATUS
Report FAILING Scope failing. This event is emitted when the process navigation enters the fault handling path of the scope.
42024
SCOPE_TERMINATED

BPC.BFM.ACTIVITY.
STATUS
Stop TERMINATED Scope terminated. A scope activity can be terminated if the associated process is terminated, for example, by a terminate activity in a branch that is parallel to the scope activity.
42026
SCOPE_COMPLETED

BPC.BFM.ACTIVITY.
STATUS
Stop EXIT Scope completed. This event is emitted when the normal navigation path of the scope and all of the activated event handler paths are completed.
42043
SCOPE_COMPENSATING

BPC.BFM.ACTIVITY.
STATUS
Report COMPENSATING Scope compensating. This event is emitted when the process navigation enters the compensation handler, including the default compensation handler, of the scope.
42044
SCOPE_COMPENSATED

BPC.BFM.ACTIVITY.
STATUS
Stop COMPENSATED Scope compensated. This event is emitted when the compensation handler, including default compensation handler, of the scope completes.
42045
SCOPE_COMPENSATION_
FAILED

BPC.BFM.ACTIVITY.
STATUS
Fail COMPFAILED Scope compensation failed. This event is emitted if a fault occurs when the compensation handler for the scope runs.
42048
SCOPE_EVENT_
RECEIVED

BPC.BFM.ACTIVITY.
EVENT
Report EV_RECEIVED This event is emitted when a new event handler instance is started for the scope.
42051
SCOPE_EVENT_
ESCALATED

BPC.BFM.ACTIVITY.
ESCALATED
Report EV_ESCALATED Scope event escalated. This event is emitted when the escalation is started that is associated with the inline human task of an active event handler for the scope.
42066
SCOPE_STOPPED
BPC.BFM.ACTIVITY.STATUS
Stop STOPPED Scope is stopped. A scope instance can stop if an unhandled fault occurs during the activation or the follow-on navigation of a scope.
42067
SCOPE_FORCE_
COMPLETED

BPC.BFM.ACTIVITY.
STATUS
Report FCOMPLETED Scope is force completed
42068
SCOPE_FORCE_RETRIED

BPC.BFM.ACTIVITY.
STATUS
Report FRETRIED Scope has been force retried
42076
SCOPE_CONDITION_
FORCED

BPC.BFM.ACTIVITY.
CONDITIONFORCED
Report SCOPE_ CONDITION_ FORCED An activity that has stopped because of an error evaluating a join condition was forced to continue navigating.

Activity scope events are a type of activity event, whose syntax was described earlier for BPC.BFM.ACTIVITY.STATUS.
For activity scope events, the following event correlation sphere identifiers have the following content:

The ECSCurrentID provides the ID of the scope.
The ECSParentID provides the ID of the containing process.

Business process events

Related reference:
Event data specific to BPEL processes
Situations in BPEL process events
Extension names for BPEL process events

Code	Event name and extension name	Situation	Event nature	Description
42020	SCOPE_STARTED BPC.BFM.ACTIVITY. STATUS	Start	ENTRY	Scope started. This event is emitted when the navigation enters the scope instance.
42021	SCOPE_SKIPPED BPC.BFM.ACTIVITY. STATUS	Report	SKIPPED	Scope skipped. The event applies only to scope activities that have join behavior defined. The event is emitted when the join condition of the scope evaluates to false. The navigation of the process continues at the end of the scope with dead-path elimination.
42022	SCOPE_FAILED BPC.BFM.ACTIVITY. FAILURE	Fail	FAILED	Scope failed. This event is emitted when the process navigation leaves the fault handler of the scope.
42023	SCOPE_FAILING BPC.BFM.ACTIVITY. STATUS	Report	FAILING	Scope failing. This event is emitted when the process navigation enters the fault handling path of the scope.
42024	SCOPE_TERMINATED BPC.BFM.ACTIVITY. STATUS	Stop	TERMINATED	Scope terminated. A scope activity can be terminated if the associated process is terminated, for example, by a terminate activity in a branch that is parallel to the scope activity.
42026	SCOPE_COMPLETED BPC.BFM.ACTIVITY. STATUS	Stop	EXIT	Scope completed. This event is emitted when the normal navigation path of the scope and all of the activated event handler paths are completed.
42043	SCOPE_COMPENSATING BPC.BFM.ACTIVITY. STATUS	Report	COMPENSATING	Scope compensating. This event is emitted when the process navigation enters the compensation handler, including the default compensation handler, of the scope.
42044	SCOPE_COMPENSATED BPC.BFM.ACTIVITY. STATUS	Stop	COMPENSATED	Scope compensated. This event is emitted when the compensation handler, including default compensation handler, of the scope completes.
42045	SCOPE_COMPENSATION_ FAILED BPC.BFM.ACTIVITY. STATUS	Fail	COMPFAILED	Scope compensation failed. This event is emitted if a fault occurs when the compensation handler for the scope runs.
42048	SCOPE_EVENT_ RECEIVED BPC.BFM.ACTIVITY. EVENT	Report	EV_RECEIVED	This event is emitted when a new event handler instance is started for the scope.
42051	SCOPE_EVENT_ ESCALATED BPC.BFM.ACTIVITY. ESCALATED	Report	EV_ESCALATED	Scope event escalated. This event is emitted when the escalation is started that is associated with the inline human task of an active event handler for the scope.
42066	SCOPE_STOPPED BPC.BFM.ACTIVITY.STATUS	Stop	STOPPED	Scope is stopped. A scope instance can stop if an unhandled fault occurs during the activation or the follow-on navigation of a scope.
42067	SCOPE_FORCE_ COMPLETED BPC.BFM.ACTIVITY. STATUS	Report	FCOMPLETED	Scope is force completed
42068	SCOPE_FORCE_RETRIED BPC.BFM.ACTIVITY. STATUS	Report	FRETRIED	Scope has been force retried
42076	SCOPE_CONDITION_ FORCED BPC.BFM.ACTIVITY. CONDITIONFORCED	Report	SCOPE_ CONDITION_ FORCED	An activity that has stopped because of an error evaluating a join condition was forced to continue navigating.