Manually exporting Results to XML

Besides by executing a Task Export Ivanti Automation Results, you can also manually export the results of a Job from the Console as an XML file. Exporting the results to an XML file allows you or others to view results without using the Console. This is useful, for example if someone wants to review the results of a Job on a computer on which a Console has not been installed. You can also use it save specific results as an XML file before you delete these results from the Datastore.

You can use the Export Results window for a number of purposes:

  1. Change the save location of the XML file, if necessary.
  2. Select the relevant export options.
  3. Click Export.
  1. Change the save location of the XML file, if necessary.
  2. Select the relevant export options.
  3. Click Copy Command Line.
  4. Configure a Task Execute Command, paste the command line on its Settings tab, and schedule a Job with this Task. Alternatively, you can run the command line using a Microsoft Windows command prompt.
  1. Change the save location of the XML file, if necessary.
  2. Select the relevant export options.
  3. Select the options Replace GUID with function and Add command line parameter to wait for job to finish.
  4. Click Copy Command Line.
  5. Configure a Task Execute Command and paste the command line on its Settings tab.
  6. Use this Task in a Job that contains the Module(s) or Project(s) of which you want to export the Job results. Alternatively, if a previous Job is still running, you can export the results of this Job by scheduling a new Job that only contains the Task Execute Command.

Because Ivanti Automation remembers the GUID of each last opened or scheduled Job, you can schedule a Job that exports the Job results of a previous Job:

  1. Change the save location of the XML file, if necessary.
  2. Select the relevant export options.
  3. Select the option Replace GUID with function.
  4. Click Copy Command Line.
  5. Configure a Task Execute Command and paste the command line on its Settings tab.
  6. On the Module Parameters tab, create a parameter $[MASTERJOBGUID] for the Task and make sure you clear the Input option Show previous value for this parameter. The parameter $[MASTERJOBGUID] is a special parameter: it works similar to the function @[MASTERJOBGUID], and is used by Ivanti Automation to capture the GUID of the previous Job.
  7. On the Settings tab, replace the function @[MASTERJOBGUID] in the command line with a parameter $[MASTERJOBGUID].
  8. Schedule a Job with the Task. During execution of the Job, the value of the parameter $[MASTERJOBGUID] in the command line will be replaced by the GUID of the previous Job.

Export Options

  1. Select Export overview results to include a general overview of the Job results for all Tasks that were included in the Job.
  2. Select Export detailed results to include a detailed overview of the Job results for all Tasks that were included in the Job. If you also select Export overview results, RES ONE Automation will create one XML file that first gives a general overview of the Job results and then a detailed overview.
  3. Select Export results per Agent to create a separate XML file for each Agent that executed the Job, including the name of the Agent. This is useful when you want to keep a separated administration for each Agent.

Configuration

  • In the Save location field, you can replace folder names with their associated environment string by right-clicking the field.
  • With Export overview results, you can create an XML file with a general overview of the results.
  • With Export detailed results, you can create an XML file with a detailed overview of the results. If you also select Export overview results, Ivanti Automation will create one XML file that first gives a general overview of the results and then a detailed overview.
  • With Export results per Agent, you can create a separate XML file for each Agent that executed the Job, including the name of the Agent. This is useful when you want to keep a separated administration for each Agent.
  • The Command line box shows the command line that you can use to generate an XML file.
    • With Replace GUID with function, you can create a generic command line that you can use in, for example, a Task Execute Command.
    • With Add command line parameter to wait for job to finish, you can create a generic command line that waits with exporting results until all running Tasks have been executed. This option only works when combined with the option Replace GUID with function.
  • It is not possible to export the results of multiple Jobs using the Command line box.
  • When you have selected the option Export results per Agent, any existing XML files will be overwritten without warning.
  • You can only execute a command line that exports results on Agents on which a Console has been installed.
  • The function @[MASTERJOBGUID] cannot be used for Run Books.
  • When used in combination with the Task Execute Command and the timeout option Terminate process, the Task will be terminated but not the sub processes. This generates Job results exported to an XML file. The timeout option Terminate process tree will also stop the sub processes and does not generate an XML file.