In business processes, events relate to processes, activities, scopes, links, and variables. The object-specific content of each of these event types is described.
If not specified otherwise, the object-specific content is written as extendedDataElement XML elements of type string.
Events of process instances have the following object-specific event content:
Attribute | Description |
---|---|
processTemplateName | The name of the process template from which the instance was derived |
processTemplateValidFrom | The date from which the template is valid |
processTemplateId | The identifier of the process template |
processInstanceDescription | Optional: The description of the process instance |
processInstanceExecutionState | A string value that represents the state of the process.
It has the format: state number-state description.
This attribute can have one of the following values: 1 - STATE_READY |
PayloadType | The string full |
Activities and scopes have the following object-specific event content:
Attribute | Description |
---|---|
processTemplateName | The name of the process template from which the instance was derived. |
processTemplateValidFrom | The date from which the template is valid. |
activityTemplateName | Optional: The name of the activity template from which the instance was derived. |
activityInstanceDescription | Optional: The description of the activity instance. |
activityKind | A string value that identifies the activity kind. This
value has the format: kind number-kind description.
This attribute can have one of the following values: 3 - KIND_EMPTY |
state | A string value that represents the state of the activity.
It has the format: state number-state description.
Note that the state codes for activities are different from those used for
processes. This attribute can have one of the following values: 1 - STATE_INACTIVE |
bpelId | A string value that represents the wpc:id attribute of the activity. |
PayloadType | The payload type. The value of the string can be one of: none, digest, or full. The value depends on the setting in WebSphere Integration Developer and whether business object (BO) content is written to the event. If an event does not contain a business object, the value is always set to full. |
Links have the following object-specific event content:
Attribute | Description |
---|---|
processTemplateName | The name of the process template from which the instance was derived |
processTemplateValidFrom | The date from which the template is valid |
flowBpelId | A string value that represents the wpc:id attribute of the flow activity that contains the link |
elementName | The name of the link that was evaluated |
description | A description of the link. This attribute is only included if specified in the process model. |
PayloadType | The string full |
Variables have the following object-specific event content.
Attribute | Description |
---|---|
processTemplateName | The name of the process template from which the instance was derived. |
processTemplateValidFrom | The date from which the template is valid. |
variableName | The name of the variable that was changed. |
variableData | Emitted when WBI Monitor compatible events are requested. An XML representation of the content of the variable. Each property of the data object is reported in the form of a nested extended data element. The element type may be of type 'boolean' or 'string', with an appropriate value. |
variableData_BO | Emitted when non-WBI Monitor compatible events are requested. This element is of type 'noValue' and contains an XML representation of the content of the variable. Each property of the data object is reported in the form of a nested extended data element. |
bpelId | A string value that represents the wpc:id attribute of the activity. |
PayloadType | The payload type. The value of the string can be one of: none, digest, or full. The value depends on the setting in WebSphere Integration Developer and whether business object content is written to the event. If an event does not contain a business object, the value is always set to full. |
(c) Copyright IBM Corporation 2005, 2006.
This information center is powered by Eclipse technology (http://www.eclipse.org)