ION OneView event types

Event type	Description
Message entered ION	This event is logged at the first moment the message is getting into ION through one of its components (such as Connection Points, Engines). This event represents the starting point for the message processing within ION.
Message sent to any connector or engine	This event is logged when a message is delivered to ION component(s) internal queue(s) that further processes this message.
Message consumed by any connector or engine	This event is logged when a message is delivered from the ION component internal queue to be processed by the receiver.
Message delivered by any connector or engine	This event is logged when a message is successfully processed by an ION component and the message is then delivered to the expected external receiver. For the Cloud 2.0 connector this event is generated when the message is delivered to the in-box of the Cloud application
Document updated	This event is logged when a message is updated by an ION component. This is mainly logged when using Database or web service Connection Points as intermediate steps and when using Workflow Activity in a document flow. Note: The original message that was sent to these connection points are not updated. A new message is created, based on that original document together with the updates done by the ION component. The new message is visible from ION OneView and its timeline is accessible.
Message listener inactive	This event is logged when a listener was active at the moment a message was picked up in ION, but the listener was deactivated before the message was delivered to the listener's in-box
Document triggered	This event is similar to "Document updated" or "Document mapped". It is logged for all trigger scenarios containing the original message id.
Message cannot be routed	This event is logged when the destination specified in the message `ToLogicalID` cannot be found. In this case, ION cannot send this message to any destination.
Confirm BOD generated	This event is logged when processing a message by one of ION components and an error occurs that causes the generation of a Confirm BOD. The new Confirm BOD message is visible from ION OneView and its timeline is accessible.
Confirm BOD stored	This event is logged when a Confirm BOD that was sent by one application or created by one of ION components during processing a BOD is stored in the Confirm BOD Engine.
Message resubmitted	This event is logged when an ION user resubmits a Confirm BOD from Connect > Error BODs page. The event is shown on the original time line of the source message id. The original message processing statuses are kept for tracing purposes.
Confirm BOD marked as handled	This event is logged when an ION user resubmits a Confirm BOD from Connect > Error BODs page and it is then automatically sent to Handled, or when an ION user selects a Confirm BOD from Connect > Error BODs page and manually marks it as `Handled`.
Confirm BOD marked as unhandled	This event is logged when an ION user selects a Confirm BOD from Connect > Error BODs and manually marks it as `Unhandled`.
Delivery Failed, retry started	This event is logged when an error occurs during the delivery of a message (for example, database is not accessible) and then ION component starts retrying to deliver the message.
Document does not match filter	This event is logged when an incoming message does not match any of the conditions configured in a Filter or a Content-Based Routing flow. In this case, the message is dropped.
Document matches filter	This event is logged when an incoming message matches a condition configured in a Filter or a Content-Based Routing flow.
Document mapped	This event is logged when a message is mapped by an ION component. This is mainly logged when using mapping activities in a document flow. Note: The original message that was sent to these mapping activities are not changed. A new message is created, based on the logic of the configured mapping. The new message is visible from ION OneView and its timeline is accessible.
Document Flow Triggered Workflow	This event is logged when a message is used to start a workflow from document flow. If the workflow started successfully, the workflow instance ID is available. Note: The original message that was used to start the workflow is not updated. A new message is created, based on that original document together with the updates done by the workflow. The new message is visible from ION OneView and its timeline is accessible.
Monitor Instance Triggered	This event is logged for every monitor that is interested in the document name of the incoming message. The monitor rule is evaluated based on the incoming message. If the rules evaluate to true, then an alert is created.
Alarm Template Triggered	This event is logged for every alarm template that was used in the alarm instance to evaluate the incoming document.
Activation Policy Instance Triggered	This event is logged for every activation policy that is interested in the document name of the incoming message. The activation policy rule is evaluated based on the incoming message. If the rules evaluate to true, then a workflow is started/cancelled based on the activation policy type and "`Activation Policy Started`" event is logged. If the rules do not evaluate to true, then no other events are logged.
Activation Policy started Workflow	This event is logged for every Activation Policy that is interested in the document name of the incoming message and its rules evaluation is true. This is based on the incoming message and a workflow instance was successfully created.
Activation Policy failed to start Workflow	This event is logged for every Activation Policy that is interested in the document name of the incoming message and its rules evaluation is true. This is based on the incoming message but a workflow instance failed to get created for some reason. For example: a workflow instance for the same document id already exists
Activation Policy Instance Completed	This event is logged for every Activation Policy that is monitoring the document name of the incoming message. The activation policy triggers the start/cancellation of a workflow. When this is workflow is completed / cancelled successfully, this event is logged.
Workflow Instance Created	This event is logged when the message causes the creation of a workflow instance. This is mainly done when a `ProcessWorkflow` message is processed that starts a workflow.
Workflow Instance Cancelled	This event is logged when the message causes the cancellation of a workflow instance. This is mainly done when a `ProcessWorkflow` message is processed that cancels a workflow.
Workflow Instance Failed	This event is logged when the message (`ProcessWorkflow`) causes the creation of a workflow instance and the execution of this workflow fails.
Workflow Instance Completed	This event is logged when the message (`ProcessWorkflow`) causes the creation of a workflow instance and the execution of this workflow is finished.
Pulse Item Created	This event is logged when the message causes the creation of an activity (Alert, Task and/or Notification). This is mainly done when a `ProcessPulseAlert` or `PulseNotification` or `ProcessPulseTask` message is processed by ION and an activity is created.
Pulse Item Changed	This event is logged when the message causes the creation of an activity (Alert, Task and/or Notification) and then this Pulse Item changed. For every change, the event is logged. This also happens if the message causes the cancellation of an activity. This is mainly done when a `ProcessPulseAlert` or `PulseNotification` or `ProcessPulseTask` message is processed by ION and an activity is cancelled.
Document was split	This event is logged when a document was split into a number of instances. This is mainly logged when the splitter activity was used in a document flow.

Message entered ION

This event is logged at the first moment the message is getting into ION through one of its components (such as Connection Points, Engines). This event represents the starting point for the message processing within ION.

Message sent to any connector or engine

This event is logged when a message is delivered to ION component(s) internal queue(s) that further processes this message.

Message consumed by any connector or engine

This event is logged when a message is delivered from the ION component internal queue to be processed by the receiver.

Message delivered by any connector or engine

This event is logged when a message is successfully processed by an ION component and the message is then delivered to the expected external receiver. For the Cloud 2.0 connector this event is generated when the message is delivered to the in-box of the Cloud application

Document updated

This event is logged when a message is updated by an ION component. This is mainly logged when using Database or web service Connection Points as intermediate steps and when using Workflow Activity in a document flow.

Note: The original message that was sent to these connection points are not updated. A new message is created, based on that original document together with the updates done by the ION component. The new message is visible from ION OneView and its timeline is accessible.

Message listener inactive

This event is logged when a listener was active at the moment a message was picked up in ION, but the listener was deactivated before the message was delivered to the listener's in-box

Document triggered

This event is similar to "Document updated" or "Document mapped". It is logged for all trigger scenarios containing the original message id.

Message cannot be routed

This event is logged when the destination specified in the message ToLogicalID cannot be found. In this case, ION cannot send this message to any destination.

Confirm BOD generated

This event is logged when processing a message by one of ION components and an error occurs that causes the generation of a Confirm BOD. The new Confirm BOD message is visible from ION OneView and its timeline is accessible.

Confirm BOD stored

This event is logged when a Confirm BOD that was sent by one application or created by one of ION components during processing a BOD is stored in the Confirm BOD Engine.

Message resubmitted

This event is logged when an ION user resubmits a Confirm BOD from > page. The event is shown on the original time line of the source message id. The original message processing statuses are kept for tracing purposes.

Confirm BOD marked as handled

This event is logged when an ION user resubmits a Confirm BOD from > page and it is then automatically sent to Handled, or when an ION user selects a Confirm BOD from > page and manually marks it as Handled.

Confirm BOD marked as unhandled

This event is logged when an ION user selects a Confirm BOD from > and manually marks it as Unhandled.

Delivery Failed, retry started

This event is logged when an error occurs during the delivery of a message (for example, database is not accessible) and then ION component starts retrying to deliver the message.

Document does not match filter

This event is logged when an incoming message does not match any of the conditions configured in a Filter or a Content-Based Routing flow. In this case, the message is dropped.

Document matches filter

This event is logged when an incoming message matches a condition configured in a Filter or a Content-Based Routing flow.

Document mapped

This event is logged when a message is mapped by an ION component. This is mainly logged when using mapping activities in a document flow.

Note: The original message that was sent to these mapping activities are not changed. A new message is created, based on the logic of the configured mapping. The new message is visible from ION OneView and its timeline is accessible.

Document Flow Triggered Workflow

This event is logged when a message is used to start a workflow from document flow. If the workflow started successfully, the workflow instance ID is available. Note: The original message that was used to start the workflow is not updated. A new message is created, based on that original document together with the updates done by the workflow. The new message is visible from ION OneView and its timeline is accessible.

Monitor Instance Triggered

This event is logged for every monitor that is interested in the document name of the incoming message. The monitor rule is evaluated based on the incoming message. If the rules evaluate to true, then an alert is created.

Alarm Template Triggered

This event is logged for every alarm template that was used in the alarm instance to evaluate the incoming document.

Activation Policy Instance Triggered

This event is logged for every activation policy that is interested in the document name of the incoming message. The activation policy rule is evaluated based on the incoming message. If the rules evaluate to true, then a workflow is started/cancelled based on the activation policy type and "

Activation Policy
								Started

" event is logged. If the rules do not evaluate to true, then no other events are logged.

Activation Policy started Workflow

This event is logged for every Activation Policy that is interested in the document name of the incoming message and its rules evaluation is true. This is based on the incoming message and a workflow instance was successfully created.

Activation Policy failed to start Workflow

This event is logged for every Activation Policy that is interested in the document name of the incoming message and its rules evaluation is true. This is based on the incoming message but a workflow instance failed to get created for some reason. For example: a workflow instance for the same document id already exists

Activation Policy Instance Completed

This event is logged for every Activation Policy that is monitoring the document name of the incoming message. The activation policy triggers the start/cancellation of a workflow. When this is workflow is completed / cancelled successfully, this event is logged.

Workflow Instance Created

This event is logged when the message causes the creation of a workflow instance. This is mainly done when a ProcessWorkflow message is processed that starts a workflow.

Workflow Instance Cancelled

This event is logged when the message causes the cancellation of a workflow instance. This is mainly done when a ProcessWorkflow message is processed that cancels a workflow.

Workflow Instance Failed

This event is logged when the message (ProcessWorkflow) causes the creation of a workflow instance and the execution of this workflow fails.

Workflow Instance Completed

This event is logged when the message (ProcessWorkflow) causes the creation of a workflow instance and the execution of this workflow is finished.

Pulse Item Created

This event is logged when the message causes the creation of an activity (Alert, Task and/or Notification). This is mainly done when a ProcessPulseAlert or PulseNotification or ProcessPulseTask message is processed by ION and an activity is created.

Pulse Item Changed

This event is logged when the message causes the creation of an activity (Alert, Task and/or Notification) and then this Pulse Item changed. For every change, the event is logged. This also happens if the message causes the cancellation of an activity. This is mainly done when a ProcessPulseAlert or PulseNotification or ProcessPulseTask message is processed by ION and an activity is cancelled.

Document was split

This event is logged when a document was split into a number of instances. This is mainly logged when the splitter activity was used in a document flow.