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 |
Folder | Refresh |
Configuration | Refresh |
Configuration Version | There should be no versions shown |
Model | Open |
Model Version | There should be no versions shown |
Glossary | Refresh |
Glossary Version | There should be no versions shown |
Semantic Mapping | Refresh |
Semantic Mapping Version | There should be no versions shown |
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 – let us know how we can improve!