If set to "File": the trigger checks if the configured jobticket (ascii file) contains the configured variable and if the content of the variable matches the configured value the trigger will return "True"......or it just checks if the configured ticketfile exists and returns "True" if it does. The format of the variables in a ticket file is: varname:varvalue

If set to "WEB": the trigger checks if a new job for the configured Ticket exists. If a new job exists the trigger returns "True".

If set to "WEB Post": the trigger checks if a new job for the configured command exists. "WEB Post" is triggered by sending a http post command to the Companion Server of Integration Tool. The specification of sending the post command is as follows:

URL:
http(s)://{url of your companion server}/api/command

HEADERS:
X-API-USERNAME = the Integration Tool WEB account that has the "Web Posts" privilege
X-API-PASSWORD = the password of the Integration Tool WEB account

CONTENT-TYPE:
application/json

CONTENT:
{

"Command" : "your command",
"P1" : "param1",
"P2" : "param2",
"P3" : "param3",
"P4" : "param4",
"P5" : "param5",
"P6" : "param6",
"P7" : "param7",
"P8" : "param8",
"P9" : "param9",
"P10" : "param10"
...
"P50" : "param50"

}

Trigger on new ticket: trigger returns True is a new ticket(file) is found
Trigger on variable name: trigger returns True if the configured variable contains the configuredvalue.

The post-command to trigger on.