For server administrators who have advanced understanding of Xinet Triggers and
Actions, this section delves into the structure and information found in the
trigger.log file.
The trigger.log file, accessible through the
Logging, Trigger subtab, will give a list of the variables used in each attempt to run an action, and that data can be used to exercise the action before implementing it in a workflow or troubleshooting why an action may not be behaving as expected.
This shows that the setting Demo_Email was run when the value of the
CheckBox data field was set to checked;
1 represents the positive value, while
0 is the negative value. Using these values, you may then try to run the
Action on the command-line like this to see if it executes properly:
Remember, always edit a copy of the Action script rather than modifying the original file. After copying the script, use the instructions for enabling debugging found within the script to select the desired debug level. Running the
Action again, as in the example above, should give you more information about why the
Action is behaving incorrectly. With that new information, you may be able to easily determine the cause of the error and correct the situation. If you require more assistance, report the results to
help@northplains.com along with a description of the problem.
