[ORD/CONNECT] Workset template?

The workspace/workset rabbit hole has no end.

I'm starting with one client. Trying not to edit those client configs. This client comes with a workset template - folder, CFG & DGNWS.
I wanted to see if that template is actually what is used to create new worksets under that client.

Apparently, it's not.

I was able to create a new workset. I selected "Create Workset", gave it a name and selected the template I would like to use. It created a folder, CFG & DGNWS in the proper location. But the folder doesn't include the files from the template folder and the CFG is not the same as the template CFG (far more generic, not even close). It would appear that the template being used is not the template I selected? Or is the CFG file unrelated to the template workset?

I am getting lost in the CFG variables, so I'm sure I have something crossed up. Can anyone make a suggestion to straighten me out?
Thank you.

Parents
  • 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.

    MaryB

    Power GeoPak 08.11.09.918
    Power InRoads 08.11.09.918
    OpenRoads Designer 2021 R2

        

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

    MaryB

    Power GeoPak 08.11.09.918
    Power InRoads 08.11.09.918
    OpenRoads Designer 2021 R2

        

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

    MaryB

    Power GeoPak 08.11.09.918
    Power InRoads 08.11.09.918
    OpenRoads Designer 2021 R2

        

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

     

  • But if you change worksets root, doesn't that make the workset.cfg editable by everybody too? We want the cfg locked down but the dgnws in a writable location.

     

  • But if you change worksets root, doesn't that make the workset.cfg editable by everybody too?

    Yes it does. The problem is that the dgnws does not function properly if it's not in the _USTN_WORKSETSROOT folder. That's been a long standing problem with the CONNECT Edition. 

    You have to pick your poison.

    Rod Wing
    Senior Systems Analyst

Reply Children