Creating Other Triggers

Server Administration > Automate Tasks and Calculate Data Using Event Triggers > Creating Workflow and Document Event Triggers > Creating Other Triggers

In addition to schedule- and rule-based triggers, you can create triggers that run when one of the following actions occur:

• time entry is changed

• item tree is copied

• item is branched

• item is labeled

• test result is created, modified or deleted

The triggers for item actions are currently used in the Integrity Requirements solution, and are useful for document management. The trigger for test results is useful for test management.

The general steps required to create another trigger are as follows:

1. Select the other trigger type.

2. Provide a description for the trigger.

3. Select a script file from the library for the trigger to run, and fill out the parameters for it.

• Scripts listed under the samples directory (for example, samples/breakLockNotification.js) are for configuration management and are not applicable to workflow and document management.

• Backlashes (\) in parameters are truncated after you save and run the trigger, for example, in a directory path. To avoid this, use forward slashes (/).

Key Considerations

• The Rule, Schedule, Query, and Assignment tabs are not meaningful to other triggers, and are therefore disabled in the Create Trigger dialog box.

• For non-batch processing of time entry triggers, a single time entry PRE event is fired before each operation, then the operation is performed and committed to the database, and finally the POST event is fired. In this way, the method used for non-batch processing of time entries triggers is consistent with the method used for batch processing.

All operations are available to you in the POST event. For example, if you submit 200 time entry edits, there will be 200 PRE triggers, then the 200 operations will process, and finally there will be a single POST trigger that references all 200 operations.

• The test results trigger will fire before and after each batch of test result creates, edits, and deletes. If the test result is modified by the tm setresults command, any creates (if they exist) will fire a trigger, and any edits (if they exist) will fire another trigger.