ASM GAIA 10.4

Using Events

This section describes what happens when an event transaction is received by ASM.

Incoming Transactions

Receive Transaction

When receiving a receive event transaction, ASM:

  1. Runs through the groups specified on the event type, in the specified order.

  2. For each group, it runs through the mappings in the specified order and evaluates the criteria specified in each mapping to determine whether to apply this mapping.

  3. Applies the first applicable mapping in the configured order. A mapping is applicable to an event if the configured criteria are satisfied, or the mapping is marked as being the default mapping.

  4. It is possible that some events do not get matched. Any non-default mappings ranked after a default mapping will never be applied. It is therefore important to position non-default mappings above the default mapping for an event type.

  5. Undertakes the action specified in the When Received field on the Event Type Mapping Details window. If No action is selected, the event is ignored but it is still recorded in the Activity log. If Log Call or Log Request is selected, the following happens:

    • A call or request is logged within ASM using the call or workflow template specified in the Event Type Mapping Details window.

    • The logging analyst of the call or request is set to the analyst specified on the Event Type Mapping Details window.

    • If a User and organization are specified on the Fields - Incoming tab of the Event Type Mapping Details window, they are used to populate the corresponding fields on the call or request, even if there is already a User and organization specified on the call or workflow template.

    • An acknowledge transaction is sent following the rules specified on the Action tab of the Event Type Mapping Details window.

    • An outage is automatically created on the CMDB item(s) linked to the call or request according to the rules specified on the Outages tab of the Event Type Mapping Details window.

    • The call or request is forwarded to the analyst and group defined on the call or workflow template. If the template does not have a pre-assigned analyst or group, the call or request is forwarded to the logging analyst specified on the Event Type Mapping Details window. If the logging analyst specified on the Event Type Mapping Details window does not have call or request ownership rights (as part of the analyst’s security roles), then the call or request is sent to the creator of the call or workflow template.

  6. If the receive transaction contains a ASM call or request reference that corresponds to an existing call or request in ASM, this transaction is handled as an update transaction (see below).

Update Transaction

When receiving an update event transaction, ASM:

  1. Undertakes the action specified in the When Updated externally fields on the Event Type Mapping Details window.

  2. Updates any fields specified on the Fields - Incoming mapping to update Always.

  3. Updates the Events browse table on the call or request with the details of the transaction.

  4. If the update transaction states that the event has been closed in the external system, ASM handles this event transaction according to the rules specified in the When Deleted externally fields on the Event Type Mapping Details window.

  5. If this transaction has an event reference or a call or request reference that is not recognized by ASM, the rules specified for receive transactions are applied.

Notify Transaction

When receiving a notify event transaction, ASM:

  1. Undertakes the action specified in the When Notified externally fields on the Event Type Mapping Details window.

  2. Updates any fields specified on the Fields - Incoming mapping to update Always.

  3. Updates the Events browse table on the call or request (see Viewing Event Transactions from a Call or Request) with the details of the transaction.

  4. If this transaction has an event reference or a call or request reference that is not recognized by ASM, no action is taken on the event.

Resolve Transaction

When receiving a resolve event transaction, ASM:

  1. Undertakes the action specified in the When Resolved externally fields on the Event Type Mapping Details window.

  2. Updates any fields specified on the Fields - Incoming mapping to update Always.

  3. Updates the Events browse table on the call or request (see Viewing Event Transactions from a Call or Request) with the details of the transaction.

  4. Closes any outage created on the CMDB item(s) linked to the call or request according to the rules specified on the Outages tab of the Event Type Mapping Details window.

  5. If this transaction has an event reference or a call or request reference that is not recognized by ASM, no action is taken on the event.

Delete Transaction

When receiving a delete event transaction, ASM:

  1. Undertakes the action specified in the When Deleted externally fields on the Event Type Mapping Details window.

  2. Updates any fields specified on the Fields - Incoming mapping to update Always.

  3. Updates the Events browse table on the call or request (see Viewing Event Transactions from a Call or Request) with the details of the transaction.

  4. Closes any outage created on the CMDB item(s) linked to the call or request according to the rules specified on the Outages tab of the Event Type Mapping Details window.

  5. If this transaction has an event reference or a call or request reference that is not recognized by ASM, no action is taken on the event.

Outgoing Transactions

This section describes what happens when an event transaction is sent by ASM.

Update Transaction

When an analyst updates a call or request logged as a result of an event (that is, saves, defers and forwards the call or request), ASM:

  1. Sends an update transaction to the external system if the rule specified in the Action tab on the Event Type Mapping Details window says to send an update transaction on call or request update.

  2. Attaches the contents of the Actions & Solutions field on the call or request to the update transaction sent to the external system.

  3. Updates any fields specified on the Fields - Outgoing mapping.

Notify Transaction

When an analyst adds a note to a call or request logged as a result of an event, ASM:

  1. Sends a notify transaction to the external system if the rule specified in the Action tab on the Event Type Mapping Details window says to send a notify transaction when a note is added to the call or request.

  2. Attaches the contents of the note to the notify transaction sent to the external system.

When ASM adds a history entry (for example, an agreement escalation) to a call or request logged as a result of an event, ASM:

  1. Sends a notify transaction to the external system if the rule specified in the Action tab on the Event Type Mapping Details window says to send a notify transaction when a system-generated entry is added to the history of a call or request.

  2. Attaches the contents of the history entry to the notify transaction sent to the external system.

  3. Notify transactions are never sent for audit-related history entries, such as objects uploaded, items linked to the call or request, analysts taking action on the call, etc.

Clear Transaction

When an analyst closes a call or request logged as a result of an event, ASM:

  1. Sends a clear transaction to the external system if the rule specified in the Action tab on the Event Type Mapping Details window requires it.

  2. Attaches the contents of the Actions & Solutions field to the clear transaction sent to the external system.

  3. Updates any fields specified on the Fields - Outgoing mapping.

  4. Objects attached to an incoming event are ignored. Objects attached to a ASM call or request are not sent with any acknowledge, update, notify or clear transactions.

Acknowledging an Event

Before you start

The Acknowledge Event option must be selected on the IPK or Workflow Management security role of the analyst viewing the call or request.

The call or request must be in Action mode (not in Review mode).

The system administrator must have configured Event Management so that acknowledgment of an event is done manually for a particular event mapping.

A message appears on the Details window of the call or request logged as a result of the eventindicating that an event has been received by ASM and resulted in a call or request being logged, but that no acknowledge transaction has yet been sent to the external system.

This message is only displayed if:

  • The mapping applied to the event for which this call or request was created has the Send Acknowledge field set to Manually, AND

  • An acknowledge transaction has not yet been sent to the external system for this event.

To send an acknowledge transaction to the external source for this event, select the Acknowledge Event button.