Skip to main content

Single Version and Configuration Licenses

The license for some editions only allows one configuration in the repository and only one version of any object. I.e., version and configuration management are disabled and not represented in the user interface. The abbreviated options affect the choices in the context menu for the following objects as detailed here:

Repository Item

Menu Items

Repository

Refresh
Operations
View Links

Folder

Refresh
Rename
Edit security
Operations
View Links

Configuration

Refresh
Rename
Edit Security
Operation
View Links

Configuration Version

There should be no versions shown

Model

Open
Search
Refresh
Rename
Import
Create Like Model
Edit Security
Operation
Remove from current configuration
View links
Delete

Model Version

There should be no versions shown

Glossary

Refresh
Rename
Edit Security
Operation
Add to current configuration
View Links
Delete

Glossary Version

There should be no versions shown

Semantic Mapping
Data Mapping

Refresh
Rename
Edit Security
Operation
Add to current configuration
View Links
Delete

Semantic Mapping Version

There should be no versions shown

Information note

A repository database that has been initialized when a single version / single configuration license is applied will NOT have a naming standards model. Thus, one cannot apply a more complete license and expect to use that database, as it is incomplete. Instead, you must initialize a new database with the new license applied.

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – please let us know!