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.
Am I allowed to MOVE workset files?
MaryB
Power GeoPak 08.11.09.918Power InRoads 08.11.09.918OpenRoads Designer 2021 R2
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.
Rod WingSenior Systems Analyst
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.
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.