Competencies and competency models can be versioned.
- The Competency Bank always displays the most recent version of the competency. When selecting competencies to include in a competency model, only the most recent version of the competency is available for selection.
- The Competency Models page always displays the most recent version of the competency model. When selecting competency models to include in a task, only the most recent version of the competency model is available for selection.
- The versioning behavior for competency models is dependent on whether the competency model is being used in a "locked task."
- When a competency model is not being used in a locked task, the current model version inherits changes to the model and underlying competencies. The competency model version number does not change.
- When a competency model is being used in a locked task, changes to the model or underlying competencies result in the creation of a new competency model version. The locked task continues to use the competency model version that was selected at the time the task was created.
In order to support the versioning of competencies and competency models, the models that are used in the following tasks are considered "locked":
- Competency Assessment
- Nested Competency Assessments
- Locked Observation Checklists - The competencies in an observation checklist are locked if the Lock Competency option is selected when the checklist is created or edited.
Competency Versioning - Auto-Versioning Rules
Competency Versioning - Impact across System
- The ordering of competency items and behaviors is removed at the competency model level. Item and behavior ordering now occurs at the competency level.
- Rating value attributes for competency behaviors at the competency level are normalized to match the rating scale used in the competency model. For example, in the scenario where a behavior rating is set to 3 out of 5, the rating value is normalized to 6 in competency models that use a 10 point rating scale.
- The rating value that is attributed to competencies and competency item development actions at the competency level are normalized to match the rating scale used in the competency model. For example, in the scenario where a development action maximum value is set to 3 out of 5, the development action maximum value is normalized to 6 in competency models using a 10 point rating scale.
- When a competency is added to a LO via the Course Catalog, the LO is also added as a development action with no minimum or maximum rating to the current competency version.
- When a LO is removed from a competency development action, the LO is only removed from the current version. If the LO is used in previous versions of the competency, then the LO remains in those versions.
- When a competency is removed from a LO, the LO is removed as a development action from all versions of the competency.
In the performance review PDF, the competency model version number appears appended to the competency model title.