---
sourceDocument: Australia IT Operations Management
sourceDocumentLink: https://www.servicenow.com/docs/r/australia/it-operations-management

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia IT Operations Management

ft:clusterId :

    - itom

bundleId :

    - itom

workflow :

    - Technology


---

# Example: Bind alerts to CIs using dynamic CI types

# Example: Bind alerts to CIs using dynamic CI types {#ariaid-title1}

Release version: Australia  
Updated March 12, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read  
Use event field mapping to dynamically bind alerts to the appropriate CIs based on event attributes. This eliminates the need for separate event rules for each CI type, also known as CI class.

## Before you begin

Role required: evt_mgmt_admin

## About this task

In general, for an event generated from a specific source mentioned in the Source field, the system applies the corresponding event rule. The override default binding option in an event rule specifies a
specific CI class for binding. However, in a more dynamic use case, the CI class is not predefined and can change based on event attributes. For example, suppose a customer has multiple CIs with the same name, but each CI
belongs to a different CI class. In the traditional event rule method, the CI class (or the CMDB table) is defined for a CI. However, the system searches the same CI class for all CIs with the same name and attributes, not the specific CMDB table defined for each CI class. This causes incorrect mapping.

To resolve this, the system uses the CI type field from the event to identify the CI class. Event field mapping maps event attributes to the CI type, so the system knows which CMDB table to search and correctly maps the CI to the event.

## Procedure

1. Navigate to AllEvent ManagementRulesEvent Field Mapping.  
2. Select Oracle Cloud.  
   This is an existing event field map used as an example. The event field map details page opens.

3. Review the event field mapping details page and understand the relevant fields and their corresponding values.  
   {#bind-ci-event-mapping__table_EventFieldMappingForm__entry__2}

   | Field | Description |
   |-|-|
   | Name | Event field map name. |
   | Source | Event monitoring software that generated the event. In this case, oraclecloud. |
   | Order | Number to define the order in which this action should be processed. Actions with lower numbers are processed first. |
   | Mapping type | Select Map field and transform value (Single field). |
   | Source field | resourceType is a field that is defined in the Additional Information field of the event defined by the Oracle Cloud system. The possible values of resourceType are listed in the From value column, while the corresponding CMDB tables for those values are specified in the To value column in the Transform value pairs section. If resourceType is instance, the system searches in the \[cmdb_ci_vm_object\] table for CI binding. |
   | Target field | The CI type field (ci_type) in an event is a special field that provides the CI class name, indicating which CMDB table to search. The CI type field values are listed in the To value column in the Transform value pairs section. |
   | Transform value pairs ||
   | From value | Lists the possible values of the event field (e.g., `resourceType`) that are derived from the event data. |
   | To value | Specifies the corresponding CMDB table associated with each value listed in the From value column. Indicates the CI type to bind the alert to. |
   [Table 1. Event Field Mapping fields]

   {#bind-ci-event-mapping__table_EventFieldMappingForm}

*[\>]: and then