Managing Event Type Mappings

You can define the criteria for applying mapping for incoming events sent from the source, the action to be taken by ASM Core.

PreviousViewing Event Types NextUsing Events

Creating an Event Type Mapping

Before you start

You must have Integration Setup selected in the Admin tab of your General Access Security Role.

Select menu, and then Admin.

From the submenu, select Integration.

The Integration Platform Settings window appears.

Select the Events option on the explorer pane.

Select a source from the Filter by Source list to view all the event types discovered on the selected source by a connector with event management capability.

Select to display the details window. The Source and Event Type fields are already populated based on the source and event type you selected to access this mapping. If groups are defined for the event types, an additional read-only field, Group, displays the event type group name. You can use this to create a mapping by event group.

Complete the details.

Name

Type a name for the mapping. This name appears in the Mappings table. This is a mandatory field.

When Received

Select the action to be taken in ASM when an event is received from the source (that is, when a Receive Transaction is sent by the external system):

Using Template

This is only active if you have selected Log Call or Log Request.

Select the Call Template or Workflow Template that ASM Core will use when logging the call or request.

If you save this mapping and open it later for editing, and change the Log Call or Log Request option, a warning message appears indicating that the criteria and field mappings will be cleared and you will have to redefine these. In the warning, click Yes to reset all the field mappings and configurations, or No to cancel.

Logging Analyst

Select the person who must be set as logging analyst or request manager for the call or request logged as a result of the incoming event for this mapping. This is a mandatory field.

If the call or workflow template does not have an assignee, then the call or request logged as a result of an incoming event using this mapping will be sent to the analyst you specify in the Logging Analyst field, but only if that analyst is permitted to own a call or request (as defined in the Options tab of the IPK Management security role). If the analyst does not have this permission, then the call or request will be sent to the creator of the call or workflow template.

Complete the Mapping Details

Select the Criteria tab to specify the conditions for applying this mapping to an incoming event:

Default Mapping - Select to flag this as the default mapping for this event type, that is, the mapping which will apply to an incoming event if no other mapping for the event type can be applied.

You can only define one default mapping for the event type. If a default mapping has already been defined, then when you save the current mapping, a warning message displays, allowing you to set the current map as the default, or clear the default mapping setting for the current mapping.

Clear to set the conditions for applying this mapping to an incoming event, using the rules builder pane. These conditions are set by defining a rule. For example, to specify that this mapping must be used when the severity of a problem is “Level 5”, you can build a rule: {[Event: Severity(1-5)}=”5”]}.

The fields you can pick in the left hand side of the rule statement correspond to the fields defined on the source. They are defined at the level of the connector, and cannot be modified. The values on the right hand side of the statement are values corresponding to the fields on the source. You cannot use ASM Core call or request fields in the criteria.

Select the Action tab and specify the rules for Incoming Transactions using this mapping and the rules for Outgoing Transactions using this mapping, in other words, the actions that ASM Core must take when an incoming event matches the defined criteria, and the event mapping is set to log a call or request.

Rules for Incoming Transactions - Events

Rules for applying an event type mapping to Incoming Transactions for the selected event type are set in the Action tab on the Event Type Mapping Details window. The rules are described below.

When Updated externally

Select the action that must be taken if the call or request logged as a result of this event is still open:

When Updated externally and Call or Request is closed

Select the action that must be taken if the call or request logged as a result of this event is closed:

When Notified externally

Select the rules that ASM Core must apply when receiving a NOTIFY transaction for an event using this mapping, specifically the action that must be taken if the call or request logged as a result of this event is still open:

When Notified externally and Call or Request is closed

When Resolved externally

Select the rules that ASM Core must apply when receiving a RESOLVE transaction for an event using this mapping, specifically, select the action that must be taken if the call or request logged as a result of this event is still open:

If child calls are present

Select the action that must be taken if the call logged as a result of this event has calls linked as children:

When Resolved externally and Call or Request is closed

Select the rules that ASM Core must apply when receiving a RESOLVE transaction for an event using this mapping, specifically the action that must be taken if the call or request logged as a result of this event is closed:

When Deleted externally

Select the rules that ASM Core must apply when receiving a DELETE transaction for an event using this mapping, specifically select the action that must be taken if the call or request logged as a result of this event is still open: