Setup Instructions:
To install this template:
1). Copy Template:
In ProjectWise, create a Bentley root folder location for the Workspaces. For purposes of this document, the location will be pw:Datasource\Documents\Resources\Bentley\
Note: The Resource folder name is not important, however for consistency, it is advised to keep the Bentley name as the root folder for the installation. Any folder under the Bentley cannot be changed without affecting the configuration paths. Once this is created,
copy the template to this location. Where a Dev/Test/Prod process* is used, repeat these steps for additional locations.
2). Create CSB called "Bentley Common Predefined 2.0" with the following syntax, which points to the Common_Predefined.cfg file provided in the template. (see relative location highlighted above).
_DYNAMIC_DATASOURCE_BENTLEYROOT = pw:\\mydatasource\Documents\Resources\Bentley\
%include $(_DYNAMIC_DATASOURCE_BENTLEYROOT)Common_Predefined.cfg
Note: when creating the _DYNAMIC_DATASOURCE_BENTLEYROOT variable, use ADD>ProjectWise Folder and browse to the Bentley folder under Resources (or other location as determined by installation). The %include entry should utilize the "String" option. Repeat steps as needed if Dev/Test/Prod process is used.
3). For V8 workspace: create a named root folder for each workspace to be incorporated. This roughly can represent the _USTN_WORKSPACEROOT folder and can be assigned as such.
4). Assign Workspace Names
Edit Common_Predefined_PWSetup.cfg to set default workspace names:
_DYNAMIC_V8WORKSPACENAME : Workspace
_DYNAMIC_CEWORKSPACENAME : Example
5) Copy the _PWSetup folder and files. Working example V8 and CONNECT Edition workspaces are provided. The _PWSetup folder and files can be copied to the respective workspace root folders. Additional example can be found in the "Documentation" folder. Both simple and advanced examples are provided
6) Edit the WorksSpacePWSetup_Predefined*.cfg file to define Framework variables as needed. For V8 workspace this will typically involve assigning location for the Projects Root, Project Root, Project Name, and cfg file at a minimum. For CONNECT this will typically involve assigning location for the WorkSets Root, Workset Root, WorkSet Name, and cfg file at a minimum. The .dgnws file may also need to be set. More often than not, addition syntax will be needed to set additional values required by the workspace. As noted in the previous step, example configuration syntax for various scenarios is provided in the template's documentation section.
7). Add Ignore workspace reload variable syntax
8). Create WorkArea (from a template if available) and Assign CSB. Rename workset cfg/project pcf file in needed. Delete .dgnws if it exists. The .dgnws should be created from the template pointed to by the workspace configuration.
* The Dev/Test/Prod process refers to a standard development process where there is an area for initial development, final testing, and the actual production area. The development area may contain various temporary development files. However, the test area should be a replica of what will be in production.