About the Change Action with Applicability Release Process

The release process for a CA with applicability depends on the kind of proposed change. Proposed changes can be for either parent parts or child parts.

Configured parts will not be revised; however, released configured parts can be updated under the same revision using a new change order:

  • Released configured parts will always be connected with “For Update” requested change and therefore no new revision will be created for configured parts.
  • All EBOM Pending relationships will be committed or converted to the current under the same revision.

This page discusses:

Parent Parts

When the proposed change of a CA is a parent configured part and:

  • ...is in the Release state:
    • A new revision is created when the CA is released.
    • The pending EBOM changes are floated from the old revision to the new revision of the part.
    • The released EBOM changes are replicated onto the new revision.
    • The pending proposed change relationships are floated to the new revision.
    • The new revision is released.
  • ...is in the Preliminary state:
    • Only the part is released. The pending proposed change relationships are updated with a Requested Change value of "For Minor Revise."

Child Parts

When the proposed change of a CA is a child part, it is released only when the CA is released, provided the part is not already released.

The requested change value is updated to "For Minor Revise" if the part is connected to other pending CAs as a parent affected part.