Try OpenEdge Now
skip to main content
BPM Events User's Guide
The rule language : Rule structure : Event variables and expressions : Event attributes
 
Event attributes
The Condition and Action parts of a rule can share event variables. Event variables are any string of characters (letters or digits), with no space between characters. Event variables usually appear in event expressions that represent attribute values. For example, given an event variable EVT_1, each expression below returns the value of some event attribute. The type of all these attributes is String, except for the date attribute, which is of type Date. Conversion rules are detailed further.
*EVT_1.type (for example, purchase order event for purchase order XML message)
*EVT_1.value (optional—to refine the type)
*EVT_1.date (date when the event was generated)
*EVT_1.name (an attribute that is specific to this type of event)
In the last example, you may also write the expression: EVT_1.context.name, as the attribute "name" is not a standard event attribute, but actually belongs to the context of the event. This context may vary from one event to the other. The context object is itself a (complex) attribute of the event object, which has in turn possibly several attributes.
Note: The mention of the "context" can be omitted most of the time, as an attribute name that is different from other standard event attributes ("type", "value", "date") is automatically considered as an attribute of the event context. Context applies only to event, not to XML messages.
The event description in the rule header: <evt variable> of <evt type>::<evt subtype>{activation filter} actually refers to specific attributes of the event object:
*<evt type> must match the "type" attribute of the event (EVT_1.type)
*<evt subtype> must match the "value" attribute of the event (EVT_1.value)
Note: The {activation filter} must match the WORKSTEPNAME and PROCESSTEMPLATENAME of the event.
For example, the event header: EVT_1 of BP Server::W_COMPLETED{WORKSTEPNAME : "Start", PROCESSTEMPLATENAME : "Assign_A_Task_V2" selects every event "EVT_1" such as EVT_1.type = "BP Server" , EVT_1.value = "W_COMPLETED".