ORD/ORLD Update 10: _USTN_CUSTOM_CONFIGURATION is being ignored

Hi

I have just installed OpenRoads and OpenRail Designer Update 10 but now I can't use our custom WorkSpaces :-(  ...is there anyone who can confirm this bad behavior?

Apperently custom configuration is being totally ignored in OLD/ORLD Update 10 unless they are saved in the installation folder (C:\ProgramData\Bentley\OpenR...).
It should be possible to create custom WorkSpaces (and WorkSets and Organization level) by defining the path to this, using the configuration variable: _USTN_CUSTOM_CONFIGURATION = "my Path", in the ConfigurationSetup.cfg file.
This works fine in ORD/ORLD Update 9 and MicroStation CE Update 16.
Because of this we can't use our custom WorkSpaces etc. :-( ...a poor workaround is to copy all the WorkSpaces and Organization folders to the installed configuration folder (then it works)!

Just to make sure it isn't our normal setup which is responsible I have made a default installation at a clean pc and (without any custom configuration). When ORD has loaded the WorkPage it only see the WorkSpaces in the installation folder. But after a dgn file is opened (and ORD is fully loaded) we can see that _USTN_CUSTOM_CONFIGURATION is defined correctly!

Unless there's something I miss this is a major bug and Bentley have to fix this as soon as possible ...PLEASE!

...and why is there any differencies between MicroStation Update 16 and ORD/ORLD Update 10 when they should both use PowerPlatform 16?

I've also file SR 7001272613

Best regards

Anders

Parents Reply Children
  • Hi Benzi

    Thanks for your reply and screenshot.

    Unfortunately I can't find any documentation about this new "Manage Configurations" dialog.

    I've have searched for where those settings is stored and apparently OpenRoads writes the modifications into a new "configuration.xml" file which is placed in the "prefs" folder along with the other user configurations. So this customization is stored at the current Windows user (under %LOCALAPPDATA%).
    This is not suitable when we are using a common "Configuration" for our Bentley products ...so I'll stick to defining _USTN_CUSTOM_CONFIGURATION = "our-network-path" ...and ignore the new "user" Manage Configurations dialog.
    I don't know if it's possible to control the path to the "configuration.xml" file. In my humble opinion Bentley should make a configuration variable which control the path to the file so I can put this on our network.
    Also (as Rod Wing wrote) there needs to be consistency in the GUI between MicroStation, OpenRoads etc. when on the same PowerPlatform.

    Best regards

    Anders