Server Administration > Automate Tasks and Calculate Data Using Event Triggers > Overview of Workflow and Document Triggers > Key Considerations
Key Considerations
Triggers fire in their position order. If there are two rule-based triggers with the same rule, the higher position (lower number) trigger fires first. If there are two scheduled triggers set for the same date and time, the high position (lower number) trigger fires first.
Triggers have administrator privileges and may override user permissions, but the history records the changes as having been performed by the user.
If a pre-event trigger modifies or creates another item, the secondary item becomes part of the transaction. Either all of the modifications made to all of the items succeed or none do.
To ensure a pre-event trigger does not run more than once, when it has completed, other secondary triggers are not permitted to obtain that item.
The values of the computed fields are neither calculated nor stored while creating or editing an item in the Windchill RV&S. This will result in the New Value of a computed field to be the same as its Existing Value when referenced in a trigger rule.
Windchill RV&S constraints functionality now allows you to manage field rule validations through the Windchill RV&S administration client GUI (or CLI). You can create constraints when you are editing types, rather than writing and maintaining individual trigger scripts. Constraints functionality effectively replaces trigger scripts that previously validated field rules.
In particular, you no longer need to use the Windchill RV&S pre-trigger mandatoryFieldsOnStateTransition.js to enforce mandatory fields on a state transition. For more information on configuring constraints, see “Managing Constraints”.