[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.

I thought that was it, but that actually seems to have removed the template from the list. And now it's not selectable in the Create Workset dialog as a template either. I'm so confused...

I think you only may be missing the underscore in front of USTN for both on Line 5

We have a winner! I've been looking at this for way too long...

I spoke too soon. it was the end of the day, and I was too eager to be done.

I have corrected the code:

_USTN_TEMPLATEWORKSETNAME = TDOT_RDWY_TEMPLATE
_USTN_WORKSETDGNWSTEMPLATE = $(_USTN_WORKSETSROOT)$(_USTN_TEMPLATEWORKSETNAME).dgnws
_USTN_WORKSETTEMPLATE 		= $(_USTN_WORKSETSROOT)$(_USTN_TEMPLATEWORKSETNAME)

And I can see my template when I try to create a new workset. However, only the CFG gets copied to the new workset name - the DGNWS and the Template folder do not get reproduced. Without a DGNWS there is no workset available to select.

The template named has a CFG, a DGNWS, and a folder:

So I'm not missing anything?

Just a guess... did you rename your workset template? I would clone the original provided template each name change, just in case...

Just a guess... did you rename your workset template? I would clone the original provided template each name change, just in case...

Yes...I did...
OK, I'll see about getting "clean" versions created from the original provided worksets.
This is a real pain if you can't even rename files.

Am I allowed to MOVE workset files?

MaryB said:

Am I allowed to MOVE workset files?

Yes.

We configure a separate WorkSets folder where the standard project folders are. That way IT doesn't have to go through any gymnastics to give all users write access to the dgnws file while restricting the rest of the files.

Set the _USTN_WORKSETSROOT folder to the Project\WorkSets folder. Your WorkSet.cfg and dgnws files will automatically be created and referenced from there. 

Something like this....

That Projects folder can be anywhere you like outside of the ORD Configuration tree.

FYI - If you want to rename a WorkSet, create your new WorkSet using the old WorkSet as a template.

Unfortunately, I don't have permissions to create a directory in our Project Files root directory...and everything under that is divided by year.

The client-based WorkSets directory underneath the client-based WorkSpaces comes automatically with the client resources, so in theory a lot of things work without the need to redirect it all. We don't have things locked down as much on the standards drive (I know, I know...but right now it works in my favor). The other option I keep playing with is year-based workspaces, with the workset CFG %including the client workspace resources, but I don't know how to get around client based workset templates. As in, an IN workset template (as delivered) is set up differently than a TN workset template. Or I don't know how to store my workset templates in a different location than the actual worksets.

To keep your sanity, sometimes you have to ditch the client based WorkSet template folder structure and use your own when you have conflicting folder setups. In cases where you have to package up the entire project folder for delivery to the client using their standard folder setup, then you're kind of stuck using theirs.

From what you have been describing, I think a custom WorkSet creation tool makes sense.