Try OpenEdge Now
skip to main content
Application Developer's Guide
Understanding the Business Process Server repository : Business Process Server event management : Event and CommonEvent class
 

Event and CommonEvent class

An event record contains the following information: event_id, type, value, date, and context_object. Type is a string that represents the origin of the event. An example of the type field is "BPServer". Event_id is the ID of the event. Process_instance_id is the ID of the process instance on which the event is sent. Value is a string that further specifies the semantics of each event. Examples of value include "PI_ACTIVATED" and "W_COMPLETED" which means "process instance activated" and "workstep completed" respectively.

Business Process Server events

The list of all events and their corresponding descriptions are presented in the following table:
Table 15. Business Process Server events
Event value
Event description
ID number
P_CREATED
A process template is created
1
P_INSTALLED
A process template is installed
2
P_REMOVED
A process template is removed
3
P_RESUMED
A process template is resumed
5
P_SUSPENDED
A process template is suspended
4
PI_CREATED
A process instance is created
6
PI_ACTIVATED
A process instance is activated
7
PI_SUSPENDED
A process instance is suspended
8
PI_RESUMED
A process instance is resumed
9
PI_COMPLETED
A process instance is completed
11
PI_PRIORITYSET
The priority of a process instance is changed
13
PI_DUEDATESET
The due date of a process instance is changed
14
PI_REMOVED
A process instance is removed
12
PI_CREATORSET
A process instance creator is set
51
PI_ATTRIBUTESET
Process instance attributes are set in bulk
41
PI_DATASLOTSSET
Process instance dataslots are set in bulk
42
W_CREATED
A workstep is created
15
W_ACTIVATED
A workstep is activated
18
W_SUSPENDED
A workstep is suspended
16
W_RESUMED
A workstep is resumed
17
W_COMPLETED
A workstep is completed
21
W_PRIORITYSET
The priority of a workstep is changed
22
W_DUEDATESET
The due date of a workstep is changed
23
W_PERFORMERSET
The performer of a workstep is changed
24
W_EVENTACTIVATION_WAIT
A monitoring workstep enters into wait state for an activation event.
91
I_CREATED
A workitem is created
25
I_ACTIVATED
A work item is activated
26
I_AVAILABLE
A work item is available
27
I_ASSIGNED
A work item is assigned
28
I_COMPLETED
A work item is completed
31
I_PRIORITY
A work item priority is changed
47
I_DUEDATE
A work item due date is changed
46
I_PERFORMER
A work item performer is changed
45
I_SUSPENDED
A work item is suspended
32
S_UPDATED
A dataslot is updated
33
EP_AFTERBREAK
Able to restart and resume the broken adapter
35
The event occurring time is stored in the date attribute as a long integer. The real event data is stored in the context attribute. The context is represented as a Map. A composite object can be represented using a Map from Java.

Event object example

An example of an event object is shown below.
EVENT_ID: 582
TYPE: BP Server
EVENT_TYPE: W_ACTIVATED
CREATE_DATE: Fri Sep 28 16:29:50 IST 2012 (This is converted from timestamp of long type)
PROCESS_TEMPLATE_ID: 40
PROCESS_INSTANCE_ID: 584
WORKSTEP_ID: 4
EVENT_CONTEXT_OBJ:
{APP_NAME=TestApp,
PROCESSTEMPLATENAME=TestApp,
PROCESSTEMPLATEID=40,
PROCESSINSTANCEID=584,
PROCESSINSTANCENAME=TestApp#584,
WORKSTEPNAME=Activity 3, WORKSTEPID=4,
TYPE=ATOMIC
MONITOR_STEP=false,
SBM_VERSION=9.0.0 (build #205),
STARTTIME=1348829989923,
PERFORMERVALUE=ebms,
DUEDATE=1348837189923,
PRIORITY=medium,
LOOPCOUNTER=1,
SESSION_USER=ebms,
RPID=0,
PERFORMER=@CREATOR,
ENDTIME=0,
ESTIMATEDDURATION=7200,
}