Save and Test the ADT Intents-based Triggered Diagnosis

You can choose to test the triggered diagnosis to make sure the settings are correct, which is not mandatory.

1. In the Configure Triggered Automation window, click OK to save the triggered diagnosis.
   

   Before testing the triggered diagnosis, you need to save it first. If you try to test an unsaved triggered diagnosis, a message will appear to notify you.

2. Click Test in the Configure Triggered Automation window.
3. In the Test Diagnosis window, define the following settings:
   1. Input the data fields to emulate the API call:
      
   2. Description: Input the Description for the potential network issue.
   3. Device_name: Enter the device name of problem device.
   4. Click Test to test the Diagnosis to determine if the Diagnosis if properly defined.

2. The system prints out the execution log with the following outputs:
• The results of Incident type.
• Matched triggered Diagnosis.
• Match intent for ADT.
• NI execution results if execution mode includes the execution of NI.
• The message “Created map incident message.” if the execution mode includes the Intent Map. Likewise, the map note is displayed if the corresponding option is selected.
• Incident devices if Set Incident Device option is set.
• Incident message if the option is enabled.
• Whether the incident message is successfully created by the Guidebook or Runbook template if the corresponding option is selected.
• Whether the subscription to preventive automation is successfully enabled if it is configured.

A View Result in Incident button is provided to view the Incident for this incoming call.

4. Click Close to close the Test Diagnosis window.