Event Summary

The Event Summary sub-tab displays additional details of the event, including:

Field Description
Event ID A unique identifier for the event.
Event Type The event type that together with the object type, defines this mapping to the Event Manager. The event type identifies what occurs to trigger the event. If the event is defined in SBM Composer for the Application Engine, it is constructed using application, state, and transition names.
Environment Type The name of the environment in which the event was raised.
Object ID A unique identifier for the application that launched the event.
Object Type A string with the name of the application that launched the event.
Status The processing status of the orchestration workflow triggered by the event.
Preceding Event ID A link to the event that preceded this event.
Orchestration Name The name of the orchestration containing the workflow triggered by the event.
Product Name A string identifying the name of the application workflow that contained the transition from which the event was triggered.
Tool Version A string identifying the version of the application workflow that contained the transition from which the event was triggered.
Product Instance If there is a string identifying a particular instance of the application workflow containing the transition from which the event was triggered, that string is listed here.
Event Details A string specifying details of the event. Created by the tool or application launching the event.
Logged On The date and time when the event was logged.
Logged By The user under whose ID the event was triggered.
Last Processed On The date and time the last attempt was made.
Attempts The number of times the Event Manager tried to match the event to an orchestration workflow. Currently, this value is always "1."
Product Callback URI The Web service endpoint for tools that support callbacks from orchestration workflows for additional information. The element content is optional for transient tools that might not be running at a later time, and so cannot accept a callback. Constantly running (server) tools that support callbacks should supply a URI.
Log Logs from the orchestration workflow associated with this event. Each orchestration workflow instance that runs from the event should log at least a [BEGIN] message and an [END] message. The [END] message indicates if the orchestration workflow succeeded or failed. A success is indicated with an [OK] message. A failure is indicated by an ERROR message and the text of the exception or SOAP fault that occurred. The text of the SOAP fault is always captured; for certain types of SOAP faults, the message text is also extracted. The message text is truncated if it is over a certain size.