[CONNECT] Workspace without WorkSets

Hi, I'm new to CE and try to migrate our V8i workspaces to CE. It's clear that old site level now is organization. And from my point of view our old project level now should be "Workspace" level, because it contains client resources. It seems that Bentley agrees here.

The issue for me is: We have many small jobs (resp. sets of DGN) for each client (resp. Workspace). Each job needs the same client resources and nothing extra. Though the Workspace/client resources are needed to edit or view the DGN files, none of these DGN files belongs to the Workspace. The design files are stored anywhere on the file system, but never inside microstation's WorkSpace. And that's why the WorkSets seem to be useless in our work flow. Unfortunatly I can't see a way to open a design file with specified Workspace but without a WorkSet. When I use a configured dummy WorkSet, it often stands in the way: The opened files are marked with WorkSet name, causing confirmations about WorkSet mismatch...

Hope, someone could tell me, how to get rid of WorkSets or at least the nasty side effects (I cant imagine that our work flow is that uniqe).

Thanks, Robert.

Parents
  • While I was in private industry, we used PCF (Project) to assign client settings. in Each PCF, was a %include statement to include a CFG file that assigned the client standards and the PCF file assigned any project specific things - which was often default folders but could allow project specific files if that was needed. So all our PCF filenames had to specify a project and that alone made sure the correct client standards were used.

    In ORD, the Workspace will load an organization-civil set of standards, so it can be a client and when a workspace is selected, it can show worksets (projects) for that client. And any of these can load organization wide (site) files if so configured. There are a lot of "hooks" in the cfg files where you can define where each type of file is stored and what names they are.

    In certain cases - Workspace and Workset, there must be matched cfg file names to folder names.

    When Bentley helped us migrate our Ss2/4 workspace to ORD, they made all of the CFG files and folders the same name MDSHA. We found this confusing as we wanted to know by name, what CFG or folder was Organization-Civil, Workspace or Workset, so we renamed each to make them unique, even if they were still similar. 


    Charles (Chuck) Rheault
    CADD Manager

    MDOT State Highway Administration
    Maryland DOT - State Highway Administration User Communities Page

    • MicroStation user since IGDS, InRoads user since TDP.
    • AutoCAD, Land Desktop and Civil 3D, off and on since 1996
Reply
  • While I was in private industry, we used PCF (Project) to assign client settings. in Each PCF, was a %include statement to include a CFG file that assigned the client standards and the PCF file assigned any project specific things - which was often default folders but could allow project specific files if that was needed. So all our PCF filenames had to specify a project and that alone made sure the correct client standards were used.

    In ORD, the Workspace will load an organization-civil set of standards, so it can be a client and when a workspace is selected, it can show worksets (projects) for that client. And any of these can load organization wide (site) files if so configured. There are a lot of "hooks" in the cfg files where you can define where each type of file is stored and what names they are.

    In certain cases - Workspace and Workset, there must be matched cfg file names to folder names.

    When Bentley helped us migrate our Ss2/4 workspace to ORD, they made all of the CFG files and folders the same name MDSHA. We found this confusing as we wanted to know by name, what CFG or folder was Organization-Civil, Workspace or Workset, so we renamed each to make them unique, even if they were still similar. 


    Charles (Chuck) Rheault
    CADD Manager

    MDOT State Highway Administration
    Maryland DOT - State Highway Administration User Communities Page

    • MicroStation user since IGDS, InRoads user since TDP.
    • AutoCAD, Land Desktop and Civil 3D, off and on since 1996
Children
No Data