Analyze potential impact AI agent

This agent analyzes the potential business and operational impact of a proposed change by identifying affected servers and services. The agent reviews the change request, performs impact analysis, and documents findings in work notes to support informed decision-making and effective mitigation strategies.

Workflow

The agent analyzes a change request to identify and document the potential impact on services and servers.

1. Validate that all prerequisites for the impact analysis are met before proceeding.

2. Retrieve the change request number from the current active page, or prompt you to provide it if unavailable.

3. Extract the affected server IDs from the change request.

4. Identify which services are potentially impacted by mapping affected servers to suggested services using the Service Mapping Candidate skill.

5. Retrieve a combined view of impacted servers and suggested services.

6. Perform a full impact analysis for each suggested service, including cascading effects, using the Service Mapping Candidates Impact skill.

7. Compile the analysis results and update the change request work notes with a consolidated summary.

<table><thead><tr><th>

Field

</th><th>

Description

</th></tr></thead><tbody><tr><td>

Allow third party to access this AI agent

</td><td>

When enabled, third-party AI agents can use this agent. This value is off (false) by default. This setting is defined in the AI Agent configs [sn_aia_agent_config] table on the External discoverable field.

</td></tr><tr><td>

Allow AI specialists to access this AI agent

</td><td>

When enabled, AI specialists can use this agent. This value is off (false) by default. When set to true, more configuration options for tools become available so that an AI specialist can map inputs and response templates to tool outputs. This setting is defined in the AI Agent configs [sn_aia_agent_config] table on the Specialist enabled field.

</td></tr><tr><td>

Manage long-term memory

</td><td>

When enabled, all previous user interactions are used as context for the LLM. This value is off (false) by default. This setting is defined by the sn_aia.ltm.enable_long_term_memory system property. For more information, see ServiceNow Otto AI agents reference.

</td></tr><tr><td>

Tools

</td><td>

• Scripts

Analyze potential impact prerequisites validator

Extract Data from Change Request

Get Impacting Servers Per Suggested Service

Update Change Request Work Notes

• Flow Actions

Get Full Impact Analysis of Each Suggested Service

Get Impacted Servers and Suggested Services

</td></tr><tr><td>

Allowed user roles The specific user roles that can access this AI agent.

</td><td>

sn_change_write

</td></tr><tr><td>

Data access roles The specific user identity roles that determine which data the AI agent can access and what actions it can take.

</td><td>

service_mapping_ai_user, cmdb_read, itom_admin, snc_internal, snc_required_script_writer_permission, sn_bm_client.benchmark_data_viewer, sn_itom_license.reader

</td></tr><tr><td>

Triggers

</td><td>

Optional. None defined by default. An admin can specify triggers if desired. For more information, see Add a trigger to an AI agent.

</td></tr><tr><td>

Channels

</td><td>

Configure an assistant for Virtual Agent or ServiceNow Otto panel using Assistant Designer.

</td></tr><tr><td>

Used in agentic workflows

</td><td>

Analyze Potential Impact

</td></tr></tbody> </table>Learn more about IT Operations Management at IT Operations Management.

Parent Topic:IT Operations Management AI agents