MicroStation CONNECT - Remove example workspace.

RE: MicroStation CONNECT - Remove example workspace.

Marc Thomas — Tue, 08 Oct 2019 15:22:57 GMT

Yep, that works. Nice one.

RE: MicroStation CONNECT - Remove example workspace.

John Frampton — Tue, 08 Oct 2019 11:56:44 GMT

_USTN_INSTALLED_CONFIGURATION is a variable that points to a path by default. By setting it to 0 you are making it not found. You could set it to Null and <blank> and do the same.

RE: MicroStation CONNECT - Remove example workspace.

Brian Wagner — Mon, 07 Oct 2019 16:54:24 GMT

I was able to "hide" the Example Configuration from the WorkSpace dropdown when I changed _USTN_INSTALLED_CONFIGURATION to equal 0 in my /Organization/standards.cfg on my network. According to the Configuration Explorer, this variable doesn't have any parents or children and initial testing does not appear to result in any other errors.

RE: MicroStation CONNECT - Remove example workspace.

Brian Wagner — Mon, 07 Oct 2019 10:59:29 GMT

When I initially set-up the network workspace, I used the tutorial from the Learn Server "MicroStation CONNECT Edition Upgrade for CAD Managers: Configuration" which suggested using the WorkSpaceSetup.cfg and a Redirect.cfg in the Organization folder locally. This worked great for MicroStation CONNECT, but, we want to use the same base standards for our OpenRoads configuration. (I could not find a similar tutorial for OpenRoads networks set-up so I have been trying to figure it out using what I learned originally.)

Using ConfigurationSetup.cfg's _USTN_CUSTOM_CONFIGURATION combined with WorkSpaceSetup.cfg's MY_WORKSPACE_LOCATION variables from the local workstation, everything seems to be working for both MicroStation CONNECT and OpenRoads Designer. MicroStation is pulling standards from the correct network folder, Organization, and OpenRoads is using the network's Organization and Organization-Civil. The only thing I want to do is disable the "Example Configuration" from appearing, minimizing the confusion for staff.

To specifically answer your other questions: Yes, I have used the configuration Explorer and determined no errors and minimal warnings (hardcoded paths mostly) within my cfg files. Startup is from the Application shortcut with no arguments in the shortcut.

RE: MicroStation CONNECT - Remove example workspace.

Marc Thomas — Fri, 04 Oct 2019 19:56:07 GMT

Hi Brian,

Please can you give some info about your configuration?

Have you used ConfigurationSetup.cfg to redirect to your Custom Configuration?

Have you tried using Bentley Configuration Explorer to examine your configuration?

Are you starting the application(s) from configured shortcuts?

RE: MicroStation CONNECT - Remove example workspace.

Brian Wagner — Fri, 04 Oct 2019 14:58:59 GMT

Has this been included in any recent updates? In my set up, the workspaces in both "sections" link to the correct workspace but the Custom Configuration contains the redirect to our network base standards (which are supplemented in workspaces). If the user selects the workspace in the "example" category, it loads the C:/ drive standards and misses our Base Network Standards. Thanks!

RE: MicroStation CONNECT - Remove example workspace.

Brian Wagner — Thu, 03 Oct 2019 19:20:18 GMT

I am having the same problem. Both listings are actually pointing to the same folder. Does anyone have any insight?

RE: MicroStation CONNECT - Remove example workspace.

mriley — Tue, 20 Aug 2019 21:22:07 GMT

I have this same look when I call a -wc cfg from an ORD shortcut. The only lines in the cfg are to process a different path for the "MY_WORKSPACES_LOCATION" and then to process the MSLOCAL.cfg. This seems to obliviate the original Examples being shown in the bottom and displays the "double" you describe but with Examples at the top and Customize at the bottom. Stil lhave not figured out how to clean that up if its possible.

Mike

RE: MicroStation CONNECT - Remove example workspace.

Shannon Merryman — Thu, 31 May 2018 15:09:30 GMT

We're currently working on getting our environment for OpenRoads Designer built and we've seen this also. We actually get a "doubled-up" list from the 'CUSTOM' to the 'EXAMPLE' at this point.

I think we'd like to have a bit more flexibility with it, for example to remove it entirely or control the list shown and populate the 'EXAMPLE' with our own training / examples for our users from our materials.

We do not have an Example.cfg to edit or remove, at least as far as I've been able to tell, in order to implement even the above solution.

Shannon,

WSDOT

RE: MicroStation CONNECT - Remove example workspace.

Marc Thomas — Fri, 04 May 2018 11:14:02 GMT

I have filed Enhancement 888503 "User requests ability to hide Example WorkSpace from UI"

Having configured a lot of real-world V8i workspaces over the years I'm pretty confident that CONNECT Edition configuration is easier and more flexible than V8i, but it is different and requires some re-learning.

RE: MicroStation CONNECT - Remove example workspace.

StirlingH — Thu, 03 May 2018 02:10:44 GMT

It have been a while since I have visited this issue. It is really a poor solution. I don't want to give our users access to these examples as they are trained enough not to need them and we want to simplify choices as we don't want people accidentally opening projects in the wrong work space. Yes I know there are warning messages etc but that is the way we wan't it here. Since MicroStation V8i was so much easier to configure I think this is a backwards step by Bentley. A decision made by someone who does not use the product in the real world, does not listen to what the users want and has no imagination that users may use the product in ways the developers had not thought of.

RE: MicroStation CONNECT - Remove example workspace.

Marc Thomas — Fri, 08 Sep 2017 14:43:24 GMT

Hi Stirling,

We recommend leaving the example files available for people to use in conjunction with our training material and also as a personal sandbox. The configuration is designed to work this way so I don't see a configuration route that we could suggest.

If you change the name of Example.cfg to Example.txt (so you can revert if necessary) on each machine Example will not show up in the UI.