Use versions
A version stores the unique state of a model at the time it is saved; for example, in release cycle management, you can specify which version of a model, with which changes, is valid as of a specific point in time. Versions cannot be modified.
Individual models, several models, or all models of a database that are available at the time of versioning can be versioned. The versioned content of a database is summarized in a change list. A change list contains selected content from a database that is versioned collectively and stored in a change list under a change list number.
Versions are only available in versionable databases. When creating a new database, select the Versionable option. To use version management, you must have at least the Version access privilege for the corresponding model. You can version models and thus store different versioning states of a model. The following versioning states exist:
Workspace
Identifies the model that has not yet been versioned. The workspace state represents the current state of a model and is editable.
Current version
Corresponds to the model last versioned. This state represents the model as it exists in the workspace state. After versioning, the model is available in read-only mode.
Current version
Corresponds to the model last versioned. This state represents the model as it exists in the workspace state. After versioning, the model is available in read-only mode.