Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Universal Controller supports the following CLI functions for Imports and Exports, which are listed alphabetically on this page.

  • Export Bulk
  • Export Trigger
  • Import Bulk
  • Import Trigger

Syntax, parameters, and examples for each function are provided.
 

...

Anchor
export trigger
export trigger
Description

Performs an export of the specified trigger(s) and all the associated record(s). For example, if you export one trigger, the CLI also exports the calendar used in the trigger and all tasks launched by the trigger. The CLI creates a separate XML file for each record type and generates the output directory and file names using a date and timestamp, plus an internal record identifier generated by the Controller.
 
All exported XML definition files will be saved to a timestamped directory under the path defined by the Export Path Universal Controller system property. The following illustrates a sample output directory and exported data:
 

 

Syntax

uagcmd ops-export-trigger global parameters trigger-name=name [trigger-type=type]
 

Note
titleNote

For backward-compatibility, you can exclude uagcmd from the command line for this function and all pre-6.2.0.0 CLI functions.


Parameters

  • trigger-name=
    Required; Name of one or more triggers. Wildcards are supported.
  • trigger-type=
    Optional; If you used a wildcard in trigger-name, you can use trigger-type to narrow down the selection to a specific type of trigger. Allowable values are (not case sensitive): cron, time, file_trigger, temporary, task_monitor, manual, application_monitor.

Example

This example exports all triggers whose name begins with SF:
 

Panel
uagcmd ops-export-trigger -c config.cfg trigger-name=SF* 


...