Server Administration > Automate Tasks and Calculate Data Using Event Triggers > Overview of Configuration Management Server-Side Triggers > Transactionality of Configuration Management Event Triggers
Transactionality of Configuration Management Event Triggers
The operation of server-side triggers occurs in the following sequence:
1. Windchill RV&S client initiates a command that will run on the Windchill RV&S server.
2. Before event begins, pre-event is posted.
3. Event occurs.
4. Windchill RV&S server polls its registry of events to determine if the event has an associated script.
5. If script is found, the Windchill RV&S server executes the resolved script.
6. Command executes.
7. If command succeeds, post-event is posted.
An event trigger is executed either prior to an event or after the event. Pre-test event triggers are executed before the command is executed and are most useful for preventing transactions if particular conditions are not met. For example, a pre-test trigger could prevent state changes if no label has been added to the member.
Post-test event triggers are executed after an event is successfully committed and are most useful for combining actions. For example, after the successful check in of a revision, a post-test event trigger could apply the label with the name of the user who checked in the revision.