How do I change configuration to select a project specific border file, rather than a default workspace border while cutting sheets in ORD??

Thank you for all the responses everyone. 

Eddie, how ya been man?? Long time no speak. Just got reunited with one of our old RETTEW cohorts. Shaun Bentz was just hired in our Mburg office, working hybrid schedule between home and office. Been cool catching up with him. 

Looking at the sheet borders and sheet seeds that PennDOT provides is a little confusing. They include Sheet Seed DGNLIBs, another set of sheet seeds grouped with the design model sheet seeds and another folder with just blank Sheet Border dgns. 

When I run the named boundary tool to cut and create the sheet models, it seems that the border is automatically referenced in from the Sheet Borders folder, not the DGNLIBs. So, would your possible solutions still work?? Kinda seems like I need to revise the variable that sets where the border is referenced from, right?? Maybe I am not thinking about this correct, but the 2 different sheet seed folders and 1 sheet border folder could have me a bit confused. Thanks again for you help.

Brett

Hello again, I can only speak from my experience, but if things are already being pulled from a workspace/workset you may not need to get into the configuration. Personally, I rely on workset files to preserve the configuration of my DOT's workspace and when on ProjectWise.

The sheet seeds that control the settings for creating a drawing/sheet model are in the workspace's Dgnlib/Sheet Seeds folder, not the main Seed folder. I'm guessing that the current blank border dgn may just already be attached directly to those.

I would try copying the desired sheet seed dgnlib (my DOT provides options at different scales) to the same location or to your workset standards location, opening it and replacing the border reference with your edited copy. Rename the models/view/boundary to show that it's for your project. Then when you create a named boundary/sheet, select that new drawing seed, the sheet created will have your project border already referenced in.

Let me know if this make sense!

I agree, but this requires the definition of the config variables I noted above within the WorkSet's .cfg files as well, right? 

It sounds like a matter of personal/company preference and there are options here. I just personally have warmed up to the idea of letting the DGNWS control. 

Neither option is perfect and each has its drawbacks. Either way, I'd say pick whichever you like best and develop a workflow internally that your users can follow easily as they will often default to path of least resistance :)

I'll also add to this great information Eddie, I found out recently you can open a DGNWS file as any dgn or dgnlib file and edit properties which could make initial setup easy (curious if doing this causes any issues??).  Another note on the dgnlib method is that the more dgnlibs the workspace loads the slower things take to process as mentioned on a recent webcast by Chuck Lawson.  Here's that link to register/view for those here... https://event.on24.com/wcc/r/3699890/D3F080986E63FA49DB5B5F9A45033F36?mode=login 

I'll also add to this great information Eddie, I found out recently you can open a DGNWS file as any dgn or dgnlib file and edit properties which could make initial setup easy (curious if doing this causes any issues??).  Another note on the dgnlib method is that the more dgnlibs the workspace loads the slower things take to process as mentioned on a recent webcast by Chuck Lawson.  Here's that link to register/view for those here... https://event.on24.com/wcc/r/3699890/D3F080986E63FA49DB5B5F9A45033F36?mode=login