Additional uses for UCM triggers

In addition to using UCM triggers to enforce development policies, you can use UCM triggers for the following purposes:

• Create an integration between UCM and a change request management (CRM) system. Although most customers can use the UCM integration with Rational® ClearQuest®, you may want to integrate with another CRM system. To accomplish this, you could perform the following steps:
  • 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.
• Create 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.
• Create a trigger type on setactivity that allows specific developers to work on specific activities.