Where and how is the variable _USTN_WORKSETDGNWS defined?

Question

I am trying to configure ORD CE for ProjectWise. 
 Our folder structure does not support worksets under workspaces but there a videos on how to configure that. I have been successful in making out projects work as worksets and associating them with a workspace. However, my efforts to enable the sheet index (and whatever else a DGNWS file provides)have failed. I have defined a common location for the Workset CFG files and location where the DGNWS file should be created using _USTN_WORKSETSDGNWSROOT. 
 But I cannot figure out how to define _USTN_WORKSETDGNWS in PW. According to its description, it should be the full path file name of the DGNWS file. But in my PW Managed Workspace, it is being defined to the Workset name only and according to the Configuration Dialog box, it is being set at a System Level, While most of my workset variables at reported to be correctly set to Workset Level. 
 I discovered that if I list the Configuration Variables using the Show Configuration Variables command of the dialog box and compare its list to the Summary of Variables from an MSDEBUG.TXT file, there are a number of assignments that are missing. Particularly glaring is the _USTN_WORKSETDGNWS assignment. In fact, I have searched every CFG I could find and do not see it listed anywhere. 
 If it is automatically generated, are there rules and conditions that can effect its assignment? I need to figure out why I cannot get the variable and its operational purpose to function in Project Wise.

Marc Thomas · Accepted Answer

I've been working on some non-ProjectWise configurations for users over the last few weeks and offer the following suggestions relating to the DGNWS. Where a configuration and project folder structure is consistent I'm recommending that key folder redirections are made in the WorkSpaceSetup.cfg in the custom configuration. For clarity of purpose we use the name 'Standards' for the root folders containing DGNLIB and other resource folders. For WorkSets this name is set by _USTN_WORKSETSTANDARDSDIRNAME. That's easy to spot, however I've noticed that MicroStation hardcodes the 'Standards' folder name in msconfig.cfg (which I will follow up on). This is easily fixed by first defining _USTN_WORKSETSTANDARDSDIRNAME with a user's folder name, then defining: _USTN_WORKSETSTANDARDS = $(_USTN_WORKSETROOT)$(_USTN_WORKSETSTANDARDSDIRNAME)\ to include the redefined folder name. having done that the DGNWS can then be located in the WorkSet 'Standarsd' folder by defining: _USTN_WORKSETDGNWS = $(_USTN_WORKSETSTANDARDS)$(_USTN_WORKSETNAME).DGNWS _USTN_WORKSETSDGNWSROOT does not need to be defined for this to work so appears redundant. However it could be used if the DGNWS was required to be in a sub-folder of _USTN_WORKSETSTANDARDS, e.g.: _USTN_WORKSETSDGNWSROOT = $(_USTN_WORKSETSTANDARDS)// _USTN_WORKSETDGNWS = $(_USTN_WORKSETSDGNWSROOT)$(_USTN_WORKSETNAME).DGNWS The complete block I've put in WorkSpaceSettings.cfg is: MY_PROJECT_SERVER = / _USTN_WORKSETROOT = $(MY_PROJECT_SERVER)$(_USTN_WORKSETNAME)/ _USTN_WORKSETSTANDARDSDIRNAME = %lock _USTN_WORKSETSTANDARDSDIRNAME _USTN_WORKSETSTANDARDS = $(_USTN_WORKSETROOT)$(_USTN_WORKSETSTANDARDSDIRNAME)\ %lock _USTN_WORKSETSTANDARDS _USTN_WORKSETDGNWS = $(_USTN_WORKSETSTANDARDS)$(_USTN_WORKSETNAME).DGNWS %lock _USTN_WORKSETDGNWS The variables are locked to ensure that other CFG files do not change them. OpenBuildings Designer for instance, to ensure that the delivered example WorkSets operate as designed, sets _USTN_WORKSETSTANDARDSDIRNAME = Standards. In multiple WorkSpace scenarios where perhaps the root folder for the WorkSets vary, some or all of these could be put in the WorkSpace CFG. The other interesting thing which may help, obvious in hindsight, is OOTB the configuration results in the folder structure: ....\\\ so WorkSets are always contained within a WorkSpace folder. By redirecting _USTN_WORKSETROOT to a path that does not include _USTN_WORKSPACENAME as shown above, the WorkSets can be stored in any required location, while the benefits (if needed) of assigning differing resources by WorkSpace within the configuration are retained, and the grouping of projects in the UI is retained. I'll post some examples over the next month, probably in my blog . Hope this helps.

Where and how is the variable _USTN_WORKSETDGNWS defined?

Top Replies