Installing Building Applications into a ProjectWise Managed Workspaces (Typical Configuration)In the Building application's integration with ProjectWise, we try to maintain a consistent application behavior, so theuser experience is similar whether inside or outside of a ProjectWise environment. The following building configurationvariables will change the user’s experience regarding DEM processing, DEM workflows and ProjectWise Integration.
The BB_SUPPORT_PW_DCW configuration variable defines the integration of the Drawing Extraction Manager (DEM) with ProjectWise. (Managed or Unmanaged workspaces). This configuration variable can control whether the DEM or ProjectWise's Document Creation Wizard (DCW) is the authority for the file creation process from the Drawing Extraction Manager
BB_SUPPORT_PW_DCW =0 (or undefined) ‐ By default, this variable is undefined. This relegates the creation of extractions file to be the responsibility of the DEM. The DEM contain all the information necessary to create a new file in a ProjectWise repository; file name, file seed, and file output destination.
BB_SUPPORT_PW_DCW =1 ‐ Defers the extraction file creation of the DEM to ProjectWise's Document Creation Wizard (DCW). The DEM will provide the ProjectWise DCW with the default file information from the extraction definition, but changes in the DCW, will be automatically synchronized back to the DEM, possibly making changes in extraction definition name and output destination.
Note: Enabling this option is recommended only if naming standards have been implemented for the ProjectWise environment and are enforced by the ProjectWise's Document Creation Wizard (DCW).
Note: DEM batch processing, will require user attention, for each extraction definition the first time the extraction is processed. This is necessary to process through the DCW options and allows the DCW to create the destination extraction file. Once the extraction file is created, batch processing should be able to complete unattended.
The TFPW_QUIET_EXCHANGE configuration variable defines the behavior of the ProjectWise Integration when exchanging between Models and the extraction files generated from the DEM. This only applies if the Model and the extractions exist in different files; there are no ProjectWise operations in the exchange between internal dgn models.
TFPW_QUIET_EXCHANGE (undefined or =0) ‐ If undefined or set equal to zero (0), then the ProjectWise Check In dialog will be presented to the user each time they initiate an exchange between the model and extraction file or vice versa.
*TFPW_QUIET_EXCHANGE =1 ‐If set equal to one (1), no ProjectWise Check In dialog is presented when exchanging between Triforma Model and extraction Drawing files. The files will remain checked‐out.
*Note: If defined TFPW_QUIET_EXCHANGE=1, It is recommend that the corresponding configuration variable, TFPW_QUIET_EXCHANGE_AUTOCHECKIN also be enabled.
The TFPW_QUIET_EXCHANGE_AUTOCHECKIN configuration variable is only considered if the TFPW_QUIET_EXCHANGE is enabled. The TFPW_QUIET_EXCHANGE_AUTOCHECKIN determines the status of the remaining file(s) during the exchange between the model and extraction file or vice versa.
TFPW_QUIET_EXCHANGE_AUTOCHECKIN =0 (or undefined) ‐ If undefined or set equal to zero (0), then the exchanged files will remain checked‐out. At the completion of the session, a user may have files remaining checked out and will need to use the Local Document Organizer from ProjectWise Explorer to Check In, Update Server Copy or Free the checked out document(s). It is recommend, if this is the preferred workflow that the default ProjectWise User Setting be set to open the Local Document Organizer on logout. (ProjectWise User Settings ‐ User Interface> Show Local Document Organizer on log out)
TFPW_QUIET_EXCHANGE_AUTOCHECKIN =1 ‐If set equal to one (1), the exchanged files will be automatically checked in. If TFPW_QUIET_EXCHANGE =1 is set, it is recommended TFPW_QUIET_EXCHANGE_AUTOCHECKIN to be set. Please consult your ProjectWise implementation team and/or administrators.
TFPW_USE_EXT_ASSOCIATIONS ‐ determines which application is associated with a file/document that was created from the building applications such as a drawing extraction.
TFPW_USE_EXT_ASSOCIATIONS =0 (or undefined) ‐ If undefined or set equal to zero (0), then the application associated to the newly created file will be inherited from the parent file. Therefore, a file extracted from a file associated with Bentley Architecture with also have an application association to Bentley Architecture.
TFPW_USE_EXT_ASSOCIATIONS =1 ‐If set equal to one (1), uses ProjectWise extension associations when creating new files to determine the application assignment. By default, the .dgn file extension is associates to MicroStation. Therefore, if a file extracted from a file associated with Bentley Architecture had an extension of .dgn, it would automatically have an application association of MicroStation based on the .dgn association.
(Applies to Unmanaged Workspaces (Workspace Profiles) Only)The TFPW_REFDATA_USE_PW_DLG configuration variable supports legacy ProjectWise integration. It provides imited ProjectWise integration to certain building features, so these features have access to the ProjectWise repository. Implementation of a ProjectWise Managed Workspace should be considered and is recommended if building datasets are required to be stored within ProjectWise.
TFPW_REFDATA_USE_PW_DLG=0 (or undefined) ‐ If undefined or set equal to zero (0), there is no change to building application behavior.
TFPW_REFDATA_USE_PW_DLG=1 ‐If set equal to one (1), provides ProjectWise integration and access to the ProjectWise repository for the following building features; Column Grid tool , Frame Builder, Structural Section, Compound Cell Manager and Quantify Tool.
Product TechNotes and FAQs
Bentley Technical Support KnowledgeBase
Bentley LEARN Server
Bentley's Technical Support Group requests that you please confine any comments you have on this Wiki entry to this "Comments or Corrections?" section. THANK YOU!