Event Manager

The Event Manager sub-tab shows the runtime logging messages that were triggered due to orchestration events or ALF events, including the source of the event, the time the event occurred, and the user who caused the event to be raised.

On the Event Manager sub-tab, you can:

Create, edit, and delete custom filters that limit the number of messages in the log. You can search messages by the event ID, time, type, orchestration name, product and more. For more information, see Working with Logs.
Retry failed events, which is critical in situations where processing of asynchronous orchestration events must be guaranteed. To retry a failed event, select an event whose status is Failure, and then click Retry. This will reprocess all failed orchestration workflows invoked by this event. For more information about retrying events, see the SBM Orchestration Guide.
Click Purge History to clear the history of events.
Click the refresh icon to update the list with the latest entries.

The following high-level information is available for each event:

Column	Description
Event ID	The unique ID of 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.
Object Type	The object type that together with the event type, defines this mapping to the Event Manager. The object type identifies the type of object or record that triggers the event type.
Status	The status of the event: Received: No orchestration workflows are mapped to the event, or the orchestration workflows mapped to the event were not created due to a system failure. Started: The orchestration workflow processing started. Complete: The orchestration workflow processing completed successfully. Failed: At least one orchestration workflow associated with the event failed. Unknown: The status cannot be determined due to a bad event ID or missing event processing data.
Logged On	The date and time the event was logged.
Logged By	The user who logged the event.
Last Processed On	The last time the event was processed.
Attempts	The number of attempts that have occurred.