Please Note that the behaviour described in the post is no longer available. I am investigating this change and will update the post with the results.
24 May 2020
In CONNECT Edition - Custom Configuration - Part 1 : Initial Creation Steps I described how the installer can be used to specify the location of your Custom Configuration by setting the value of the variable _USTN_CUSTOM_CONFIGURATION listed in "C:\ProgramData\Bentley\MicroStation CONNECT Edition\Configuration\ConfigurationSetup.cfg" to the chosen Network Configuration path; e.g.: \\hal\CONFIGURATIONS\MCE.
We also have a related variable, _USTN_USER_CONFIGURATION.
In the majority of organizations the WorkSpaces configuration level will provide the necessary granularity to support departmental or other high level business structures so a single Custom Configuration should be sufficient to meet the organization's needs for production.
However from a support perspective it is useful if not essential (and now easier!) to have a work in progress or test copy of the operational Custom Configuration.
Simply define (and this is a manual CFG edit, which is fine in an administrative context) _USTN_CUSTOM_CONFIGURATION to specify the WiP Custom Configuration, e.g.:
Once that variable is added a third option, User Configuration, will appear when selecting a WorkSpace:
I strongly recommend that this is only used for the administrative purposes described above, it is unnecessary for production use.
Translated German Wiki articles:CONNECT Edition - Was bewirkt _USTN_USER_CONFIGURATION?
Hi Duncan, you are correct. This is no longer working as I found when writing this post. Having looked at this one I think the behaviour you are seeing is the original design intention. I am discussing with colleagues and have filed Defect 1095759 to get it checked out. I've added a note at the head on the post.
If I define _USTN_USER_CONFIGURATION it overrides my custom configuration, what do I need to do to get the workspace drop down to display the 3 configurations as you show above, or evne jut custom and user?
I used to have this but seems that in recent versions if USTN_CUSTOM_CONFIGURATION is defined and exists then it overrides and hides the installed example configuration, and if USTN_USER_CONFIGURATION is defined also it overrides both.