Draft comment: This topic only applies to BAW, and is located in the BAW repository. Last updated on 2025-03-13 12:15
Events are emitted for scope activities if monitoring is requested for these activities
in IBM® Integration
Designer. 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.
Event name
The name of the event.
The
following table describes all scope activity events.
Table 1. Scope activity events
Code
Event name
Description
42020
SCOPE_STARTED
Scope started. This event is emitted when the navigation enters the scope
instance.
42021
SCOPE_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.
Draft comment: what does dead-path elimination apply to - the navigation or the
scope?
42022
SCOPE_FAILED
Scope failed. This event is emitted when the process navigation leaves the
fault handler of the scope.
42023
SCOPE_FAILING
Scope failing. This event is emitted when the process navigation enters
the fault handling path of the scope.
42024
SCOPE_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
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
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
Scope compensated. This event is emitted when the compensation handler,
including default compensation handler, of the scope completes.
42045
SCOPE_COMPENSATION_FAILED
Scope compensation failed. This event is emitted if a fault occurs when
the compensation handler for the scope runs.
42048
SCOPE_EVENT_RECEIVED
This event is emitted when a new event handler instance is started for
the scope.
42051
SCOPE_EVENT_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
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
Scope is force completed
42068
SCOPE_FORCE_RETRIED
Scope has been force retried
42076
SCOPE_CONDITION_FORCED
An activity that has stopped because of an error evaluating a join
condition was forced to continue navigating.
This topic only applies to BAW, and is located in the BAW repository. Last updated on 2025-03-13 12:15