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?
Yongan.Fu said:Personal thinking, this new feature seems extend the management layers from two(Workspace/Workset) to three(Configuration/Workspace/Workset).
I like the concept of adding another configuration layer, but not managed by a user-specific file in the user LOCALAPPDATA folder and not something that is automatically on for everyone.
I have clients that use a combination of MicroStation and ORD where the MicroStation users use the same Configurations as the ORD users. For ORD you can redirect to different configurations based on the version, MicroStation you only get one.
Using this new feature you can make ORD 10.9, 10.10, (and eventually 10.11) configurations available at the same time in MicroStation from the WorkPage.
Rod WingSenior Systems Analyst
This is so irritating. A 'feature' that no one wants that is on by default and can't easily be turned off. CAD admin pain in the neck, confused users. It's just another thing driving us away from Bentley.
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
Hi Stirling,
Once the XML is edited to <IsActive>false</IsActive> your users will only see the Custom Configuration:
What's the best way to suggest changes to this feature? Microstation ideas site, post on communities or open a service request?