CONNECT Edition - Custom Configuration - Part 1 : Initial Creation Steps

This article is based in the MicroStation CONNECT Edition installation process. The process for other applications is similar but will generally have some additional steps to cover application specific requirements, AECOsim Building Designer (ABD) datasets for instance. The additional steps for ABD are linked from CONNECT Edition - Configuration : Customization Guides.

The initial setup of WorkSets requires some manual intervention.

Once the first WorkSet is created, then modified with any required content and configuration, it can become a template for subsequent WorkSets. Obviously multiple template WorkSets can be created where required.

  1. Create the folder on your network where the Custom Configuration will be located. This can use a mapped drive or a UNC path. e.g.:
    O:\CONFIGURATIONS\MCE
    or
    \\hal\CONFIGURATIONS\MCE
    the UNC path will be used in this example.
  2. During installation of MicroStation CONNECT Edition specify this location in the Configuration dialog

    The folder does not need to contain anything for installation to succeed. The installer does not create any files or folders in the Custom Configuration location.
    What it does do is set the value of the variable _USTN_CUSTOM_CONFIGURATION listed in "C:\ProgramData\Bentley\MicroStation CONNECT Edition\Configuration\ConfigurationSetup.cfg" to the chosen Network Configuration path; \\hal\CONFIGURATIONS\MCE in this example.
    Note: The defect in MicroStation CONNECT Edition Updated 5 and 6 that resulted in this value not being written has been fixed in Update 7.
  3. Copy C:\ProgramData\Bentley\MicroStation CONNECT Edition\Configuration\Organization and its contents to the Custom Configuration location. These folders are empty but will contain DGNLIBs and other resources that are shared by the whole organization.
    This folder should be Read-Only to everyone other than the people responsible for maintaining the Organisation standards.
  4. Edit, either at this stage or later on, the standards.cfg file, e.g.: \\hal\CONFIGURATIONS\MCE\Organization\Standards.cfg adding the variables that are appropriate for your organization.  This file is discussed in Part 4.
  5. Create a new folder, WorkSpaces, e.g.: \\hal\CONFIGURATIONS\MCE\WorkSpaces
  6. Decide whether one WorkSpace or multiple WorkSpaces are needed for your organization. Typical scenarios include grouping project work by: professional discipline; project start year; project client organization; etc. Name your WorkSpace(s) appropriately. For this document the examples will be WorkSpace_01, 02, etc.
  7. Decide on the naming syntax for WorkSets. For this document the examples will be WorkSet_01, 02, etc.

At this stage starting MicroStation CONNECT Edition will show only the delivered example project, the Custom Configuration will not be displayed in the UI.

To enable the Custom Configuration and its contents to become visible each WorkSpace must have a Configuration File named <WorkSpaceName>.cfg that must be located in the same folder as the WorkSpace folder, e.g.: \\hal\CONFIGURATIONS\MCE\WorkSpace_01.cfg.

To create this follow the next sequence of steps.

  1. Open MicroStation, click the arrow at the right of the Welcome Screen to 'Start a work session.
    BEFORE opening the Example WorkSpace/WorkSet and any files:
    From the WorkSpace menu pick Create WorkSpace:
  2. In the Create WorkSpace dialog note that the Folder locations shown are in the Custom Configuration.
    Enter the new WorkSpace name and description, note that the folder locations update to show the new WorkSpace name.
    Click OK:

    Note in this step that the list of Standards Subfolders, this list is populated by the variable _USTN_WORKSPACESTANDARDSUBDIRS, the list can be modified to add any custom folders that are needed.
    While folders can also be added to the list in this dialog, adding them to the variable's value list will ensure consistent folders in every WorkSpace.
    Now the Backstage WorkSpace list will contain WorkSpace_01 and prompt to create a WorkSet:
  3. Before going on to do that lets take a look at what has been created. In \\hal\CONFIGURATIONS\MCE\WorkSpaces there is now both a WorkSpace_01 folder and its accompanying WorkSpace_01.cfg.

    Inside the WorkSpace_01 folder are the Standards and WorkSet folders:

    The Standards Folder contains the Subfolders defined by _USTN_WORKSPACESTANDARDSUBDIRS:
  4. Now click the Create a WorkSet button, note in the Template field the only option is None and that the Folder Locations are set to \\hal\CONFIGURATIONS\MCE\WorkSpaces\WorkSpace_01\WorkSets:

    Enter the name of the new WorkSet, note that this is added as the new WorkSet folder name in the Folder paths, there is no need to browse. Standards Subfolders will be created as specified by variable _USTN_WORKSETSTANDARDSUBDIRS:

    Now in the WorkSets folder WorkSet_01 has been created along with the accompanying WorkSet_01.cfg and WorkSet_01.dgnws files

    WorkSet_01 contains the specified Subfolders:
  5. Now the basic structure of the first WorkSet and the supporting Custom Configuration is in place, it is possible to create a new file:

BUT….

There is still work to do. This process has created the functional structure of the Organization with the first WorkSpace and WorkSet with the essential configuration files needed for it to operate. Is has not created any of the resources that contain the Organization, WorkSpace or WorkSet standards.

Organization Resources

See Part 2 for more on resources and how to organize them.