[ORD/CONNECT] Workset template?

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.

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.

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.

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.

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.