[ORD/CONNECT] Workset template?

OK, so the issue is with one specific client, but I'm still running into other issues.

The rest of the templates that DO appear to give me CFGs from the proper template aren't creating directories. Now, I don't actually need those directories there but...

As much as I don't want to edit the client configs more than necessary, I did have to add a block to account for they way we store our data. That gets edited after workset creation to the proper project directory, and it includes "placeholders" for files that are about to exist.

#============================================================================
# Template for a new WorkSet
#============================================================================

PROJECT_YEAR = 2022
PROJECT_NUMBER = WS_Test
PROJECT_DIRECTORY = $(SHR_PROJECTSDIR)$(PROJECT_YEAR)/$(PROJECT_NUMBER)/
_USTN_WORKSETROOT = $(PROJECT_DIRECTORY)CADD/Design/
PROJECT_CADD = $(_USTN_WORKSETROOT)

MS_DEF = $(PROJECT_CADD)Base/
MS_DEF > $(PROJECT_CADD)Sheet Sets/
MS_RFDIR = $(PROJECT_CADD)Base/
MS_RFDIR > $(PROJECT_CADD)Sheet Sets/

%if defined (CIVIL_WORKSET_TEMPLATE_LIBRARY_NAME) && exists ($(PROJECT_CADD)ORD/$(CIVIL_WORKSET_TEMPLATE_LIBRARY_NAME))
  CIVIL_ROADWAY_TEMPLATE_LIBRARY        = $(PROJECT_CADD)ORD/$(CIVIL_WORKSET_TEMPLATE_LIBRARY_NAME)
%endif
#----------------------------------------------------------------------------

%if defined (CIVIL_WORKSET_DESIGNSEED) && exists ($(PROJECT_CADD)ORD/$(CIVIL_WORKSET_DESIGNSEED))
  MS_DESIGNSEED                         = $(PROJECT_CADD)ORD/$(CIVIL_WORKSET_DESIGNSEED)
%endif

My thought was that, if the workset creation makes a copy of the workset template directory, that copy could be moved into the project to the proper location, renamed "ORD" and be ready for design with the proper files.

I found it.

#====================================================================================
#set up workset variables
_USTN_WORKSETDGNWSTEMPLATE = $(_USTN_WORKSETSROOT)TDOT_RDWY_TEMPLATE.dgnws
_USTN_TEMPLATEWORKSETNAME = TDOT_RDWY_TEMPLATE
_USTN_WORKSETTEMPLATE 		= $(USTN_WORKSETSROOT)$(USTN_TEMPLATEWORKSETNAME)
#====================================================================================

Workset templates were provided, but not defined. Once I found these variables, I was able to get "proper" worksets.

So far, we don't have to actually deliver full design packages. I know it's coming (from somewhere) but at this point it's not a requirement. I suppose I can set up my own workspaces/worksets to get the work done until that does show up.

All but one of my DOTs has all of their files in Organization-Civil, so eliminating the client workspaces will probably not actually affect anything...So to create "Yearly" workspaces that can point to a Worksets directory in each project year directory. Then access to every client's workset templates so that each project can %include the correct client standards files.

Since I can't just copy and rename worksets (DGNWS), I imagine I still need to go through the actual "Create Workset" dialog. I can see a VBA that could copy (create) and edit the workset CFG file based on a few user values, and the project directories will already exist, but I don't see any way around the official process for the DGNWS.

It would be really nice if you could Browse...for a workset template.

MaryB said:

Since I can't just copy and rename worksets (DGNWS), I imagine I still need to go through the actual "Create Workset" dialog.

No, if the dgnws doesn't exist the first person to open the workset will create it by copying the defined dgnws template file. You can define a template for JUST the dgnws using _USTN_WORKSETDGNWSTEMPLATE. That variable can point to any file at any path. It will be copied to either the default location or what _USTN_WORKSETDGNWS points at.

Person that creates the file has to have read/write on the destination, but that's always me currently so hasn't been an issue.

Kevin van Haaren said:

Person that creates the file has to have read/write on the destination, but that's always me currently so hasn't been an issue.

Every user will need read/write access to the dgnws file if you want them to be able to edit the WorkSet Properties, and add sheets to the Sheet Index. That's the main reason we remap the location of _USTN_WORKSETSROOT so that everything under _USTN_CUSTOM_CONFIGURATION can be read only except for the admins.

That sounds as if I don't need to create a DGNWS to create a workset?
Would I be able to set _USTNWORKSETDGNWSTEMPLATE in the workset CFG? That would certainly simplify one thing...And it suggests that I could bypass the "Create Workset" dialog entirely, as long as I could generate the workset CFG any other way.

Also...Is there a way to isolate the workset templates from the regular worksets? If I do need to use the standard "Create Workset" dialog, I would like it to just show my templates for the workspace, not all of the worksets for the workspace.

_USTN_WORKSETTEMPLATE is for a single file. If I need to use the standard dialog, I need them to be able to select from a list of client templates for the workset, but I wouldn't want to bog that list down with all the rest of the workspace worksets.

Of course, if I all I really need to do is create the CFG file, that is fortunately moot.

I'm not sure if you can set _USTN_WORKSETDGNWSTEMPLATE in the workset.cfg, I want to say it has to be at the workspace or lower but it's been a long time since i tried and I don't remember the results. Mine is set at effectively the organization level.

I'm not sure if you can set _USTN_WORKSETDGNWSTEMPLATE in the workset.cfg, I want to say it has to be at the workspace or lower but it's been a long time since i tried and I don't remember the results. Mine is set at effectively the organization level.

Oh, I just remembered when ORD (or other product) is opened it doesn't just create a DGNWS for the current workset, it actually creates one for every .cfg in _ustn_worksetsroot that doesn't already have one, even if you don't open that particular workset. So if you take a template file, rename it to a .cfg file and start editing it, if somebody else opens any other workset in that folder it creates the dgnws for your cfg from whatever it's template is.

I think we filed this as a bug but I can't remember if Bentley agreed. Currently we say to keep the .template part until you're actually done editing it.