Event data specific to business processes

In business processes, processes, activities, scopes, links, and variables can send event data. 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.

Process

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 representation of the state of the process, for example 2 - STATE_RUNNING or 11 - STATE_WAITING
PayloadType The string full

Activity and scope

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. For example: 23 - KIND_RECEIVE or 21 - KIND_INVOKE.
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.
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 Information 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.

Link

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 Optional: A description of the link
PayloadType The string full

Variable

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 An XML representation of the content of the variable. The XML fragment is written into an extended data element of type hexBinary. The element type may be of type 'boolean' or 'string', with an appropriate value.
variableData_BO This element is of type "noValue" and contains an XML representation of the content of the variable. The XML fragment is written into an extended data element of type hexBinary.
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 Information 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.

Terms of use | | Broken links

Last updated: Tue Dec 06 04:14:40 2005

(c) Copyright IBM Corporation 2005.
This information center is powered by Eclipse technology (http://www.eclipse.org)