Versioning Redesign Enhancements - General Availability
Prior to this enhancement, preventing erroneous versioning and assignment of training to end users was costly for organizations which resulted in extra administrative time for troubleshooting, leading to compliance and training completion tracking issues.
This enhancement provides new Curriculum versioning workflows for consistent and reliable behavior whenever a Curriculum Child Learning Object (LO) is versioned or whenever a Curriculum structure is modified simultaneously, so that the right users get the right training at the right time while maintaining compliance with respect to tracking training completions.
The enhancement enables enhanced performance optimizations for back-to-back versioning including administrator and Child LO versioning for Curriculum.
The new versioning workflows are now available in the General Availability for all customers in the July 2023 Release.
How Does this Enhancement Benefit My Organization?
- Administrators who can version Curricula can see if the versioning is still in progress via an icon if versioning happened through administrator structure changes.
- Administrator overhead to troubleshoot is significantly reduced as this avoids and prevents erroneous versioning and assignment of training to end users for back-to-back scenarios.
- Robust and reliable workflows make sure that the users are always assigned the right version of the Curriculum or Curriculum Child LOs to remain compliant.
- Provides improved reliability, scalability, and quality with system versioning flows.
Use Cases
Use Case 1: Materials or online course LOs belonging to the same Curriculum are versioned back-to-back. It creates the latest version of all Materials or Online Course LOs in the latest version of the Curriculum (Child LO Versioning).
Use Case 2: Material M1v1 is part of Curriculum C1v1 and M1v1 is versioned to M1v2. However, if Material M3v1 is added to Curriculum C1v1 via administrator structure changes causing the Curriculum to version, then the Curriculum will have M1v2 and M3v1 in the latest Curriculum version, thus maintaining consistency.
Use Case 3: Material M1v1 is part of Curriculum C1v1 and M1v1 is versioned to M1v2. However, if M1v1 is removed from C1v1 via administrator structure changes, then the Curriculum will not get versioned, as Child LO Material M1v1 will be removed from the Curriculum structure.
Use Case 4: Curriculum C1v1 is a child LO under the Parent Curriculum C2v1. If we version Material M1v1 to M1v2 under C1v1, triggering the child LO versioning flow, C1v1 will be versioned to C1v2, and C2v1 gets versioned to C2v2. But if we version C1v2 to C1v3 via an administrator structure change, then C2v2 remains C2v2 and no parent Curriculum versioning happens.
Use Case 5: In case of Curriculum versioning via Structure changes by Admins, when there are two Materials in the Curriculum Structure, M1v1 and M1v2 which are versioned using Append mode and both are Active (old version has still not expired) then Admin tries to remove M1v1 to create to create new version before expiration of older one, then M1v1 will not be removed from the structure in the new version which will be created. It will be removed only once it expires. Customers need to review changes in case of Append scenarios accordingly.
Considerations
- This enhancement supports only versioning that occurs due to administrator structure changes or Child LO versioning.
- This enhancement is specific to the back-to-back versioning scenarios that lead to versioning inconsistencies for curricula.
Frequently Asked Questions (FAQs)
What happens when a child LO is removed from the Curriculum structure by an administrator and at the same time child LO versioning requests occur for the same LO?
In this case, the Curriculum versioning will not happen as the Child LO no longer exists in the Curriculum Structure.
Resources
Implementation
Enhanced Versioning will be enabled in phases based on the customer's swimlane.
| Swimlane | Deployment Date |
|---|---|
| AU SL1 (AWS) | 21 July 2023 |
| CDG SL4 (AWS) | 21 July 2023 |
| JP SL1 (AWS) | 21 July 2023 |
| FRA SL1 (AWS) | 28 July 2023 |
| CDG SL1 (AWS) | 28 July 2023 |
| UK SL4 (AWS) | 28 July 2023 |
| LAX-SL1 | 11 August 2023 |
| LAX-SL2 | 11 August 2023 |
| LAX-SL4 | 18 August 2023 |
| LAX-SL5 | 18 August 2023 |
| UK SL1 (AWS) | 18 August 2023 |
| UK SL2 (AWS) | 25 August 2023 |
| US SL1 (AWS) | 25 August 2023 |
| UK SL3 (AWS) | 1 September 2023 |
| US SL2 (AWS) | 8 September 2023 |
| LAX-SL3 | 15 September 2023 |