Locking Versions

You must be a SAS Decision Manager administrator to lock and unlock a version. Administrators can lock a project version to prevent users from modifying some properties and files for the version’s models. The champion version can be locked when the project champion model is approved for production or is pending approval. After a version is locked, users cannot perform the following tasks:

SAS Decision Manager administrators remain authorized to perform these activities. If the champion model is not deployed to an operational environment, then an administrator can unlock a version so that users can change the models. Advanced users can still modify the Attachments, Reports, and Scoring pages after a version is locked.

When the champion model has been used in production scoring, you must unlock the model if you want to change the contents of the champion version. However, use caution in modifying the version content. If the model UUID and revision number for the score code in production scoring environments are always recorded, then you can modify a version even after the version is deployed to production environment.

If you attempt to delete a project that contains a locked version, SAS Decision Manager displays a message indicating that you cannot delete a project that contains locked versions. An administrator must unlock the versions before the project can be deleted.

Locking a version restricts the activities that you can do with the project. You normally lock a version after you declare a champion model in preparation for deploying the champion model to a production environment.

If changes to a model are required after the version is locked, an SAS Decision Manager administrator can unlock the version.

For more information about versions, see Lock and Unlock a Project Version.