During event notification, the adapter converts XML Activity Invocation Request messages sent by Workflow to business objects which are then published to the broker.
Before publishing the business object, the adapter populates the ObjectEventId with the External Process Context identifier passed by Workflow, in bold in the following Workflow message fragment:
<WfMessage> <ActivityImplInvoke> <ExternalProcessContext>XXXX</ExternalProcessContext>
If no value is defined, the adapter will instead populate the ObjectEventId with the Process identifier passed by workflow in the message:
<WfMessage> <ActivityImplInvoke> <ProgramInputData> <_PROCESS>XXXX</_PROCESS>
If no value is defined for either of the above identifiers, the ObjectEventId will be left undefined when posted to the broker.
When the adapter receives requests to execute/start a workflow, it will, by default, attempt to include an External Process Context identifier in the request message sent to Workflow. If attribute, ExternalProcessContext, is defined and populated in the Process Template Config meta-object included in the request business object, this user-supplied value will be specified as the External Process Context identifier. If no such value exists in the meta-object, the adapter will check the ObjectEventId and use this value instead. If a value cannot be found in either location, the adapter will not include an element for the External Process Context identifier in the message sent to Workflow.
If provided, value will be included in message to Workflow as follows:
<WfMessage> <WorkflowProcess...> <ExternalProcessContext>XXXX</ExternalProcessContext>