Create CM Task and Open for Users

Prerequisites: Only when you interactively run a single intent, the following logics occur; the following logics will not occur if the NI is run in the backend, for example, the NI is triggered to run, or ADT intent is run via timer.

After the execution is complete, the framework checks for any CM task information in the NI result. If such information is found, a confirmation window will prompt you to decide whether to proceed with follow-up remediation. If you selects Yes, the CM task will be created and opened on a map with devices to be configured. You can then efficiently execute the network change by clicking each node in the CM task.

Execute Change via	UI	Description
Config Change Node		The CLI change commands for each device are displayed in the right pane: To distinguish different types of changes for a single device, there is a CLI icon next to the device hostname on the left UI.
Ansible Node		The following change information for each device is displayed: Playbook text The definition line of host variables that defines input variables in the inventory template The segment of the ‘external input vars’ in YAML in the inventory template that belongs to the current device Additionally, there is also an Ansible node icon next to the device hostname on the left UI.

Note: If multiple config changes are defined in the CM template, they will be combined in order and displayed in this prompt box.

After you select Yes:

• A new map is created from the client and all the devices in the CM device list will be drawn to this new map.
• A CM task is created on this new map using the specified CM template and change list.
• The newly created CM task is automatically opened on the new map, and the NI execution is completed.

After the CM task is opened, you can manually click to perform the subsequent remediation operations in the open CM task, including sending approval requests, benchmark before, executing change, etc.