A member rule is a revision—typically a symbolic revision—attached to a member. You can use it with any command that allows you to specify a revision based on the member rule.

In the GUI, only the Check Out and Update Member Revision commands allow you to specify a revision based on the rule defined for the member.

You can set a member rule to specify a revision based on a symbolic location in the development path (working file, head revision, trunk tip, or member branch tip), property (state, label, or timestamp), current project configuration, or external project configuration.

For example, if you wanted to share members in project A with project B without using shared subprojects, you could apply a member rule to members in project B that links them to the corresponding members in project A. Then, you would update the members in project B by using the Update Member Revision command with the member rule.

To set a member rule, select Member > Properties > Set Member Rule.

After you create a rule for a member, you can also view and edit the rule in the Member Information view.

By design, applying a rule to update a member revision does not dynamically update the corresponding member revision in another project configuration. For example, if the member revision for member_1 is updated in project_A, the corresponding member revision in a variant of project_A with the rule configured to link to project_A is not updated with the same member revision.

To update the corresponding member in the variant according to the member rule, you can use the Update Member Revision command with the member rule, or your administrator can configure the ClientLink.js sample event trigger script that enables dynamic updating of linked member revisions under certain conditions. For more information, contact your administrator.