Configuration Blog Series - Changes to Configuration Levels

In MicroStation, configuration variables are stored at different hierarchical levels. Such hierarchy helps in segregating standards and resources at different levels. For example, you may have some standards that are common organization-wide and some are specific to a department. In such case, you would define configuration variables for accessing Organization-wide standards at a different level from the department-wide standards.

Each of these Configuration levels have a priority. The higher priority levels override the ones at a lower priority.  For example, any configuration variable definition made at User level overrides the definition of the same configuration variable at any other level, as the User Level has the highest precedence.

The following image highlights the difference between V8i and CONNECT Configuration levels.

Now, let us learn more about each Configuration Level and changes in CONNECT.


Configuration variables at this level are usually defined in the system Configuration Files which should not be modified by users. However, you can override the configuration variables defined at this level by any of the higher priority configuration levels.


Configuration variables at this level are defined in Configuration Files that are supplied by MicroStation or layered applications. Again, these files should not be modified by users.


The old “Site” level is now renamed as “Organization”. Organization-wide standards are specified at this level. By default, MicroStation provides sample folder structure with standards.cfg containing predefined Organization level configuration variables, which can be used as is or customized for your organization. Additional Configuration files pointed by the _USTN_CONFIGURATION configuration variable are processed at this level.


This is a new configuration level introduced in CONNECT. Standards that are applicable to a WorkSpace are specified at this level. In CONNECT, the purpose of categorization per WorkSpace can be different for each organization. For some, each WorkSpace can correspond to a client, for others it could identify department or team. Hence, the label “WorkSpace” in the UI is customizable. You can change it by changing the value of _USTN_WORKSPACELABEL in WorkSpaceSetup.cfg file.

 “WorkSpace” label changed to “Client”


The “Project” level is now renamed as “WorkSet”. Standards that are applicable to a WorkSet are specified at this level. Each WorkSet must have a WorkSpace .cfg file in the _USTN_WORKSETSROOT directory (<worksetname>.cfg). Additional Configuration files can be put into _USTN_WORKSETROOT for processing at this level.


This is a new configuration level added in CONNECT. The Role Configuration level is provided to set configuration variables values based on user roles. For example, say you want certain library files accessible only to Administrator and not to the drafters. In such case, you can create two user roles, namely, Admin and Drafter, and assign different Configuration variables paths to each.

You can create different configuration files (.cfg) for each user role and point the _USTN_ROLECFG variable to the desired cfg file. The _USTN_ROLECFG variable can be defined at any Configuration level above the Role Configuration level.  After the WorkSet configuration files have been processed, msconfig.cfg determines if there is a set value for the _USTN_ROLECFG configuration variable. If there is a value defined, that specific *.cfg is processed.


Though this level existed in previous releases, its behavior is slightly changed in CONNECT. You no more have the User selection in the UI. Changes made to configuration variables in the Configuration Variables dialog are now stored in Personal.ucf.

The following diagram illustrates the configuration variables that point to various folders.

In the next blog, we will learn about Configuration files in CONNECT.

translated German Wiki articles:
Konfiguration Wiki/Blog Serie – Änderungen an den Konfigurationsebenen