Event Management — Event Rule Binding Tab Shows Limited or No CI Identification Options<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } .kb-wrapper { font-family: 'Lato', sans-serif; font-size: 12pt; line-height: 1.7; color: #000000; max-width: 100%; } .kb-wrapper h2 { font-family: 'Lato', sans-serif; font-size: 14pt; font-weight: 900; color: #032D42; border-bottom: 2px solid #e8fce4; padding-bottom: 4px; margin-top: 28px; margin-bottom: 12px; } .kb-wrapper p { font-size: 12pt; margin: 0 0 12px 0; } .kb-wrapper ul, .kb-wrapper ol { font-size: 12pt; margin: 0 0 12px 0; padding-left: 24px; } .kb-wrapper li { margin-bottom: 6px; } .kb-wrapper .callout-info { border-left: 4px solid #52B8FF; background: #e6f4ff; padding: 10px 14px; margin: 14px 0; font-size: 12pt; } .kb-wrapper .callout-warning { border-left: 4px solid #e6a817; background: #fff4e0; padding: 10px 14px; margin: 14px 0; font-size: 12pt; } .kb-wrapper code { background: #e6f0f5; color: #032D42; border: 1px solid #b8cfd8; padding: 1px 5px; border-radius: 3px; font-size: 11pt; } .kb-wrapper table { width: 100%; border-collapse: collapse; margin-bottom: 16px; font-size: 12pt; } .kb-wrapper table th { background-color: #032D42; color: #ffffff; padding: 8px 12px; text-align: left; font-weight: 700; } .kb-wrapper table td { padding: 8px 12px; border-bottom: 1px solid #dde6ea; vertical-align: top; } .kb-wrapper table tr:nth-child(even) td { background-color: #e8fce4; } .kb-wrapper .steps-list { list-style: none; padding-left: 0; counter-reset: step-counter; margin: 0 0 12px 0; } .kb-wrapper .steps-list li { counter-increment: step-counter; display: flex; align-items: flex-start; gap: 12px; margin-bottom: 10px; } .kb-wrapper .steps-list li::before { content: counter(step-counter); min-width: 26px; height: 26px; background-color: #032D42; color: #63DF4E; border-radius: 50%; display: flex; align-items: center; justify-content: center; font-weight: 700; font-size: 11pt; flex-shrink: 0; margin-top: 2px; } .kb-wrapper .related-links a { color: #032D42; text-decoration: underline; } .kb-wrapper .link-disclaimer { font-size: 10pt; font-style: italic; color: #555; margin: 2px 0 10px 0; } Summary When configuring the Binding tab on an Event Rule and selecting CI Identification as the binding type, users may encounter one or more of the following behaviors: The CI Identification section shows only a single attribute option with no ability to add more.The attribute fields appear blank or do not display, even though the underlying data exists in the system.A warning message reads: "The binding rule does not match any identification rule…" even when a valid identification rule exists for the selected CI class.The behavior is intermittent — attribute fields display correctly on some visits to the rule but not others. This article explains why these behaviors occur and what is expected for standard CI classes, Calculated Application Service, and Mapped Application Service. Figure 1. Event Rule Binding tab with CI Identification selected and Calculated Application Service as the target class, showing a single available criterion attribute. The warning message "The binding rule does not match any identification rule…" may appear even when a valid identification rule exists for the selected class. This message does not necessarily mean binding will fail at runtime. The Event Rule may still resolve CI matches correctly even when this warning is displayed. Special Case: Calculated Application Service The Calculated Application Service class (cmdb_ci_service_auto) uses a dynamic, composition-based identification model. In the CI Identification binding context, this class supports only a single condition — typically name or sys_id. Configuring multiple AND/OR attribute conditions is not supported for this class type when using CI Identification binding. Special Case: Mapped Application Service The Mapped Application Service class (cmdb_ci_service_by_tags) does not have an independent IRE identification rule defined out of the box. Because the Binding tab is populated entirely from IRE identification entries, no attribute options are available when this class is selected with CI Identification binding. The Binding tab will appear empty or non-functional for this class regardless of instance configuration. This is expected out-of-the-box behavior and is not a defect. Note — UI deprecation: The Event Rule Designer is the legacy interface in which these behaviors occur. ServiceNow has introduced a newer event rule management experience in Service Operations Workspace. Consider evaluating the newer interface as an alternative. Related Links Event rules Identification and Reconciliation Engine Calculated Application Services