TRIGGER EDIT
Description
Edits a trigger.
Usage
cm trigger | tr edit <subtype_type> <position_number> [--position=<new_position>] [--name=<new_name>] [--script=<script_path>] [--filter=<str_filter>] [--server=<repserverspec>]
Options
| Option / Argument | Description |
|---|---|
| --position | New position of the specified trigger. This position must not be in use by another trigger of the same type. |
| --name | New name of the specified trigger. |
| --script | New execution path of the specified trigger script. If the script starts with "webtrigger ", it will be considered as a web trigger. See Remarks for more further details. |
| --filter | Checks only items that match the specified filter. |
| --server | Modifies the trigger on the specified server. If no server is specified, executes the command on the one configured on the client. (Use 'cm help objectspec' to learn more about server specs.) |
| subtype_type | Trigger execution and trigger operation. (Use 'cm showtriggertypes' to see a list of trigger types.) |
| position_number | Position occupied by the trigger to be modified. |
Help
Remarks
Web triggers: A web trigger is created by typing "webtrigger <target-uri>" as the trigger command. In this case, the trigger will execute a POST query against the specified URI, where the request body contains a JSON dictionary with the trigger environment variables, and a fixed INPUT key pointing to an array of strings.
Examples
cm trigger edit after-setselector 6 --name="Backup2 manager" --script="/new/path/al/script"
cm tr edit before-mklabel 7 --position=4 --server=myserver:8084
cm trigger edit after-add 2 --script="webtrigger http://myserver.org/api"