• Result. The result of the task for the selected device.
• Message. Any message pertaining to the task for the selected device. In some instances, this field may be empty.
• Trace. A history of all communication that takes place between the device and the WhatsConfigured service during the task's attempted completion. If the task collects a configuration file as part of the task, it is included in the trace. If the task was successful for this device, the trace displays what the command prompt would have looked like if the user consoled into the device and run the commands manually using a command prompt.

  If the task failed and no communication took place between the device and the WhatsConfigured service due to communication or configuration errors, the box displays "No communication with the device was recorded." Finding the cause of this failure may be accomplished by reviewing the credentials listed on the Settings tab, reviewing device configurations, attempting to communicate with the device manually, or by checking the log.

• Script Text. The script assigned to be run by the task. If this script is a custom script, it appears exactly as it did when it was configured in the New/Edit WhatsConfigured Task Script dialog. If this is a predefined password or backup task, the script displayed is the script chosen for this device based on the WhatsConfigured script registry.

Note: Scripts for predefined WhatsConfigured tasks are looked up based on the OID associated with the device. If there is no OID assigned to the device, the lookup fails and no script is listed. OID's can be assigned to a device from the Device Properties - Tasks dialog, or collected by discovering the device. Due to the large number of devices and their varying commands this script to device mapping may fail.

• Processed Text. The WhatsConfigured scripting language allows for variable replacement within scripts. WhatsConfigured pre-defined scripts utilize this ability when running password tasks. Before the script is run the script is processed and all variable references are replaced with the variables corresponding value. The processed text displays the resulting script after processing. This field allows the user to ensure variable declarations are being assigned and interpreted properly.

Tip: If you are experiencing a problem with a script, Save the results listed in the script tab to a text (.txt) file. If you contact Technical Support, this file will aid in troubleshooting your script problem.

The Name and Value of any variables used and defined within the task script.

The Commands tab displays a list of the commands as they were interpreted by the WhatsConfigured script runner. It also displays the results of those commands if they were run against the device when the task was run.

For each command, the following information is listed:

• Command. The specific command; for example, login or show configuration.
• Result. The success or failure of the command when it was ran by the task.
• Output. The results of the responses declared by the WhatsConfigured script language.

You can use the Commands tab to ensure your custom scripts are being interpreted by WhatsConfigured properly.

Note: To ensure that the responses to your commands are working properly within the task script, refer to the Trace on the Output tab.

The log tab displays error messages that were logged as the task ran.

Log messages can include failed commands and configuration errors.

The Settings tab displays the protocol credentials assigned to the device to enable the task's completion.

• Type. The type of protocol credentials; for example, SSH or Telnet.

Note: WhatsConfigured defaults to SSH credentials when available. If SSH credentials are not assigned to a device, WhatsConfigured will look for/use Telnet credentials.

• Name. The name of the credentials as assigned in the Credentials Library.
• Description. The description of the credentials as assigned in the Credentials Library.