We went through the AMP program with ChucK L and with his assistance, create a local workspace/workset. I was able to copy this to a network share and get it up and running, as a custom configuration while preserving the delivered examples.
Now, as we are continuing to refine our workspace, we wanted to move the Workspace to a new location and leave the worksets under their original location (at least for now). Everything I have tried to get the new location for the workspace has failed. Currently, the custom configuration option is now gone from the workspace menu. I was very experienced with CFG file processing in prior versions but CONNECT has thrown me for a loop. When I look at the contents of some of the CONNECT CFG files and try to follow along with their logic, I see many things that appear to make zero sense.
is there some type of follow the bouncing ball explanation of what occurs in these files and what makes the Example Configuration and Custom Configuration both display and what minimum files must exist where for this to work?
There appears to be some type of internal management within MicroStation/ORD of the _USTN_CONFIGURATION, _USTN_CUSTOM_CONFIGURATION, and _USTN_USER_CONFIGURATION variables that is a bit mysterious. The file C:\ProgramData\Bentley\OpenRoads Designer CE\Configuration\ConfigurationSetup.cfg will sometimes change for whatever reason.
I've had good success defining _USTN_CUSTOM_CONFIGURATION in a configuration file that gets loaded earlier in the SYSTEM level, prior to the loading of ConfigurationSetup.cfg. I define the variable and then lock it (%lock _USTN_CUSTOM_CONFIGURATION) so that it does not get updated by any subsequent configuration file.
The path defined by the _USTN_CUSTOM_CONFIGURATION should contain your custom Organization, Organization-Civil, and Workspaces folders. When set up in this manner the _USTN_ORGANIZATION, CIVIL_ORGANIZATION_STANDARDS, and USTN_WORKSPACES_ROOT folders will be directed to these custom locations.