New to Dynamic Managed Workspaces.. Getting workspace standards to load?

Do you have a link to what's in the Predefined 1.7 CSB?

I have some rules I try to follow in my setup:

1. Don't try to make one workspace that automatically chooses between v8i and connect. Just keep them completely separate.
2. Don't try and import an existing non-projectwise configuration. You end up doing more editing than not.
3. Keep CSBs as simple as possible and do most work in cfg files stored in ProjectWise.
4. Avoid needing to create CSBs for every project.

I think 3 is key for us. For example, the predefined CSB I use in my basic-used-for-experiments workspace is:

I set 2 main variables - the root location of my configuration in the datasource and _USTN_CONFIGURATION. The root location is set as a ProjectWise folder with a string appended to it. 99% of my variables are built using the root location variable, i pretty much never use the ProjectWise Folder or File types in setting variables in CSBs after this one.

Because I set _USTN_CONFIGURATION in this block, ORD will auotomatically load the WorkSpaceSetup.cfg in the folder that _USTN_CONFIGURATION points at. I don't need to manually %include it in the CSB, ORD does it automatically. I put all my real workspace setup in that WorkSpaceSetup.cfg file.

I pretty much repeat this same process for Organization, WorkSpace and WorkSet CSBs. Set the pointer variable in the CSB and let ORD automatically load the correct cfg file from projectwise.

I work for a consulting firm so we have to plug in a lot of different DOT/municipality/federal standards for different projects. That's a little more complicated as support for the Civil Organization isn't built into ORD natively and I do have to do a manual %include to get the right cfg file. I handle that at the ProjectWise Customer level.

To add to Kevins reply, the "WorkSpaceSetup.cfg" for OpenRoads defines a variable called:
CIVIL_ORGANIZATION_ROOT
which is pointing to "$(_USTN_CONFIGURATION)Organization-Civil/" by default.

If you define that variable in your CSB it should help solve the issue.

This is my main csb

Location of the "Common_Predefined.cfg"

This is the only mod to the "WorkAreaPWSetup_ file

This is the location of the "Standards" that I need to get loaded:

Sorry I think I hit a button that rejected a reply. So sorry

Only using OpenRoads at the moment.

It doesn't look like they are using the Organization Civil area on that then. Can you confirm that the standards load in MicroStation (i.e. is it and OpenRoads specific problem)?

The KDOT configuration does not use Organization Civil. (outside of projectwise) Instead it installs itself as a WorkSpace in the Configuration\WorkSpaces\KDOT folder for each product you have installed. Most of the standards are in the WorkSpaces\KDOT\Standards folder.

When I set ours up i moved all that around into a Civil-Organization type structure instead and used that, but it took me a while.

The KDOT configuration does not use Organization Civil. (outside of projectwise) Instead it installs itself as a WorkSpace in the Configuration\WorkSpaces\KDOT folder for each product you have installed. Most of the standards are in the WorkSpaces\KDOT\Standards folder.

When I set ours up i moved all that around into a Civil-Organization type structure instead and used that, but it took me a while.

Thank you Kevin. I am trying my best to just go with the out of the box from KDOT to make it easier since they are trying to do quarterly updates.

I might have to do as you have stated instead.

The KDOT workspace cfg sets these variables up to use as a basis for loading standards

_KDOT_WORKSPACESTANDARDS=$(_USTN_WORKSPACESTANDARDS)
_KDOT_WORKSPACEROOT = $(_USTN_WORKSPACEROOT)
_KDOT_WORKSPACESROOT = $(_USTN_WORKSPACESROOT)
_KDOT_Civil = $(_KDOT_WORKSPACESTANDARDS)_Civil/

I had to replace those with our own values, but since I don't use the dynamic workspace I'm not really sure how to handle that inside of that.

Yeah, i'm not looking forward to that. I may have shot myself in the foot. Fortunately i retained their directory structure, but i did rework their config files quite a bit to use a single cfg file.