In CE17 there seems to be another layer of messy configuration options bar in already confusing config jungle. How can I get rid of them? Our Microstaton users no need to access any example configs as we use our company workspace only. Therefore I would like to turn obsolete items off so that only our own config options would be visible. What's the point making the GUI more complicated? Who needs this?
Documentation is here: Creating and Managing Configurations (bentley.com). The XML syntax is not currently included in help. It is covered by this new blog: Configuration Tips - Manage Configuration Utility.
Configurations are stored in C:\Users\...\AppData\Local\Bentley\MicroStation\10.0.0\prefs\configuration.xml.
This file can be copied to any users provided that the path(s) stored in the XML for each configuration is/are valid for each user.
The example configuration can be hidden by editing the XML, set the IsActive statement to false:
<IsActive>false</IsActive>
Development is continuing to work on this feature so these comments will be taken note of.
This feature was introduced in response to demand from our users for multiple configurations and does offer a more flexible mechanism for control of configurations, we need to do some further work to address the questions in this thread.
Marc
What is the relationship between ConfigurationSetup.cfg (in c:\ProgramData..) and configuration.xml (in User Pref folder) when Microstation launches? Does the XML read the CFG file? I need to know this when deploying out to 250 users.
In the default configuration, it appears the configuration.xml file overrides the ConfigurationSetup.cfg.
You can get around this by setting the _USTN_USER_CONFIGURATION variable to what you would normally set the _USTN_CUSTOM_CONFIGURATION variable.
Just make sure you do some serious testing prior to deploying to your 250 users.
Rod WingSenior Systems Analyst