ION OneView event types
During the processing of messages within ION, events are logged by ION components handling the messages. All events have these properties by default:
- Event Type
- Event Description
- Creation Date-Time (UTC)
The table lists the currently logged events:
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. This event is logged also when an initially marked message as "no route" is resent from the Active Connection Points management page. |
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. |
Document Updated | This event is logged when a message is updated by an
ION component. This is
mainly logged when using Database or Webservice 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 as well.
|
Message migrated to Infor Data Lake |
This event is logged when a message is migrated into the Infor Data Lake. |
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 that is 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 as well. |
Confirm BOD stored | This event is logged when a Confirm BOD that was sent by an application or was 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 timeline 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 the page and it is automatically sent to Handled. Or when an ION 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 page 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, the database is not accessible. Then the 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 | user selects a Confirm 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 merged |
This event is logged when a document was merged with another document in a document flow. Merge can be done in a simple way or using an advanced technique such as scripting. This event is shown for the last merge component on the timeline view. The event details contain information of the both input merged document. |
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,
that is based on that original document, together with the updates
that are 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, a workflow is started or cancelled based on the activation policy type. An "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 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 Notification) and then this activity
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 several instances. This is mainly logged when the splitter was used in a document flow. |
Retrieved from Data Lake | This event is logged when a scheduled retrieval from Data Lake occurs of an instance of the same data object. |
Purged from Data Lake | This event is logged when a document was successfully purged from Data Lake. |
Document Processed by script | This event is logged when a document was processed by a script from one document to another document. |
Document warning too large | This event is logged when the message size violates the license agreement. This preemptive event is only used during the introduction of this new license validation (July 2020). |
Document blocked too large | This event is logged when the message processing was blocked, because the message size violates the license agreement. |