The IGNORE action means that the object must be ignored. When used with a migrate operation, it means that the behavior is equivalent to the object not existing in its migrate source location. When used with work area conflict detection, it means that any uncontrolled file with this action is ignored and not reported as a work area conflict. The reserved word IGNORE is not case-sensitive.
Example: WHEN %name ~ '*.tmp' IGNORE
In this example, objects with a .tmp suffix are ignored.
Here is the syntax of this built-in action:
SET nameExpression TO valueExpression
SET TYPE TO valueExpression
The first form specifies the name of the property using a nameExpression that is converted to a string. The string must be a valid Rational Synergy attribute name. The second form is provided as a convenient shortform that is equivalent to specifying a nameExpression of ’type’. The SET, TO, and TYPE reserved words are not case-sensitive.
The valueExpression specifies the value that is to be set for the property.
Example:
WHEN %name ~ '*.java' SET TYPE TO 'java'
WHEN %name ~ '*.perl' SET 'type' TO 'perl'
In this example, objects with a .java suffix are created with a Rational Synergy type of java, and objects with a .perl suffix are created with a Rational Synergy type of perl.
For migrate usage, the type of Rational Synergy attribute that is expressed in the generated import package depends on the type of the result of the valueExpression as shown in the following table:
Type of value | Type of Synergy attribute |
---|---|
Integer | integer |
Float | float |
Boolean | boolean |
String | A value containing any newline characters becomes text. If the value does not contain any newline characters, it becomes string. |
any other type | The value is converted to a String using the Java™ toString() method, and the rules for String as described above are applied. |
The BECOME and MAKE actions are used in migrate operations to express a relationship to or from the object being migrated and another object.
The BECOME action creates a named relationship from the specified the object to the object being evaluated. The MAKE action creates a named relationship from the object being evaluated to the specified object. The syntax of these actions is as follows:
BECOME relationExpression OF objectExpression
MAKE objectExpression MY relationshipExpression
The BECOME, OF, MAKE,, and MY reserved words are not case-sensitive.
The relationExpression is converted to a string and specifies the name of the relationship that is expressed in the import package generated by migrate. This name must be a valid Rational Synergy relationship name.
The objectExpression is converted to a string and must be the four-part objectname form of an existing Rational Synergy object.
Example:
WHEN %name='Utils.java'
BECOME 'associated_cv' OF 'task12:1:task:probtrac'
In this example, a file named Utils.java has an associated_cv relationship from the object task12:1:task:probtrac to it.
The STOP action is used in migrate operations to stop further processing of mapping rules for the current object. This action might be used to prevent the actions of previously evaluated rules from being overridden by later rules.