About Feature Revisions

When a feature is revised, all sub features related to the previous revision are also related to the new revision, all the parts and model versions in the GBOM are also related to the new revision, and all feature context rules are copied to the new revision.

See Also
Revisions Page
Creating a Feature Revision
Working with Builds

For example, when feature revision A is revised to revision B, the same sub features of revision A are also connected to revision B. For rules, the copy allows the rules to be feature-revision specific. Later changes to the rules apply to that feature revision only.

These items related to the previous revision, which will also be related to the new revision:

  • Images
  • Specifications
  • Reference documents
  • test case
  • Use cases

These items related to the previous revision will NOT be related to the new revision:

  • Routes
  • Models that define the feature as a candidate logical feature, variant, or option group
  • Models that define the feature as a committed logical feature, variant, or option group
  • Issues

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