Version Equivalence Alignment Use Cases

Use Case 1

  • Create a Material Version 1 (M1V1).
  • Assign it to the Users (U1 and U2) and complete M1V1 as a Standalone.
  • Reversion the M1V1 to M1V2.
    • Version Preference - Replace
    • Effective Date - Immediately
    • Version - All versions
    • Status - Not Started, In Progress, Completed
    • Assign To - Users with Previous Version(s) on Transcript
    • Version Equivalency - Require Retraining (Deselect the users)
  • Reversion the M1V2 to M1V3.
    • Version Preference - Replace
    • Effective Date - Immediately
    • Version - All versions
    • Status - Not Started, In Progress, Completed
    • Assign To - Users with Previous Version(s) on Transcript
  • Version Equivalency - Versions Equivalent.
  • Select U1 and U2 at the time of Reversion.

Before the enhancement: Both U1 and U2 have M1V3 Equivalent Training Completed with M1V1.

After the enhancement: Both U1 and U2 have M1V3 in a registered status.

Use Case 2

  • Create a Material Version 1 (M1V1).
  • Assign it to the Users (U1 and U2) and complete M1V1 as a Standalone.
  • Reversion the M1V1 to M1V2.
    • Version Preference - Replace
    • Effective Date - Immediately
    • Version - 1.0
    • Status - Not Started, In Progress, Completed
    • Assign To - Users with Previous Version(s) on Transcript
    • Version Equivalency - Versions Equivalent
  • Select the user U2 at the time of Reversion
  • Reversion the M1V2 to M1V3 
    • Version Preference - Replace
    • Effective Date - Immediately
    • Version - 1.0
    • Status - Not Started, In Progress, Completed
    • Assign To - Users with Previous Version(s) on Transcript
  • Version Equivalency - Versions Equivalent
  • Select U2 at the time of Reversion.

Before the enhancement: U2 has M1V3 in a version equivalent status.

After the enhancement: U2 has M1V3 in a version equivalent status. No change on current behavior.