Open Roads Workspace & Workset setup for Work Server

RE: Open Roads Workspace & Workset setup for Work Server

MaryB — Thu, 10 Nov 2022 21:37:18 GMT

Here is a list of blog articles that have some useful information about setting up workspaces, worksets and network resources.

There is also an entire forum dedicated to Product Administration that has a lot of additional information.

I have the C:\ProgramData\Bentley\OpenRoads...\Configuration\ directory structure duplicated on my network CAD standards drive.

This means that, as long as I can redirect the root folders, the rest of the paths stay "relative" and essentially unchanged. I have pulled the worksets out to their own directory because of the way we store our data, and the need for the workset DGNWS file to have write-access.

I use a combination of C:\ProgramData\Bentley\OpenRoads...\Configuration\WorkspaceSetup.cfg and ConfigurationSetup.cfg to handle that basic redirection. I still have a few kinks to work through, but it's functional.

Workspaces and configurations are definitely different than they were for decades.

RE: Open Roads Workspace & Workset setup for Work Server

Richard Boozer — Thu, 10 Nov 2022 19:42:13 GMT

I got it to work how you both mentioned earlier! Thanks for all the help!

RE: Open Roads Workspace & Workset setup for Work Server

caddcop — Thu, 10 Nov 2022 19:40:24 GMT

The capability mentioned in Paul Cusack's reply can be combined with the built-in workspace capabilities, to get Project Folders working in multiple locations. To accomplish the same thing in V8i took a lot of manual customization of many CFG files. At the other firms I worked, we generally had one person create the Project files on the network for everyone to use. While it might be possible to allow any user to create projects in the workspace, the steps necessary to accomplish this and to maintain uniformity and consistency might be too much to expect.

RE: Open Roads Workspace & Workset setup for Work Server

Richard Boozer — Thu, 10 Nov 2022 16:26:48 GMT

I did both of these things and set up the configuration setup and the workspace setup on my local drive to direct it to the "T:\Configuration\Organization-Civil" folder but anytime I make a workset that doesn't also have all of those folders/files from the Standards in the "Organization-Civil" folder, none of our levels or anything are in the dgns that are created.

RE: Open Roads Workspace & Workset setup for Work Server

caddcop — Thu, 10 Nov 2022 15:05:48 GMT

The Organization-Civil folder an contain multiple Agency/Client/Whatever folders for as many different standards as you need. You can then define the variable CIVIL_ORGANIZATION_NAME to match the folder name and CFG filename stored in that folder, in the Workspace CFG file that the menu's call. These can be local folders or a network share.

Additionally, once you move to ORD 2022 R1, the startup screen (or backstage after pressing Close (Ctrl+W) supports multiple configurations in multiple locations.

We place most of our main workspace files in that main folder under Organization-Civil and while there is an entire folder structure under our WorkSpace for additional settings, we do not store many things in that structure.

Workspaces are very different than prior releases, so even those of us that knew and understood CFG files "like the back of our hand" find ourselves having to relearn a lot. The changes with 2022 R1 are nice but did change how a number of things worked prior to it, so even that caused a few hours of head scratching and testing before I was comfortable with their new operation.

RE: Open Roads Workspace & Workset setup for Work Server

Richard Boozer — Thu, 10 Nov 2022 14:43:01 GMT

We only use the DOT's Standards for every project is there any way I can keep from copying all of the folders/files to every single workset? Thank you for mentioning the template selection which would definitely make it easier to copy all of the files if that is the only way.

RE: Open Roads Workspace & Workset setup for Work Server

Paul Cusack — Thu, 10 Nov 2022 00:26:26 GMT

_USTN_WORKSETSROOT can be used to define the folder that contains the workset folders and configuration files and it can reside in a location that is separate to the main workspace and configuration folders. The WorkSpaceSetup.cfg is setup to allow users to modify the MY_WORKSET_LOCATION variable to redirect the workset folders but if that is not suitable then you can directly modify _USTN_WORKSETSROOT

When creating new worksets there is an option to select a "template" that is a pick list of the existing workset folders. The chosen template folder and all of its files (including it's cfg file) will be copied to the new name for the workset being created. See https://communities.bentley.com/products/microstation/b/microstation_blog/posts/configuration-blog-series---dgnws-file-and-workset-template