42 Administering Revision-Specific Relationships

This chapter explains how to configure the Revision-Specific Relationships feature in Agile PLM.

42.1 Revision-Specific Relationship Attributes

When Agile PLM is first installed, revision-specific relationships are disabled by default. To use revision-specific relationships, the Agile administrator must enable the appropriate relationship tabs attributes and define the needed privilege masks for user roles.

Revision-specific relationships are supported for the revision-controlled classes Parts, Documents, and Prices. To create a revision-specific relationship, the revision-specific relations attributes must be enable for both classes in the relationship. However, you can choose to display the revision for some classes, but not for others.

For example, you may choose to enable revision-specific relationships for only Parts and ECOs. In a relationship between a Part and an ECO, the relationship defaults to the LATEST revision on the Relationships table of the ECO, and then the user can select a specific revision. In contrast, in a relationship between a Part and a Deviation (not revision-specific relationship enabled), the relationship defaults to ALL revisions on the Relationships table of the Deviation.

The Relationship table (Content table in PPM) attributes that are used to track revision-specific relationships are:

Revision

Enabling this attribute is required for revision-specific relationships. When this attribute is enabled, and the user has the appropriate Read and Modify privilege masks, then the user can select a specific revision from the Revision cell drop-down list on the Relationships table

Read and Modify privilege masks must include the Relationships table Revision attribute in the AppliedTo list.

When the Relationships table Revision attribute is enabled, then the Relationships table More menu selections for Accept New Revisions and are also enabled

Important:

Before you enable a Relationship table Revision attribute, plan how you want to use revision-specific relationships in your company. After users have created revision-specific relationships, the revision-specific relationship feature is not easily disabled.

When you have enabled the Revision attribute (set the attribute Visible property to Yes), and then you save your modifications to the attribute properties, the following Warning is displayed:

WARNING! If you enable the revision attribute, it cannot be easily disabled later. Once you have enabled the revision attribute, users are allowed to create multiple Revision-Specific relationships on the Relationships tab. If you wish to disable the revision attribute later, you must first resolve all multiple rows (one row for each revision of the same object) to a single ALL to All relationship row for all <object class name> with Revision-Specific relationships. Click Yes to proceed.

Change

This read-only attribute shows the change (ECO, MCO, or PCO) associated with the selected revision in the Revision cell. If this attribute is visible, and the user has read privilege for the attribute, when the user clicks the change number, the use is navigated to the change object.
Track Impact

Track Impact determines whether or not to track the impact of a new release of the revision-controlled target object.

Track Impact is editable inline if the user has the appropriate modify privilege mask AppliedTo property. To edit Track Impact, the target must be revision-controlled.
Impacted Flag (image)

When Track Impact is set to Yes, then the Track Impact flag indicates that the Relationship target object has changed and has a new revision.

If the selected revision is Latest, then the flag is cleared when the user selects the relationship row and chooses More > Accept New Revision.

Refer to Getting Started with Agile PLM for more information about revision-specific relationships.

42.2 Revision-Specific Relationship System Settings

The preference Display Change on Relationship Tab Revision Dropdown determines whether the change number associated with the selected revision is displayed beside the revision in the Revision drop-down list. See "Default Systemwide Preferences."

The Copy Relationships to Rev SmartRule determines whether or not the relationships table is copied to the new revision of a revision-controlled object. See "Copy Relationships to Rev."

42.3 Privileges for Revision-Specific Relationships

In order to use revision-specific relationships, users must have the appropriate Read and Modify privilege masks.

The user requires Read privilege mask that includes Revision, Change, Track Impact, and Impacted Flag (image) in the privilege mask AppliedTo property.

To create a revision-specific relationship, the user requires a Modify privilege mask that includes at least Revision in the AppliedTo property. Include Change and Track Impact in the AppliedTo property depending on the capabilities you wish to grant to the user. The Impacted Flag (image) attribute does not appear as a choice in the Modify privilege mask AppliedTo dialog because it does not require a Modify privilege mask.