About Global Trigger Types

Resolving The Problem

By design, trigger types must be created locally in each VOB.

Trigger types, unlike other metadata types (labels, attributes, branches, elements, hyperlink), cannot be created as global resources in an Administrative VOB because they cannot properly traverse hyperlinks; which is how the Administrative VOBs connect to their client VOBs.

There is a method that will allow you to more easily generate a trigger type across multiple VOBs and allow trigger types to be used as a global resource like other metadata.

While trigger types cannot be created as a global type in an AdminVOB, they can be copied from one VOB to another. Thus, you can store your trigger types in an Administrative VOB and copy them to the client VOBs when needed.

The cptype (copy type) command creates a new type object that is a copy of an existing type object. The existing and new objects can be in the same VOB, or in different VOBs. The copy can have the same name as the original only if you are making the copy in a different VOB.

The two objects, original and copy, do not retain any connection after you execute this command. They are merely two objects with the same properties, and perhaps even the same name. If there are any changes made to the trigger, such as by using cleartool mktrtype -replace, then those changes must be made manually to each copy of the trigger, or you must perform the copy again using the -replace switch; see the cptype reference page for more information.

In order to copy a trigger type from one VOB to another, the syntax would look something like this:

cleartool cptype trtype:NO_RMELEM@\admin_vob trtype:NO_RMELEM@\production_vob

Example:

To copy a trigger type from one VOB to another, the cptype command can be used as follows:

cleartool cptype trtype:NO_RMELEM@\source_vob