Try OpenEdge Now
skip to main content
BPM Events User's Guide
Understanding BPM Events : The BP Server event protocol : Type and value of the event
 

Type and value of the event

The type of BP Server event is always "BP Server".
The value field of BP Server events depends on when the event was generated in the process. This field represents a more detailed classification of events of this type: it is usually used as a subtype. The most common events that BP Server processes generate have the values described in Table 9.
Table 9. Event values
Value
Description
PI_CREATED
Process instance created. Such an event is generated when the process instance is created in the process engine–but not yet started.
PI_ACTIVATED
Process instance activated. Such an event is generated when the process is initiated. At this time, some predefined initial values are known for some attributes (dataslots) of the process instance.
PI_PRIORITYSET
Process instance priority is set.
PI_DUEDATE
Process instance due date is set.
PI_ATTRIBUTESSET
Process instance attributes are set.
S_UPDATED
Slots updated. These events are generated when the dataslots of the process are updated.
PI_DATASLOTSSET
Process instance dataslots updated. Lists all dataslots, with name, type and value of each, whose value was changed during activation of the process instance.
PI_COMPLETED
Process instance completed. Such an event is generated when the process is terminated.
PI_REMOVED
Process instance removed. Such an event is generated when the process instance is removed. This event is similar to the PI_COMPLETED event, but it can happen at any time when the process instance is running and indicates that the process instance was aborted.
W_ACTIVATED
Workstep started. Each workstep of the process generates an activation event, including the Start workstep of the process.
W_PRIORITYSET
The priority of a workstep is set.
W_DUEDATESET
The due date of a workstep is set in a list of events.
W_COMPLETED
Workstep completed. At the end of each workstep, this event is generated.
I_CREATED
Work item created, as the result of assigning the workstep to a human performer. Note that a single work step can trigger several work items, in case there are multiple performers.
I_ASSIGNED
Work item assigned to a performer.
I_AVAILABLE
Work item available to a performer.
I_COMPLETED
Work item completed.
A sequence of events that is generated by the execution of a particular process instance is called the event-map of the process. A detailed description of an event-map is presented in Understanding event-maps.