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.
Regards
Marc
Why was this feature introduced if development is still working on it?Why was it developed with no way to protect it from the users?
Does the configuration.xml NEED to be local, or is there a way to locate that on a network drive as part of an Organization configuration?
MaryB
Power GeoPak 08.11.09.918Power InRoads 08.11.09.918OpenRoads Designer 2021 R2
I also see a variable in the personal.ucf :
_USTN_LAST_ACCESS_CONFIGURATION
which is a bit confusing from
_USTN_LAST_ACTIVE_CONFIGURATION
in the cache.ucf
Timothy Hickman
CADD Manager | CADD Department
timothy.hickman@colliersengineering.com
Main: 877 627 3772|
1000 Waterview Drive Suite 201 | Hamilton, New Jersey 08691
Well this is cute. There is a new variable:
_USTN_CACHECFG that points at the cache.ucf file. It is locked.
There is also a _USTN_CACHEWSCFG that points at a WORKSPACE.ucf where WORKSPACE is the name of the (current?) workspace, the path is the user prefs folder. This file doesn't exist on my system howerver.
I added a variable to the cache.ucf to see the order it is loaded in and it loads before the Personal.ucf so theoretically anything in the Personal.ucf should override the cache.ucf.
I've no idea why these cache files are needed either.
looks like Bentley's getting ready for an early easter egg hunt.
No idea what that thing is for (for someone else), but I'd like to know if I can just make it all go away. I hate having stuff like that up on my screen that I must constantly ignore.
Connect r17 10.17.2.61 self-employed-Unpaid Beta tester for Bentley
Hi Bob,I haven't tried this with Update 17, but you could try setting both _USTN_USER_CONFIGURATION and _USTN_CONFIGURATION to your configuration path (as either command line arguments or as Windows Environment Variables) and that should ignore the local and custom configuration setups.