My company currently has our default FDOT workspace drop down store/use worksets on a shared network location. This is not a good option for working from home because of how slow it is operating over a VPN. We do not use ProjectWise. I would like to create a second Workspace that uses all of the FDOT standards, but stores its Worksets on my C drive.This would allow me to copy full FPID folders onto my desktop or C drive and then paste to the shared network to update files. I have tried several things to accomplish this, but the "HOME" workspace always wants to create worksets in the shared drive location instead of the local drive. I have tried environment variables and a series of config files, but I seem to be missing something. Does anyone have a workflow on how to do this? I managed to accomplish this for SS4, but I'm not having as much luck with ORD.
My current environment variables:
FDOT_ORGANIZATION = C:\FDOTConnect\Organization-Civil\
FDOT_WORKSETS = W:\FDOTConnect\
HOME_WORKSETS = C:\FDOTConnect\Workspaces\ (seems like this variable isn't actually doing anything though)
Where is your _USTN_CUSTOM_CONFIGURATION variable pointing?
I feel your pain on the WorkSets issue. I wish Bentley would have given us the latitude to define more than one location for the _USTN_WORKSETSROOT variable and parse them in order. It's dumb that we have to basically set up a whole separate Workspace (or some other workaround) to switch.
Eddie Giese, PE Senior Roadway Engineer (licensed in FL & PA)
Patel, Greene & Associates, LLC PowerGEOPAK V8i SS10 (08.11.09.918) OpenRoads Designer 2020 R3 (10.9.0.91)ProjectWise Explorer CE 10.0.3.434LumenRT CE Update 14 (220.127.116.11)