8.7 Additional Uses for UCM Triggers

The examples shown in the previous sections represent just a few ways that you may use UCM triggers to enforce development policies. Other uses for UCM triggers include the following:

• Creating an integration between UCM and a change request management (CRM) system. Although we expect that most customers will use the out-of-the-box integration with ClearQuest, you may want to integrate with another CRM system. To accomplish this, you could do the following:

• Create a trigger type on mkactivity that creates a corresponding record in the CRM database when a developer makes a new activity.

• Create a trigger type on setactivity that transitions the record in the CRM database to a scheduled state when a developer starts working on an activity.

• Create a trigger type on deliver that transitions the record in the CRM database to a completed state when a developer finishes delivering the activity to the integration stream.

• Creating a trigger type on rebase that prevents developers from rebasing certain development streams. You may want to enforce this policy on a development stream that is being used to fix one particular bug.

• Creating a trigger type on setactivity that allows specific developers to work on specific activities.