The edit button for Impacted Services/CI's is missing on change requests.

[ShivaKumarB9231]

Hi Team,

The 'Edit' button on the Impacted CIs tab is missing. When the Change Request is in the "New" state, we are able to see the 'Edit' button on the Affected CIs tab, but it is not visible on the Impacted CIs tab.

Could you please help us understand the reason for this behavior?

Than you.

[MaxMixali]

What’s going on

• Affected CIs (related list = task_ci) is meant to be edited by the change team. You can add/remove CIs directly, so you see the Edit button there (in “New” state and other editable phases).

• Impacted CIs is typically a derived / read-only list that’s calculated by impact analysis (e.g., from the selected Business/Technical Services, service maps, or from the Affected CIs and their dependencies). Because it’s computed, the platform doesn’t expose the Edit action on this list. You change what’s impacted by adjusting inputs (Affected CIs, Impacted Services) and re-running impact analysis—not by editing the list itself.

Why you don’t see “Edit” on Impacted CIs

• The related list behind Impacted CIs points to a table used by the impact analysis output (varies by release; often an “impacted_*” table or view). OOTB it’s read-only by design, so the “Edit” UI action is not shown.

• In contrast, Affected CIs uses task_ci, which supports manual maintenance, so the “Edit” button appears when the Change is in an editable state and your roles/ACLs allow it.

How to change what appears under “Impacted CIs”

1. Add/Remove on Affected CIs (the editable list).

2. Adjust Impacted Services / Business Service if you use service-based impact.

3. Run/refresh Impact Analysis (e.g., “Analyze impact” or the workspace action) so the platform recalculates the Impacted CIs list.

If you really need manual editing of “Impacted CIs”

Not recommended (it defeats the purpose of a computed list), but options are:

• Expose/replace the related list with an editable M2M to cmdb_ci (customization), or

• Build a UI action/form that writes to the same table your instance uses for impacted-output records (requires understanding your release’s data model and relaxing ACLs).

Quick checks (if behavior seems off)

• Confirm you’re looking at Impacted CIs (computed) versus Impacted Services (M2M to cmdb_ci_service, which usually is editable).

• Ensure your Change state/model doesn’t lock related lists (some models lock after certain phases—but you said “New”, so that’s fine).

• Verify roles/ACLs if even Affected CIs lacked Edit (not your case).

Bottom line:

You can edit Affected CIs; Impacted CIs is computed and intentionally read-only. Adjust the sources (Affected CIs/Services) and re-run impact to update it.

[ChallaR]

Hi @ShivaKumarB9231 ,

please find the below root cause , this might help you the find the issue .

Root Causes

1. List Control Settings:

   • Out-of-the-box (OOTB), ServiceNow only shows the 'Add' button for the Impacted CIs tab in the "New" state.
   • To enable the 'Edit' button, you need to manually configure it via the List Control:
     • Right-click on any column in the related list.
     • Select List Control.
     • Ensure the 'Omit Edit' checkbox is unchecked.
     • Save the changes.

2. Relationship Type:

   • The 'Edit' button typically appears for many-to-many relationships.
   • If the Impacted CIs tab is configured as a one-to-many or defined relationship, the Edit button may be hidden by default.

3. ACLs (Access Control Lists):

   • If there are ACLs restricting access to the underlying table or fields, the Edit button may not appear.
   • You can check ACLs for the impacted_ci or related table and ensure the user has write access.

4. Scripted Conditions:

   • There might be a scripted condition in the List Control or UI Policy that hides the Edit button based on the state of the Change Request.

 Suggested Fix

To enable the 'Edit' button on the Impacted CIs tab:

• Go to the Change Request form.
• Navigate to the Impacted CIs related list.
• Right-click a column header → List Control.
• Uncheck 'Omit Edit' if it's selected.
• Save and test again in the "New" state.

Please mark as correct and close the thread if this is helpful.

Thanks,

Rithika.ch