About Feature Revisions

When a feature is revised, the related objects undergo the following changes: all subfeatures related to the previous revision are also related to the new revision (For example, when a feature revision A is revised to revision B, the same subfeatures that are on revision A are also connected to revision B.), all the parts/products related to the feature via the GBOM relationship are also related to the new revision, and all feature context rules are also copied to the new revision (This ensures that the new rule objects are feature-revision specific. Later if the changes are done to the rules, they apply to the feature instance in context).

Related Topics
Revisions Page
Creating a Feature Revision
Working with Builds

The following is a list of objects on the previous revision which will also be connected to the new revision:

  • Image
  • Specification
  • Reference Document
  • Test Case
  • Use Case

The following is a list of objects on the previous revision which will NOT be connected to the new revision:

  • Engineering Change (EC) objects via the Affected Items or Implemented Items relationships.
  • Route objects
  • Model objects via the Candidate Features relationship
  • Model objects via the Committed Features relationship
  • Issue objects
  • Feature List objects via the Feature List To

When a feature is revised, its parent feature list objects are not changed. For example, if Revision A of a feature is connected to another product or product configuration via the feature list object, then that feature list object will always point to Revision A of the feature.