Server Administration > Automate Tasks and Calculate Data Using Event Triggers > Coding Configuration Management Triggers
Coding Configuration Management Triggers
Once you have referenced the necessary Beans, you can begin coding the rest of the trigger according to your needs.
For example, to create a server-side script that checks for a member revision description type the following:
Next, do the following:
1. Save the trigger script to the trigger library:
2. Update events definition file.
3. Restart Windchill RV&S server.
4. Windchill RV&S runs the configuration management event trigger at the next applicable client action.
You should restrict JavaScript triggers to a reasonable length. Although the Windchill RV&S server can process commands in parallel, a long running script can affect the duration of that specific command from the client’s perspective.
For example, the following client-side script—CIpre—runs a KornShell script that prompts the user to add a revision description for the member they are checking in.
To configure the trigger, the following information is added to the Windchill RV&S server:
si.trigger.CIpre.command=sh -w -c 'echo Please provide a brief summary
of changes you made in the Revision Description field.'