Try OpenEdge Now
skip to main content
BPM Events User's Guide
BPM Events tutorial : Using rules to monitor an application : Events generated by the application
 

Events generated by the application

After defining the report, you must write additional BPM Events rules to populate it. These rules capture events generated by BP Server while executing the application process. It is important to understand these events.
All events, whether sent by BP Server or by an adapter connected to third party software, have the following structure:
(type, date, value, context)
Table 5 describes the elements of this structure.
Table 5. Event elements
Element
Description
Type
Used as a main discriminator for events. This attribute identifies either the source of the event, such as "BP Server" or the type of a major event, such as "NewSubscription."
Note: Business Process Server includes a few predefined types, two of which are "BP Server" and "initRules." The set of possible values for type is open; you decide on the value of this attribute when creating new events.
Date
The timestamp of the event. You can choose the precision level from day to millisecond.
Value
An attribute that further qualifies the event, and is used as a second-level discriminator for events. For instance, the value of a BP Server event depends on the type of action that generated it such as starting a process, ending a workstep, or changing a dataslot. Typically, for a given event type, there exists a set of predefined values for value.
Context
A list of name-value pairs specific to an event type and value. It represents any additional business data of interest for this event. It may, for example, contain a mapping of complex business objects that we want to associate with the event, such as a purchase order. Some of the information kept in the context field include the following:
*PROCESSINSTANCENAME
*PROCESSTEMPLATENAME
*WORKSTEPNAME
*PERFORMER