ProjectWise V8i Administrator Client

(SELECTseries 2)

Bentley Institute Course Guide

TRN013280-1/0003

Trademarks
AccuDraw, Bentley, the “B” Bentley logo, MDL, MicroStation and SmartLine are registered trademarks; PopSet and Raster Manager are trademarks; Bentley SELECT is a service mark of Bentley Systems, Incorporated or Bentley Software, Inc. AutoCAD is a registered trademark of Autodesk, Inc. All other brands and product names are the trademarks of their respective owners.

Patents
United States Patent Nos. 5,8.15,415 and 5,784,068 and 6,199,125.

Copyrights
©2000-2010 Bentley Systems, Incorporated. MicroStation ©1998 Bentley Systems, Incorporated. All rights reserved.

ProjectWise V8i Administrator Client

Copyright © 2010 Bentley Systems, Incorporated

ii

Jun-10

Instructor Set-Up
The course needs the following items as part of the datasource. The datasource should be created using the template so it has all the delivered USTN example files. Those files are used in this course. Create a storage area: • Exton

General: • • • Make sure that the students can get to the class data set folder. They will be adding these folders and files to the datasource. MicroStation/J is used in the integrated applications module. In the spatial module, students set the datasource up so spatial features can be used. If the instructor desires, and has their own datasource set up so spatial features can be used, they can demonstrate that: Sub-folders, which may be project folders, are displayed on the background map in their true geographic location Double clicking on a sub-folder opens it. A background map displays a smaller area representing its true geographic area of interest, such as the area represented by a project All the documents in the folder are displayed on a folder’s background map Double clicking on a document opens it, just like using the list tab. You can explain the symbology that is assigned by default, the symbology legend, and the View > Geospatial options. Execute a search using spatial search criteria •
Important: Environments are imported during this course (pwclass.aam and Standard.aam). They must be imported into a database instance to which they have not been imported previously. If not, errors will occur and they will not

Jun-10

iii
Copyright © 2010 Bentley Systems, Incorporated

Instructor Set-Up

import properly. Also, use the version of the environments in the current data set.

Instructor Set-Up

Copyright © 2010 Bentley Systems, Incorporated

iv

Jun-10

Table of Contents
Instructor Set-Up ____________________________________ iii Course Overview ____________________________________ 1
Course Description ____________________________________1 Target Audience_______________________________________1 Prerequisites _________________________________________1 Course Objectives _____________________________________1

Document Architecture ______________________________ 3
Module Overview _____________________________________3 Module Prerequisites __________________________________3 Module Objectives_____________________________________3 Introductory Knowledge ________________________________4 Questions ________________________________________4 Answers __________________________________________4 Document Information _________________________________4 Creating Documents ___________________________________5 Converting abstract documents _______________________5 Document ID’s_____________________________________6 Document preview _________________________________8 Extended Document Properties __________________________8 Security tab _______________________________________9 Attributes and More Attributes tabs ___________________9 File Properties tab __________________________________10 Workspace tab ____________________________________12 Components tab ___________________________________13 Departments _________________________________________13 Creating Departments_______________________________14 Module Review _______________________________________14 Questions ________________________________________14

ProjectWise Explorer Best Practices ____________________ 17
Module Overview _____________________________________17 Module Prerequisites __________________________________17 Module Objectives_____________________________________17

Jun-10

Copyright © 2010 Bentley Systems, Incorporated

v

Table of Contents

Table of Contents

Introductory Knowledge ________________________________18 Questions ________________________________________18 Answers __________________________________________18 ProjectWise Explorer Networking _________________________19 Datasource display names ___________________________19 Navigating multiple sub-nets _________________________20 ProjectWise network configuration ____________________20 ProjectWise network registry entries ___________________23 Basic File Operations ___________________________________24 Document Check Out and check in_____________________24 The working directory _______________________________25 Delta file transfer __________________________________28 ProjectWise Applications________________________________31 Defining applications________________________________32 Working with existing applications_____________________36 Applications and file extensions _______________________37 User overrides for application actions __________________37 Module Review _______________________________________39 Questions ________________________________________39

Managing User Accounts _____________________________ 41
Module Overview _____________________________________41 Module Prerequisites __________________________________41 Module Objectives_____________________________________41 Introductory Knowledge ________________________________42 Questions ________________________________________42 Answers __________________________________________42 User Accounts ________________________________________42 Account Types ________________________________________43 Authentication ____________________________________44 Authentication for Logical accounts ____________________44 Authentication for Windows accounts __________________44 Using ProjectWise User Synchronization Service __________45 Single Sign On _____________________________________47 User IDs __________________________________________48 User Properties Settings ________________________________49 Default user properties ______________________________50 Settings categories _________________________________50 Working directory category __________________________51 General category___________________________________53 User Interface category______________________________55 Administrative category _____________________________59 Document category_________________________________61 Document List category _____________________________65 Folder category ____________________________________67 Message Folders category ___________________________68

Jun-10

Copyright © 2010 Bentley Systems, Incorporated

vi

Table of Contents

Table of Contents

Custom Folders category ____________________________70 Global user lists category ____________________________72 Document Creation Conflicts category__________________73 Audit Trail category_________________________________78 Managed Workspace Profiles category _________________80 Project permissions category _________________________81 Establishing the Default user _________________________81 Modifying user properties ___________________________82 Modifying properties for multiple users_________________83 Secondary Administrative Accounts _______________________83 Deleting Users ________________________________________84 Group and List Membership _____________________________87 User groups _______________________________________87 User Lists _________________________________________90 Selecting users by group or list ________________________91 The Database User Account _____________________________91 Module Review _______________________________________92 Questions ________________________________________92

Environments ______________________________________ 93
Module Overview _____________________________________93 Module Prerequisites __________________________________93 Module Objectives_____________________________________93 Introductory Knowledge ________________________________94 Questions ________________________________________94 Answers __________________________________________94 Environment Overview _________________________________94 Defining Environments _________________________________95 Using existing database tables ________________________96 Using new database tables ___________________________97 Creating environments by importing script files __________99 Interfaces ____________________________________________99 Creating an Interface _______________________________99 Labels and prompts_________________________________102 Fixed pick-lists _____________________________________103 Using format strings ________________________________105 Providing default values _____________________________105 Dynamic pick-lists __________________________________106 Triggered updates for environment attributes ___________107 Required fields ____________________________________108 Modifying Property Column Properties ____________________111 Deleting Environments _________________________________112 Attribute Sheets_______________________________________112 Adding and removing attribute sheets __________________113 Defining Document Codes_______________________________113 Setting up document code restrictions _________________116

Jun-10

Copyright © 2010 Bentley Systems, Incorporated

vii

Table of Contents

Table of Contents

Allow and forbid restrictions__________________________116 Reserved restrictions________________________________117 Searching for Documents by Environment Attributes _________118 Attributes Properties Dialog _____________________________120 General tab _______________________________________120 Value tab _________________________________________121 Editing tab ________________________________________125 Extra Values tab____________________________________125 Environment and Attribute User Properties Settings __________125 User Interface-> Attribute Form _______________________126 User Interface-> Search Form _________________________126 Module Review _______________________________________127 Questions_________________________________________127

Importing Legacy Documents __________________________ 129
Module Overview______________________________________129 Module Prerequisites___________________________________129 Module Objectives _____________________________________129 Introductory Knowledge ________________________________130 Questions_________________________________________130 Answers __________________________________________130 Non-interactive Import _________________________________130 The BulkLoad tool __________________________________130 The Bulkload dialog _________________________________131 Process Bulkload File options _________________________132 Interactive Import _____________________________________134 The Wizard Manager ________________________________134 Advanced Document Creation Wizard __________________135 Importing without a wizard___________________________139 Completing the Process _________________________________140 Using the Scan References and Link Sets wizard __________140 Working with link sets _______________________________147 Module Review _______________________________________150 Questions_________________________________________150

Document Indexing __________________________________ 151
Module Overview______________________________________151 Module Prerequisites___________________________________151 Module Objectives _____________________________________151 Introductory Knowledge ________________________________152 Questions_________________________________________152 Answers __________________________________________152 Extraction Process Overview _____________________________152 Supported file types ________________________________153 How it works ______________________________________153 ProjectWise Orchestration Framework Service ___________155

Table of Contents

Copyright © 2010 Bentley Systems, Incorporated

viii

Jun-10

Server requirements ________________________________155 Configuration______________________________________156 Thumbnail Extraction___________________________________157 Automatic extractions _______________________________159 Manual extractions _________________________________160 Full Text Extractions____________________________________161 Indexing Service architecture _________________________162 Process stages _____________________________________163 Choosing a folder for the Microsoft Catalog______________163 Enabling full text indexing ____________________________168 Querying the Microsoft Catalog _______________________169 Full text searches from ProjectWise Explorer_____________170 Processing Non-standard File Types _______________________171 Processing AutoCAD Documents __________________________173 File Property Extraction _________________________________174 Monitoring Extraction Processes__________________________178 File Extraction User Properties Settings ____________________179 User Interface category______________________________179 Module Review _______________________________________180 Questions_________________________________________180 Audit Trail _________________________________________ 181 Module Overview______________________________________181 Module Prerequisites___________________________________181 Module Objectives _____________________________________181 Introductory Knowledge ________________________________182 Questions_________________________________________182 Answers __________________________________________182 Enabling Audit Trail for a Datasource ______________________182 Datasource settings_________________________________182 Routinely logged events _____________________________184 Freeing documents and Audit Trail _____________________185 Audit Trail review __________________________________186 Deleted documents _________________________________186 Additional datasource settings ________________________187 Audit Trail Maintenance ________________________________188 Truncating the Audit Trail ____________________________188 Datasource statistics ___________________________________191 Audit Trail User Properties Settings________________________192 Module Review _______________________________________194 Questions_________________________________________194 Access Control ______________________________________ 195 Module Overview______________________________________195 Module Prerequisites___________________________________195 Module Objectives _____________________________________195 Jun-10 Copyright © 2010 Bentley Systems. Incorporated ix Table of Contents .

Incorporated x Jun-10 .Table of Contents Introductory Knowledge ________________________________195 Questions_________________________________________196 Answers __________________________________________196 Access Control Overview ________________________________196 Security Permissions ___________________________________197 The Object Security Hierarchy ____________________________198 Folder security _____________________________________198 Assigning security to a folder _________________________199 Folder permissions _________________________________201 Document security _________________________________202 Document permissions ______________________________202 Organizing object security____________________________203 Inherited folder security _____________________________205 Security and Document Processors ____________________205 Establishing default security __________________________206 Document level security _____________________________208 Workflow Security _____________________________________210 Implementation____________________________________211 Working with Workflow-Based Security ____________________213 Real _____________________________________________213 Workflow _________________________________________213 Folder____________________________________________214 Security Datasource and User Properties Settings ____________214 User properties setting ______________________________214 Datasource properties setting_________________________215 Module Review _______________________________________215 Questions_________________________________________215 ProjectWise Workflows ______________________________ 217 Module Overview______________________________________217 Module Prerequisites___________________________________217 Module Objectives _____________________________________217 Introductory Knowledge ________________________________218 Questions_________________________________________218 Answers __________________________________________218 Workflow Overview ____________________________________218 Creating and Modifying States ___________________________219 Creating states_____________________________________219 Modifying a state___________________________________220 Creating and Modifying Workflows________________________220 Messaging Services ____________________________________222 Creating a message agent ____________________________222 Non-workflow related events _________________________223 Workflow related events_____________________________223 Workflows in ProjectWise Explorer ________________________225 Assigning a workflow to a folder_______________________225 Table of Contents Copyright © 2010 Bentley Systems.

Incorporated xi Table of Contents .Identifying folder/document workflow and state _________228 Changing states ____________________________________229 Workflow related messages __________________________230 Working with Workflow-Based Security ____________________231 Real _____________________________________________231 Workflow _________________________________________231 Folder____________________________________________232 Workflow Datasource and User Properties Settings___________234 User properties settings _____________________________234 Datasource settings_________________________________234 Module Review _______________________________________235 Questions_________________________________________235 Integrated Applications ______________________________ 237 Module Overview______________________________________237 Module Prerequisites___________________________________237 Module Objectives _____________________________________237 Introductory Knowledge ________________________________238 Questions_________________________________________238 Answers __________________________________________238 Multiple MicroStation Versions ___________________________238 MicroStation Reference Management _____________________241 Creating sets ______________________________________242 Reference location _________________________________244 References without file extensions_____________________245 Dynamic View support ______________________________245 In place reference activation__________________________246 Reference user properties settings _____________________247 Versioning to Manage the Design Process __________________249 Versioning datasource and user properties settings _______250 Datasource settings_________________________________250 User properties settings _____________________________251 Configuring MicroStation Workspaces _____________________252 Unmanaged Workspaces_____________________________253 Workspace profiles and web parts _____________________256 Managed Workspaces _______________________________257 Creating individual configuration settings blocks __________261 Dynamic project configuration ________________________263 Variables to Exclude From Copy Out____________________265 Applying CSBs in ProjectWise Administrator _____________265 Applying CSBs in ProjectWise Explorer __________________265 Configuring a User’s Personal Workspace _______________266 AutoCAD Workspace Profiles_____________________________267 MicroStation Title Blocks ________________________________267 Creating MicroStation attribute exchange rules___________268 Placeholder tags ___________________________________270 Jun-10 Copyright © 2010 Bentley Systems.

Incorporated xii Jun-10 .Table of Contents Attribute exchange rules_____________________________271 Establish update conditions __________________________272 AutoCAD Title Blocks ___________________________________273 MicroStation Link Sets __________________________________274 Selecting the correct link set source ____________________276 AutoCAD Sheet Set Manager Integration ___________________276 AutoCAD Session File Manager ___________________________277 Other AutoCAD Integration Features ______________________277 Integrated ProjectWise Navigator _________________________278 Configuration______________________________________278 Marking up documents with ProjectWise Navigator _______279 Related document markups __________________________279 i-model Composer Integration ___________________________280 Configuration______________________________________280 Microsoft Office Integration _____________________________281 Registry strings ____________________________________282 Attribute Exchange for Microsoft Office Documents _______283 Adding new custom properties________________________285 Exporting and importing attribute mappings _____________287 Module Review _______________________________________288 Questions_________________________________________288 Managing Projects ___________________________________ 289 Module Overview______________________________________289 Module Prerequisites___________________________________289 Module Objectives _____________________________________289 Introductory Knowledge ________________________________289 Questions_________________________________________289 Answers __________________________________________290 Defining Projects ______________________________________290 Project strategy ____________________________________291 The one-to-many definition __________________________291 Define a template project folder structure_______________292 Establish storage areas ______________________________292 Add new users _____________________________________293 Create security groups ______________________________293 Copying the template project to the new project _________294 Applying the security schema _________________________294 Backup and restore procedures _______________________294 Full back up one-to-many project definition _____________297 Export command line options _________________________298 Module Review _______________________________________300 Questions_________________________________________300 Spatial Management _________________________________ 301 Module Overview______________________________________301 Table of Contents Copyright © 2010 Bentley Systems.

Module Prerequisites___________________________________301 Module Objectives _____________________________________301 Introductory Knowledge ________________________________302 Questions_________________________________________302 Answers __________________________________________302 Spatial Management ___________________________________302 ProjectWise Explorer’s Spatial tab _____________________302 Working with Coordinate Systems ________________________303 Defining Spatial Symbologies_____________________________305 Working with Background Maps __________________________307 Creation __________________________________________307 Static CAD Layers___________________________________307 Dynamic CAD layers_________________________________308 DPR Layers ________________________________________308 Scanning for Spatial Locations ____________________________310 Associating applications to metadata scanners ___________311 Scanning using ProjectWise Explorer ___________________312 Creating spatial location files _________________________313 Loading spatial location files __________________________314 Using the Spatial Tab ___________________________________315 Drawing spatial locations ____________________________315 Spatial Searches _______________________________________317 Module Review _______________________________________319 Questions_________________________________________319 ProjectWise Web Server ______________________________ 321 Module Overview______________________________________321 Module Prerequisites___________________________________321 Module Objectives _____________________________________321 Introductory Knowledge ________________________________322 Questions_________________________________________322 Answers __________________________________________322 SharePoint Implementation______________________________322 Configuring SharePoint services _______________________323 Creating a web application ___________________________325 Adding users ______________________________________326 Installing ProjectWise Web Server ________________________327 ProjectWise Web Server and Web View Server supports: ___328 Before installing____________________________________329 Configuring User Settings for Web Parts Users _______________333 Configuring Web Parts in a SharePoint Site _________________334 Standalone web parts _______________________________335 Usability enhancements for users______________________336 Connecting web parts to a datasource __________________336 Configuring Web Parts in a Non-SharePoint Site _____________339 Integrating with ProjectWise Publishing Server ______________342 Jun-10 Copyright © 2010 Bentley Systems. Incorporated xiii Table of Contents .

Incorporated xiv Jun-10 .Table of Contents Performance and port configuration ___________________342 Procedure ________________________________________342 Configuring Users' Systems ______________________________344 Design Compare_______________________________________346 Module Review _______________________________________347 Questions_________________________________________347 ProjectWise Maintenance ____________________________ 349 Module Overview______________________________________349 Module Prerequisites___________________________________349 Module Objectives _____________________________________349 ProjectWise Administrator Specific ________________________349 Datasource names__________________________________349 DFT benchmark tool ________________________________350 ProjectWise Explorer Specific ____________________________351 Importing export files from earlier versions ______________351 Scan for References after converting a pre-8.1 datasource __351 Vista users disable protected mode in IE ________________352 Module Review Answers _____________________________ 353 Document Architecture _________________________________353 Questions_________________________________________353 Answers __________________________________________353 ProjectWise Explorer Best Practices _______________________354 Questions_________________________________________354 Answers __________________________________________354 User Accounts ________________________________________355 Questions_________________________________________355 Answers __________________________________________355 Environments _________________________________________356 Questions_________________________________________356 Answers __________________________________________356 Importing Legacy Documents ____________________________357 Questions_________________________________________357 Answers __________________________________________357 Document Indexing ____________________________________358 Questions_________________________________________358 Answers __________________________________________358 Audit Trail____________________________________________359 Questions_________________________________________359 Answers __________________________________________359 Access Control ________________________________________360 Questions_________________________________________360 Answers __________________________________________360 ProjectWise Workflows _________________________________361 Questions_________________________________________361 Table of Contents Copyright © 2010 Bentley Systems.

Incorporated xv Table of Contents .Answers __________________________________________361 Integrated Applications _________________________________362 Questions_________________________________________362 Answers __________________________________________362 Managing Projects _____________________________________363 Questions_________________________________________363 Answers __________________________________________363 Spatial Management ___________________________________363 Questions_________________________________________363 Answers __________________________________________364 ProjectWise Web Server ________________________________364 Questions_________________________________________364 Answers __________________________________________365 Glossary ___________________________________________ 367 Jun-10 Copyright © 2010 Bentley Systems.

Incorporated xvi Jun-10 .Table of Contents Table of Contents Copyright © 2010 Bentley Systems.

Course Overview Course Description This course presents the ProjectWise Administrator application. It focuses on the options available to administrators from within the application. Course Objectives After completing this course. Target Audience This course is recommended for the following audience: • • Administrators who need to understand how ProjectWise relates to the management of projects and documents Those who require the ability to set up and manage a datasource. as opposed to those things done externally through database manipulation. Prerequisites • Participants should have a basic familiarity with ProjectWise Explorer and an understanding of network management. you will be able to: • • • Understand document architecture Set up and maintain a datasource Implement ProjectWise Web Server Jun-10 1 Copyright © 2010 Bentley Systems. Incorporated Course Overview .

Incorporated 2 Jun-10 .Course Objectives Course Overview Copyright © 2010 Bentley Systems.

Incorporated Document Architecture . As those familiar with the ProjectWise Explorer client know. Module Prerequisites • Familiarity with the ProjectWise Explorer client Module Objectives After completing this module. you will be able to: • • • • Decipher document information Create documents Understand extended document properties Create departments Jun-10 3 Copyright © 2010 Bentley Systems.Document Architecture Module Overview This module discusses the concept of a ProjectWise document and the techniques used to store document records in the datasource. but they really represent different concepts. he terms document and file may appear interchangeable.

Document File Name. It is an item in a ProjectWise folder.Introductory Knowledge Introductory Knowledge Before you begin this module. where is the document placed? What is a simple definition for a datasource? Answers 1 The ProjectWise definition for a document is. it is representative of the type of information maintained for each document. essentially. When they perform a check out. the term document refers to a row in the ProjectWise datasource. What is the ProjectWise definition for a document? When a team member wants to edit a document. which is either an electronic file. Each datasource represents a working area. Document Application. are displayed. Document ID. they can check it out. the available working areas. Each datasource is associated with a separate database and one or more storage locations. a few fields are Document Architecture Copyright © 2010 Bentley Systems. let's define what you already know. In addition. Incorporated 4 Jun-10 . When ProjectWise is launched. Document Creator. while others are for internal use and are not exposed. This row includes attributes such as: Document Name. it becomes a “document”. or a placeholder for an electronic or hard copy file that is not stored in ProjectWise. Document Status While this list is not all-inclusive. Document Version. Some of the fields are visible to the user. 2 3 Document Information Within ProjectWise. Questions 1 2 3 When a file is uploaded from a file system into ProjectWise. the document is placed into a working directory on their system and the database record for the document is marked accordingly. When a team member performs a check out. or datasources. Document Description. a record in the database.

the Document File Name field is one of the optional fields. In each case. but most are optional.Creating Documents mandatory. or may serve to index legacy paper documents. Since there is no file associated with this document. and then added that information to the file name field in the new row You can create an abstract document using the Document >New or New command from the right click menu. Most importantly. there are multiple methods for accomplishing the task. a file is created outside of ProjectWise. Incorporated 5 Document Architecture . there is no need to set the Application field. New documents have been created using three different methods. it is quite possible that metadata was already entered into ProjectWise. ProjectWise completed the following steps: • • • • Created a new row in the datasource using the file name as the document name Set the document creator field in the new row to the current user Set the document created date field in the new row to the current time and date Copied the file to the storage area designated for the folder. so it is of limited value. Converting abstract documents In the case where a document is converted from paper to electronic media. Abstract documents may serve as placeholders for documents yet to be created. a document does not have to have a file associated with it. • • • Drag and drop from Windows Explorer New document with no file associated New document with a file associated During that process. Creating Documents The procedure for creating documents varies depending on the source. a seed or template file is used. In other cases. If the image Jun-10 Copyright © 2010 Bentley Systems. There is no file associated with this type of document. there is no existing document and a new one is created. In some cases. Alternatively. and then must be imported. In other words.

Incorporated 6 Jun-10 . and are not typically exposed to the user. and are thus often referred to as GUID’s. click Advanced and select Import. This is also more Document Architecture Copyright © 2010 Bentley Systems. The Document Name and Description remain the same. By creating a custom view. Deleting the old document prior to importing the new one is not a good option because the existing metadata would be lost. The Application is determined based on the file’s extension. ID’s are for system use only. so special steps must be taken in order to view it. In addition. because names must be unique within the folder. While not useful to users. Document ID’s Every document is assigned an identification number within ProjectWise. The file name is inserted into the File Name field. it is sometimes advantageous for administrators to view GUID’s. select the document and press the space bar to open the document properties dialog. The administrator does not have the ability to assign or manipulate document ID’s. The best method is to convert the existing abstract document to a document with a file. Even though the Document Name. Click Save. Globally unique ID’s are system generated strings that are never duplicated. ProjectWise Explorer can display any sub-set of document attributes as columns within the document view. the GUID remains constant throughout the life of the document. or File Name can be changed. in ProjectWise Explorer. This property is not displayed in the standard document properties dialog. and then Close. Document ID’s are said to be globally unique.  How to convert an existing abstract document: First. the new document must have a different name than the old. the metadata on the existing document record is not transferred to the new record.Creating Documents file was imported into ProjectWise as a new document. In the File section. Navigate to the location of the document you want to associate to the abstract document and select it.

and drop them. Select View > Manage Views. 4 5 6 7 8 9 10 Collapse Basic Columns and expand the Folder Columns category. the folder ID is the number used to identify the physical folder in the storage area. Create a new root level folder named Document Indexing. Incorporated 7 Document Architecture . Although a GUID is a complicated string that is rarely of direct use. 11 Double click Folder Id to add it to the list. In Windows Explorer.Creating Documents convenient than opening the document properties dialog each time you need to see additional properties. and then click Close. You see the order in which the folders were added to the datasource and also the dms folder ID. 12 Click OK. In the Manage Views dialog. Scroll to File Size and double click to add it to the list. 14 Open one of the sub-folders and note the IDs. click New. expand the Basic Columns category. log in as the administrative user. On the left side of the dialog. Jun-10 Copyright © 2010 Bentley Systems. and can be quite useful. Double click Object Id to add it to the list. a dmsXXXXX number. drag the sub-folders from that folder into the new ProjectWise folder.  Exercise: Viewing object and folder ID’s 1 2 3 Launch ProjectWise Explorer. This Id shows the order in which items are added to the datasource. Name the view Identification. 13 Set the View to Identification and click the Document Indexing folder. navigate to the \Document Indexing folder in the class data set.

the preview pane can be used to display more properties for a single document. Information stored in these tables is linked back to their respective documents using the document GUID. which is not desirable. Once again. You might expect that each folder would be represented in the datasource by its own table. This method works well for storing standard document metadata. ProjectWise also allows extended document attributes. Log out of the datasource and exit ProjectWise Explorer when you are done. ProjectWise also maintains tables for folder and document security. In this case. This way searches are quick because only a single table is searched. However. Document Architecture Copyright © 2010 Bentley Systems. This would result in a constantly changing database schema. Incorporated 8 Jun-10 . Those properties are accessed on the General tab of the document properties dialog. that would require ProjectWise to create a new table in the database each time a folder was created. ProjectWise tracks the folder to which a document belongs as a column in the documents table. this way it can show a different view than the document list.Extended Document Properties Document preview In ProjectWise Explorer. There may be times when a user would like to view even more information. Extended Document Properties ProjectWise automatically stores a standard set of attributes for every document. Standard properties for all documents within the datasource are stored in a single table. Users can select the columns to display within the preview pane using its View option menu. These fields are pre-defined by ProjectWise and are not subject change during implementation. To provide flexibility. In addition to the standard document fields. these tables are pre-defined by ProjectWise and are not subject to change during implementation. the document view’s columns are useful to access additional document information. Note the tabs contents.  Exercise: Review the document properties dialog 1 2 3 Right click on a file in the open folder and select Properties. The document properties dialog has tabs for accessing this metadata.

Incorporated 9 Document Architecture . or delete the file. If used. If a user selects the Attributes or More Attributes tab for a document. Jun-10 Copyright © 2010 Bentley Systems. It also includes settings to determine which users can read or write document metadata. and the table in which they’re defined. it provides a tool to change ownership of a document. Once the tables are defined. Lastly. The administrator is responsible for defining additional tables in the database to store this information. write to. many administrators prefer to establish security at the folder level. these tools build an access control list for each document. there is no interface. In addition. but does not create an interface to gain access to the data. Importing an environment import creates a table in which to store additional data. While this is a powerful feature. The term environment refers to a set of extended document attributes. rather than at the file level. This information is stored in the document security table. if security changes were required. it can be quite time consuming to build an access control list for each document. each document would need to be individually modified. that will appear when users select either the Attributes or More Attributes tabs. a form. the administrator then creates a user interface. Attributes and More Attributes tabs These tabs are the user’s means of accessing extended document metadata. Therefore.Extended Document Properties Security tab This tab provides the tools to establish security at the document level. This includes settings such as which users are allowed to read.

and AutoCAD to store information such as a file’s author. the last date printed. File Properties tab This tab provides user access to the properties of the file as stored on the file system. etc. This tab is also defined by the administrator. and to run for a specified interval of time. you can also manually start the extraction. Note: Note that the appearance of the File Properties tab is determined by the user properties setting User Interface -> Show file properties. Windows provides a means to store file attributes at the operating system level. Document Architecture Copyright © 2010 Bentley Systems. Some applications don’t store any information at all. using the ProjectWise Administrator application. Running file property extractions You can configure file property extractions to start automatically based on a schedule. while others store information that is only useful to the program itself. This feature is used primarily by applications like Microsoft Word. or if no extraction schedule is defined. MicroStation. If you need to run an extraction before the next extraction is scheduled to occur.Extended Document Properties The More Attributes tab is used to display additional attributes when there are too many to display on the Attributes tab. An administrator must configure ProjectWise to display the items that will be meaningful to the user. There is very little consistency between applications as to what is stored. Incorporated 10 Jun-10 . Some applications store information that is useful to users here.

However. Incorporated 11 Document Architecture . Configure extension mapping rules as necessary on Jun-10 Copyright © 2010 Bentley Systems. regardless of any non-standard file extensions. no scheduled extractions will occur and no manual extractions can start.Extended Document Properties Extracted file property data displays on the File Properties tab on the respective document's properties dialog. and then enter their password. enable the Extraction enabled check box. For example. select the user who will run the extractions. Then. Note: When the Extraction enabled option is off. For file property extractions. enable the Extraction enabled check box. a Microsoft Word document with the extension ABC. and then OK You can configure extension mapping rules as necessary on the File Type Associations tab. and can be searched on in ProjectWise Explorer's Search dialogs. the user account specified must have Document Read and Document Write access. On the Scheduled Updates tab. rather than DOC. you may want to use the File Type Associations tab to prevent documents of certain file types from being processed. after you manually start an extraction. On the General tab. and who has other appropriate user properties settings set.  How to enable and schedule file property extractions: In ProjectWise Administrator. expand the Document Processors icon. as long as the files being processed are structured COM storages. file properties are extracted successfully. and no configuration on this tab is necessary. select Run and in the time table. Set up a special account for extractions whose user properties setting General -> Use access control is off. Click Apply. select the user account that the document processor will use for copying out the documents and updating their processing status. in the console tree. the next extraction will occur as regularly scheduled. click all the day/time cells during which you want extractions to run. Right click File Property Extractions and select Properties. will still be extracted successfully. and the user properties setting Document -> Modify must be set.  How to manually start file property extractions: In the File Property Extraction Properties dialog. General tab. Manual extractions Starting extractions manually will not cancel any upcoming extractions you have scheduled. and enter their password. For File Properties extractions.

Click Apply. an iFilter for Outlook. such as: Microsoft Word documents Microsoft Excel spreadsheets Microsoft Power Point presentations Microsoft Projects Microsoft Visio drawings MicroStation V8 DGN files Though these were the file types tested with file properties extractions. rather than DOC. Now you can perform file extractions on e-mail messages so you can do full text searches on their contents.msi. you can extract file properties from other file types that are structured COM storages. Hint: Download msgflt.Extended Document Properties the File Type Associations tab. you create an extension mapping rule that prevents files with that extension from being extracted. Once that many documents are processed. is still extracted successfully unless. a Microsoft Word document having the extension ABC. the extraction is over. For example. of course. and then OK. from Microsoft and install it on the server so ProjectWise understands what an e-mail message is. The number of documents processed when you manually start an extraction is determined by the number you set in the Max documents processed in a single pass field on the General tab of the Full Text Indexing Properties dialog. Incorporated 12 Jun-10 . Workspace tab This tab is used assign an unmanaged workspace profile or various managed workspace settings. Configuration settings blocks and workspace profiles are discussed in conjunction with integrated applications. Document Architecture Copyright © 2010 Bentley Systems. Right click the File Property Extraction icon again and select Start Processing Now. There is no limitation on the extensions for files that are structured COM storages. Supported file types for file property extractions File properties can be extracted from files that are structured COM storages.

or divisions within the organization. there is no method to automatically set the correct department. Jun-10 Copyright © 2010 Bentley Systems. and optionally. doors. Users in the plant industry.Departments Components tab This tab is used to review all components included in the document. and windows. assuming components have been extracted from this document and a component index has been generated. A component is an asset or item that is important to your business. you will build the list of Departments that is presented to users. components are extracted from DGN documents in the datasource. Users are required to select the appropriate Department value when entering data in the New Document dialog. for example. As the administrator. components are mapped to tables in the database for persistent storage. disciplines. might consider components to be equipment or process lines. Some examples might be office locations. the creation of an index that specifies the location of those components in their respective documents. project names. ProjectWise Explorer provides an interface to set this field. They are listed. The term department already has meaning for most organizations. The components are categorized by class. Users in the building industry might consider components to be walls. This attribute is most useful to provide logical information for users when searching for documents. Using ProjectWise Class Editor. Component indexing involves the identification and classification of components within documents. Using ProjectWise Automation Service. In order to optimize use of Departments in ProjectWise. When creating new documents. the extraction and importation of component data. but does not use the field directly. Incorporated 13 Document Architecture . Departments A Department is simply a built-in attribute to help define document ownership. you should use this field to represent existing departmental structures when they exist.

Module Review Now that you have completed this module. ProjectWise does not use the Department field directly. type the following. Questions 1 What is an abstract document? Document Architecture Copyright © 2010 Bentley Systems.Module Review Creating Departments Departments are created using ProjectWise Administrator. and then click OK: Name: Marketing Description: Marketing Dept. so there are no consequences from leaving this field blank. Admin/Administrative Support Care should be taken to assign the proper department to each new document as it is created. let’s measure what you have learned. in the New Department Properties dialog. It is provided as a means by which to search for documents. Incorporated 14 Jun-10 . 4 Create two more departments: Construction/Construction Dept. Existing documents can be modified so that their Department is correct. Right click Departments in the console tree and select New > Department.  Exercise: Adding Departments 1 2 3 Log in to ProjectWise Administrator as the administrative user. In the New Department Properties dialog.

and no manual extractions can start. Incorporated 15 Document Architecture . Jun-10 Copyright © 2010 Bentley Systems. Why? What is a GUID? What are the Attributes and More Attributes tabs in the document properties dialog? True or False: When the Extraction enabled option is off in the File Property Extraction Properties dialog.Module Review 2 3 4 5 It is not a good idea to delete an existing abstract document and import a new one. no scheduled extractions will occur.

Incorporated 16 Jun-10 .Module Review Document Architecture Copyright © 2010 Bentley Systems.

Module Prerequisites • • General knowledge about ProjectWise Explorer Knowledge about document architecture Module Objectives After completing this module. Incorporated ProjectWise Explorer Best Practices . you will be able to: • • • Understand ProjectWise Explorer networking Understand basic file operations Define ProjectWise applications Jun-10 17 Copyright © 2010 Bentley Systems.ProjectWise Explorer Best Practices Module Overview This module examines how ProjectWise Explorer works in some detail. This will help you to develop best practices.

let's define what you already know. Warning: Never directly delete the directories or files created by ProjectWise from Windows Explorer. Use the Local Document Organizer or the check in and purge commands. Incorporated 18 Jun-10 . Use Attributes to track document information. An interface is a predefined arrangement of a document’s attributes in the properties dialog’s Attributes and More Attributes tabs. The second icon indicates the document’s type and its associated application.Introductory Knowledge Introductory Knowledge Before you begin this module. 3 The first icon indicates the general permissions and status for the document. or to enter information in the title blocks of designs. 4 5 6 7 ProjectWise Explorer Best Practices Copyright © 2010 Bentley Systems. Questions 1 2 3 4 5 6 7 What is your working directory? How do you maintain your working directory? What do the two icons that are associated with each document tell you? Where do you choose the types of information you want to see about documents or folders? What is on the Attributes More Attributes tabs? What is a workspace profile? What is an Interface? Answers 1 2 The area to which ProjectWise copies the files that you work with. Select View > Manage Views to open the Create View dialog. search for documents. These define the location of a MicroStation workspace that exists on a local or network drive outside of ProjectWise.

Click Apply. Incorporated 19 ProjectWise Explorer Best Practices . but this is rarely required. The log in process and all subsequent communication between the ProjectWise client and integration server takes place using TCP port 5800. If the Display Name field is populated. The server can be configured to use other ports if necessary. ProjectWise Servers on the network listen for these requests. This broadcast is in the form of a UDP protocol request on port 5799. More specifically. client systems would automatically detect it and request its list of datasources. If users are logged in to ProjectWise Explorer they must Refresh to see the new name. users can log in.ProjectWise Explorer Networking ProjectWise Explorer Networking When ProjectWise Explorer launches. Datasource display names When the datasource is added to the server. the datasource list returns to the client in the format ServerName:DatasourceName. it attempts to discover any ProjectWise Servers on the network by sending out a broadcast on the network. Once the datasource list has been retrieved.  How to change a display name: In ProjectWise Administrator right click the datasource and select Properties. Enter the desired Display Name. If the Display Name is omitted. Broadcasting for the datasource list is a convenient feature because it lets ProjectWise Explorer find the server without requiring configuration. The downside is that network broadcasts are considered chatty. it will take precedence and the datasource list is returned to the client in the format DisplayName. and are discouraged by many network administrators. fields are provided for the Name and a Display Name. the port must be open bi-directionally between the client and server for ProjectWise log in to succeed. users see the name twice in their datasource list and won’t be able to tell them apart. and respond by sending back their respective datasource lists. and then OK to close the datasource Properties dialog. Note: If two servers use the same display name. If a new server were brought online. Regardless of the port choice. broadcasts generate significant traffic on the network because the request is sent to every Jun-10 Copyright © 2010 Bentley Systems.

In addition. UDP. Typically. ProjectWise internal Domain Name System information can be retrieved from any server within a subnet using the UDP protocol. the broadcast method will likely fail to produce a datasource list because the router connecting the sub-nets will not allow the broadcast packets to pass from one sub-net to the other. but you can also use it to establish a TCP connection to a local server. Incorporated 20 Jun-10 . In this case. is a connectionless protocol that runs on top of IP networks. many network administrators prefer to limit network broadcasts in order to make their networks run more efficiently. most routers block broadcasts. Navigating multiple sub-nets In many corporate networks. By default. thus improving performance on the client system. ProjectWise network configuration Once ProjectWise Explorer is installed. It is primarily used to establish a TCP connection from the client to one or more servers. so this method is limited to finding servers on the same sub-net. This tool is used to configure the networking aspects of the ProjectWise Explorer client application. ProjectWise provides a number of alternate network modes so it can function in most any network environment. ProjectWise clients request ProjectWise DNS information using the UDP protocol from ProjectWise Gateway Services and ProjectWise Integration Servers that are situated within the same subnet. the ProjectWise Integration Server and Explorer client will not be on the same sub-net. you use this dialog to connect the client to remote servers. In addition. and then block the client from broadcasting UDP requests.ProjectWise Explorer Networking system on the network. The User Datagram Protocol. the ProjectWise V8i Network item appears in the Control Panel. ProjectWise must provide another means of obtaining the datasource list. ProjectWise Explorer Best Practices Copyright © 2010 Bentley Systems. In these configurations.

logging in by key-in. When this option is not checked. Jun-10 Copyright © 2010 Bentley Systems. but this client is not sending out any requests. 5 6 Click OK to close the dialog. There are three methods for accomplishing this task. Double click the ProjectWise V8i Network item. Incorporated 21 ProjectWise Explorer Best Practices .  Exercise: Disabling datasource list broadcasts 1 2 3 4 Open the Control Panel. your server’s datasources will always display in ProjectWise Explorer if your ProjectWise Integration Server happens to be on the same system as your ProjectWise Explorer client. when you do turn on Prevent UDP on the Datasource Listing tab. or when you open the Export Wizard or the Import Wizard. your server's datasources will not display in the datasource list of the ProjectWise Log in dialog that opens when you launch integrated applications from the desktop. the default. the setting is inherited from other configuration settings. • • • Do nothing. Require users to enter the server name each time. In those cases. you can still log in to the datasource by entering the servername:datasourcename in the Datasource field. Click the Prevent UDP check box in the lower left corner until it contains a check mark. However. The server is still listening for UDP requests on port 5799. Select the Datasource Listing tab. Exit ProjectWise Explorer. When it is grayed. The challenge now is to configure ProjectWise Explorer to find the server again. UDP is not prevented. This simulates an environment where the ProjectWise client and server are on different sub-nets. It must be solid to prevent UDP. and then re-launch it. Use the Gateway Service as the method of publishing datasource lists to clients.ProjectWise Explorer Networking Whether or not you turn on Prevent UDP on the Datasource Listing tab. The datasource list should now be empty because your ProjectWise Explorer client is no longer requesting the datasource list. Use the ProjectWise V8i Network Configuration Settings dialog to specify the server.

Select the Datasource Listing tab. However. user name.  Exercise: Identifying the server for datasource lists 1 2 3 4 Open the Control Panel. Once the ProjectWise Explorer client knows the identity of the Integration Server. Enter the administrative user name and password and click Login. In the Data Source field. it also enables the administrator to identify the ProjectWise Integration Server.  Exercise: Log in to a datasource by key in 1 2 In ProjectWise Explorer. the user must enter data into the datasource name. Enter the following: Name: myServer Host/IP: [yourServerName] ProjectWise Explorer Best Practices Copyright © 2010 Bentley Systems. and password fields in the login dialog. Log in by key-in ProjectWise Explorer is able to log in to a datasource. select Login from the Datasource menu. Using ProjectWise V8i Network configuration Just as this tool allows you to disable the broadcast feature. so users will only have to enter this once unless multiple datasources are in use. The datasource display name cannot be used.ProjectWise Explorer Networking Note: To prevent UDP globally. The datasource name should be entered in ServerName:DatasourceName format. In order to use this method. Double click the ProjectWise V8i Network item. it no longer needs to broadcast to find it. The datasource list is strictly a matter of convenience so users don’t have to remember the datasource name. Incorporated 22 Jun-10 . since it does not contain the server name. check the Prevent UDP for DNS and Listing check box. on the General tab. enter: [MachineName:Datasource]. even when no datasources appear in the list. ProjectWise remembers the most recent datasource name. 3 This may seem cumbersome for users.

If the server’s datasource configuration changes. In addition. In the Host/IP fields on the DNS Services and Datasource Listing tabs. No system level error dialogs will pop up on the system. they can easily be implemented by importing new or modified registry keys.ProjectWise Explorer Networking Port: [leave blank] 5 6 Note: Click Add.cfg file of the Integration Server or Gateway Service to which you are connecting. those changes are automatically detected by the ProjectWise Explorer client application. enter the Name and IP address of the computer on which the ProjectWise server containing name resolution information is installed. set the following registry key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Windows\ErrorMod e=2 This registry setting applies to all processes running on the machine. the errors are written to the system log. Jun-10 Copyright © 2010 Bentley Systems. If this occurs. the ProjectWise V8i Network Configuration Settings dialog stores configuration information in the Windows Registry. ProjectWise network registry entries The server-side MicroStation engine used for processing DGN/DWG files displays a system level modal dialog in the event of a system level error. You only need to enter a port number on the DNS Services and Datasource Listing tabs if the default listener port has been changed in the dmskrnl. MicroStation will pause and prevent jobs using the engine from completing. in the respective fields. The system will log exceptions on client machines without notifying you through a modal dialog. The default listener port used for TCP connections is 5800. Open ProjectWise Explorer and note the datasource list. When client-side changes are necessary. Take advantage of this. and then click OK to close the dialog. This is a recommended setting on server machines. • Using the Network Configuration Settings tool makes maintaining the configuration is easier. To suppress the display of this modal dialog. however. Incorporated 23 ProjectWise Explorer Best Practices . • • The name field is for a descriptive name that may contain any character string. using a meaningful name to make maintenance easier.

3. this would include the status of the document (is it already checked out to someone else?). asking to check out the specified document. At a minimum. In any case. This directory is known in ProjectWise as the working directory. When properly implemented. the file must be transferred to the local client system and placed into a temporary directory. and the access control list for the document. The ProjectWise Explorer sends a message to the ProjectWise Server. The ProjectWise Server retrieves all pertinent database records in order to decide if the user should be allowed to check out the document. 5. Finally. they must request access to the file through ProjectWise. which is an implied check out since the file must be checked out before it can be opened. the user may already be in an application and select File > Open in order to retrieve a new document. Incorporated 24 Jun-10 . This way. 2. changing the document status to Going Out. although most of it is transparent to the user. 1. The user may select a file and then select Check Out from the Document menu. the ProjectWise Server executes a database transaction. ProjectWise Explorer Best Practices Copyright © 2010 Bentley Systems. The file is then transferred from the storage area to the user’s working directory. The ProjectWise Server then determines the storage area for the specified document. double clicking initiates the Open command. indicating the file to send. Document Check Out and check in Users must check out files in order to work on them or copy out files in order to view them. By default.Basic File Operations Basic File Operations ProjectWise stores all files on servers in specifically designated folders known as storage areas. 6. In order to view or modify a file. 4. or double click the file. the following process takes place. ProjectWise implements access control to prevent unauthorized access to files. and placed in a sub-folder of the same name as that of the folder on the server (dmsXXXXX). Assuming the user is allowed access to the document. and to prevent two users from modifying the same file. The client then initiates a conversation with the system hosting the storage area. This information is sent back to the client. storage areas are not accessible to users from Windows Explorer. Since users don’t have direct access to the files on the server. The check out process can be initiated different ways.

The working directory The ProjectWise working directory is a temporary location where files are placed when checked out by ProjectWise Explorer. In this case. As files are transferred to and from the server. the physical storage folder for A is dms00050. system. folder A could have a document named readme. Jun-10 Copyright © 2010 Bentley Systems. If a document appears to be permanently in either status. Finally. This transaction writes a record of the document. ProjectWise Explorer creates sub-folders under the working directory matching the physical folder names on the server. The first folder created. Folder ID’s typically start with the number 50 and increment upward. the file is verified for completeness and the conversation with the storage area system is terminated. The check in process is the reverse of the check out. as could folder B. and date of the check out. The ProjectWise Explorer then sends a message to the ProjectWise Server indicating a successful check out. The administrator will need to contact the user owning the document and decide on the best course of action. and so on. will have ID=50. So. folder A in this case. While users work with directories by their name. Within the storage area. 10. changing the document status from Going Out to Checked Out. ProjectWise creates sub-folders under this directory for each involved ProjectWise directory. Assume for the moment that the working directory is set to C:\pw-wrkdir. When file transfer is completed. but only temporarily.html. The ProjectWise Server completes the operation by executing a database transaction. user. what would happen if a user attempted to check out both of those documents at the same time? To prevent one from overwriting the other. it indicates a transfer problem. Incorporated 25 ProjectWise Explorer Best Practices . the ProjectWise Server executes one last database transaction. Within ProjectWise. ProjectWise maintains a numerical ID for each directory. Going Out and Coming In are also legitimate values for document status. document names need not be unique unless they are in the same folder. the temporary status is set to Coming In. 9. and the physical location for B is dms00051. 8.Basic File Operations 7. time. folder B will have ID=51. The only significant difference is that when the document is being checked in.

Incorporated 26 Jun-10 . The administrator has the option to pre-set this configuration for each user. however the sub-folders are not. When users select Check In or Update Server Copy. master1.dgn. Each XML file will have the name of the master file prepended to the file name. and to determine if the user is allowed to change it.xml. if the user checked out both readme. changes documented in the XML file are discarded and not saved to the database. click on Users in the console tree. an XML file is created in the working directory. Log out in ProjectWise Explorer. The user can access just those items the administrator allows them to change from ProjectWise Explorer.html files. the changes documented in the XML file are saved to the logical set in the database. the local working directory would look like: C:\pw-wrkdir\dms00050\readme.xml.Basic File Operations In the example. For example. the local copy of each file is removed when the document is checked back in. The administrator can access the settings for any user from ProjectWise Administrator.dwg.html When both files are checked back in. Click Cancel to close the dialog. 4 5 6 7 8 ProjectWise Explorer Best Practices Copyright © 2010 Bentley Systems. select Tools > Options. In ProjectWise Administrator. This means the user can change the working directory. The working directory is configured as a per-user setting and should be unique for each user. This file lists all the master document's references. master2.html C:\pw-wrkdir\dms00051\readme.  Exercise: Changing the working directory user properties setting 1 2 3 In ProjectWise Explorer. If users free the master document. Select the Settings tab. the local working directory would look like: C:\pw-wrkdir\dms00050 C:\pw-wrkdir\dms00051 Note: By default. You see the Working Directory item. Double click the administrative user in the list view. For each master MicroStation or AutoCAD document you check out.fileinfo.fileinfo. Select the Settings tab in the Properties dialog. and records all reference-related changes to the master document.

Basic File Operations

9

Double click the Working Directory item.

10 Disable Allow user to change working directory and click OK. 11 Log in to ProjectWise Explorer using the administrative credentials, and

then and select Tools > Options.
12 Select the Settings tab.

Since you can no longer change the Working Directory setting, it is removed.
13 Click Cancel to close the dialog. 14 Exit ProjectWise Explorer.

Exercise: Returning the working directory user properties setting
1 2 3 4

In ProjectWise Administrator, double click the administrative user in the list view. Select the Settings tab in the Properties dialog. Double click the Working Directory item. Enable Allow user to change working directory and click OK.

Note:

• •

If two users are sharing a client system, they should not share working directories. Each user should have a unique working directory. Working directories can be set to network drives, although there is no advantage to doing so. Performance is better when working directories are local. When a user checks out a document, the document can only be worked on from the requesting client system. This holds true even if their working directory is set to a network drive. A user may not check out a drawing on one system, and expect to work on it from another.

Warning:

Administrators should take care to check in all files and purge all copies if a client system will undergo a node-name change. Once the name is changed, the user cannot check in files that were checked out prior to the name change. Users should not work on files directly from the working directory using Windows Explorer. Users should not attempt to maintain the working directory from Windows Explorer. For the most part, ProjectWise maintains

Jun-10

Copyright © 2010 Bentley Systems, Incorporated

27

ProjectWise Explorer Best Practices

Basic File Operations

this directory automatically. ProjectWise Explorer provides tools for advanced users to manage this directory if they must. • Users should not change their working directory unless all documents are checked in and all copies purged. At this point, the directory is empty and can be deleted. Thought should go into establishing a standard for working directories. You must plan for a location that provides storage drive space. In addition, if you don’t allow users to change the setting, and inadvertently set it to a nonexistent drive, the user cannot log in. If multiple datasources are in use, it is also a good idea to include the datasource name or abbreviation in the working directory path. Therefore, a suggested standard for working directory names is: C:\pw-wrkdir\datasourcename\username This standard provides for multiple datasources as well as multiple users on a single client system. In addition, ProjectWise provides a mechanism to make it easy to define this path as a default for all users. A document must be checked out by the user prior to being opened for modification. The user can open a document in two steps, Check out and then Open, or simply Open the document in a single operation. In the event that the user chooses Open for a document that is not checked out, ProjectWise will check out the document and then open it. By default, the Open command is executed when the user double clicks a file. Similar to the working directory, this setting can be changed in the user’s settings.

Delta file transfer
Delta File Transfer, or DFT, can improve file transfer performance when using ProjectWise Explorer over a WAN connection by only sending the parts of a file that have changed over the network.

ProjectWise Explorer Best Practices

Copyright © 2010 Bentley Systems, Incorporated

28

Jun-10

Basic File Operations

Delta File Transfer takes two copies of a file, typically one on the file server and one in the user's working directory, and compares them. Based on the comparison, ProjectWise determines what portions of the file are different, takes those sections of the file, and sends them to the location of the other copy of the file. Once there, the changed portions are applied to the second copy of the file and once again the two copies are compared to be sure they match exactly. DFT works when ProjectWise Explorer or integrated applications are used. The overall process is based on a commonly used approach called RSYNC. The process of comparing the files uses a series of checksum calculations. Calculating the checksum requires that the file be read from disk, creating disk activity. Then the CPU calculates the checksum, creating CPU activity. In most cases, this activity is only fractionally higher then the current load on the machines, however, for very busy file servers, it may require a faster CPU and hard disk.
Hint: Watch CPU and disk activity on your main ProjectWise file servers to ensure

that you are getting the best possible performance from DFT.

How to check the Delta File Transfer datasource setting: In ProjectWise Administrator, log in to the datasource you will be using for the benchmark. Right click the datasource and select Properties. Select the Settings tab. Expand the Network category and make sure the Enable Delta File Transfer option is enabled.

Delta file transfer testing
To help you evaluate the benefits of DFT, there is a Benchmark Wizard for testing DFT in your environment. This Wizard is run from a user's machine, typically at a remote office, and can either run a standard set of files or a list of files you provide. The Wizard is delivered with the ProjectWise V8i Administrator installation, and requires a ProjectWise V8i datasource to which to connect. The wizard file name is dftbmwiz.exe. The wizard will walk you through the process. If you are running this test against a new datasource created using the ProjectWise Administrator, DFT is on by default. If you are running this test against an existing, upgraded datasource, you must first activate the Delta File Transfer datasource setting. The Delta file transfer benchmark tool creates example files in the selected storage area, runs a test check out and check in on them, and then displays statistics about the transfer.

Jun-10

Copyright © 2010 Bentley Systems, Incorporated

29

ProjectWise Explorer Best Practices

Basic File Operations

How to run a delta file transfer test: In Windows Explorer, navigate to the \Bentley\ProjectWise\bin folder and double click dftbmwiz.exe. When the Delta File Transfer Benchmark Tool opens, click Next. To run the tool the user setting Network -> Allow user to change client/server network settings must be enabled. Select a ProjectWise V8i datasource. Enter an administrative user name and password for a user that has the following user settings enabled; Folder Create, Folder - Delete, Document - Create, and Document - Delete. Click Next and select the storage area you want to use in the delta file transfer test. Click Next and enter the name of a test folder to be created. This is where the test files will be stored. This folder will be deleted after the test is run. Select Automatic DFT test and click Next. When the test is done, select the tabs at the top of the wizard to examine the results. If you want to save the results for your own information, click Save Results to save the results to a text file.

File types and delta file transfer
Delta File Transfer is file format independent and application independent, so it will work with any file and any version of MicroStation. It also works with Microsoft Office documents, raster files, or zip files. When using AutoCAD 2007, files are essentially re-written every time a user performs a Save. This affects the Delta File Transfer implementation.

Server settings
Delta File Transfer happens when users perform normal ProjectWise operations. Users continue to open and edit files the way they always have, only the experience is faster. One item that Administrators need to consider for the best performance is the use of the user setting “Leave local copy on Check in”. Enabling this setting causes ProjectWise to leave a copy of files that have been checked out and then checked back in in the user's working directory. This means the next time a user copies the file out, there is already a local copy of the file that DFT can use to do its comparisons. DFT is not likely to provide significant advantage to users that are working on files over a local high-performance LAN, however, it is also not likely to cause any performance degradation. However, if the users on the LAN are consistently working with very, very large files, the time taken to compare the files may cause

ProjectWise Explorer Best Practices

Copyright © 2010 Bentley Systems, Incorporated

30

Jun-10

ProjectWise Applications

some performance degradation compared to simply sending that whole file over the high performance LAN. For every ProjectWise Integration Server, Caching Server, and Gateway Service, delta file transfer is enabled by default. To disable it on a particular server, open that server’s (\Program Files\Bentley\ProjectWise\bin) dmskrnl.cfg file. In the [DFT] section, add the line enabled:false.

Datasource settings
The option Enable Delta File Transfer in the Network category on the Settings tab of the Datasource Properties dialog is enabled by default. This enables delta file transfer for all ProjectWise Explorer clients connected to this datasource. When this option is enabled, you must also enable the user setting of the same name for each user you want to benefit from delta file transfer. The option Compress client/server request data enables data compression for all ProjectWise Explorer and Administrator clients connected to a datasource. When this option is enabled, you must also enable the user setting of the same name for each user you want to benefit s data compression.

ProjectWise Applications
The Applications list in ProjectWise Administrator should contain a list of the programs users commonly use to open documents. When the datasource is created, the Applications list is automatically populated based on the applications defined in the file appinfo.xml, which is in the \ProjectWise\bin directory. You can

Jun-10

Copyright © 2010 Bentley Systems, Incorporated

31

ProjectWise Explorer Best Practices

ProjectWise Applications

modify the Applications list to add new applications, delete applications your users do not use, or modify the definitions of existing applications. Users associate documents to the appropriate application in ProjectWise Explorer so that opening a particular document will launch whatever program executable is defined for the associated application. When you define a ProjectWise application, you can select the default program icon that will display next to documents associated to that application in ProjectWise Explorer. You can also specify the file extensions that are typically opened by that application. By assigning file extensions to an application, new documents are automatically associated to the correct application based on their file extension. You also select the program to launch when a user tries to open, view, redline, or print a document that is associated to that application. Many of the application definitions in the delivered appinfo.xml file are fully configured, so depending on the applications you use, you may not need to do any additional application configuration. Users with permissions to modify documents can associate documents to existing applications as necessary. Users can use the applications as they are defined in ProjectWise Administrator, or they can define their own custom settings for existing applications by selecting Tools > Associations > Programs in ProjectWise Explorer, then set the association view to User Associations. Custom settings are unique to the user who sets them and are stored in the database, so they will follow the user no matter where the user logs in. When users have custom settings defined for an application, those settings are used instead of those currently configured for the application in ProjectWise Administrator. When a ProjectWise application contains at least one extension, and files having that extension are initially imported into ProjectWise Explorer, those new documents are automatically associated to the ProjectWise application. For example, if an application called MicroStation has the extension DGN assigned to it, then importing a DGN file into ProjectWise Explorer automatically associates that new ProjectWise document to the application MicroStation. Documents that already existed in ProjectWise when their respective application was created will have to be manually associated on the document's properties dialog.

Defining applications
A ProjectWise application is just a label. Most people tend to use the name of the program that will run from the client systems as the application name. This is not mandatory and there is no validation for a name.

ProjectWise Explorer Best Practices

Copyright © 2010 Bentley Systems, Incorporated

32

Jun-10

ProjectWise Applications

Once the application is named, you must define several additional items. • • • • • • The icon to display in ProjectWise Explorer for this type file The executable to use to open this type file Optional: the executable to be used to view this type file Optional: the executable to be used to redline this type file Optional: the executable to be used to print this type file Optional: extensions to be mapped to this application during import operations

All client configuration is done from the ProjectWise Administrator application in the New Application Properties dialog. Type the name, add file extensions, and set the icon to display on the General tab. Extensions are only used during file import operations and may be omitted.

Establish the executable used to modify, view, redline, and print the file on the Actions tab. Each executable defined here should exist on each client. In addition, the executable can be defined using a hard coded path, a relative path, or program class name. The program class name is the preferred method because it uses the Windows registry to locate the designated executable. Not all desktop applications create registry entries for program class, so those applications need to be defined using one of the path options. In these exercises, the default application for html files is overridden by the new application.

Exercise: Add the Internet Explorer application
1

In ProjectWise Administrator, click on Applications in the console tree. You see the list of default delivered applications.

Jun-10

Copyright © 2010 Bentley Systems, Incorporated

33

ProjectWise Explorer Best Practices

ProjectWise Applications

2 3 4

Right click Applications and select New > Application. In the New Application Properties dialog, type the name HTML. Type html in the File extensions field and click Add.

Note: Do not enter the dot in the extension, only the characters.

5 6 7 8

Enter htm in the File extensions field and click Add. Select the Actions tab and click Create. Set the Action option to View. Type the Program description: Internet Explorer Click browse, to the right of the Program class name field.

9

10 From the programs list, select Internet Explorer and click OK. 11 Enable the Set application icon check box.

12 Click OK to close the Create Association dialog.

ProjectWise Explorer Best Practices

Copyright © 2010 Bentley Systems, Incorporated

34

Jun-10

Click OK to close the New Application Properties dialog. the appropriate programs launches if it’s installed and opens the document. With the configuration defined as it is. Do not enable the Set application icon check box and click OK. If the htm or html extensions were mapped to another application. Action associations determine what program launches when a user tries to open. markup. and then set one as the default. For example. Redline and Print association type for each application. you can specify either its registry class name. Set Action to Open. when DGN documents are associated to the ProjectWise application called MicroStation. or print a document associated to an application. If the program is not installed or cannot be found. if needed. or the actual directory path to the program executable. click Create. but cannot print from ProjectWise Explorer. on the Actions tab. 4 5 6 7 Click Yes to complete the operation. To identify a particular program. select Notepad. you see that there are two associations for the Open action. ProjectWise Navigator as the program to redline DGN documents. view. Incorporated 35 ProjectWise Explorer Best Practices . and Bentley View as the program to view DGN documents. the user is given an option to manually select the correct program. However. and click OK. and for printing. redline. you will see a warning. you can create as many Open associations as you need for each application. The first Open action is the default and is associated to Bentley MicroStation and the second is associated to MicroStation V7. and they can’t redline. For example. Type the Program description: Notepad Click browse. if you open the properties for the existing application MicroStation. users can view and edit files of this type. You can only create one View. To fully define the application in the exercise you would add other action associations for redline. Jun-10 Copyright © 2010 Bentley Systems. Then when a user opts to open. you can set MicroStation as the default program to open DGN documents.ProjectWise Applications  Exercise: Add another Action 1 2 3 In the New Application Properties dialog. This way you can easily switch which program is the default for opening MicroStation documents. or view documents associated to MicroStation.

rather than as source code. actions. In the document view. To delete an application. click on Applications in the console tree. The key to this operation is to select Paste from the left pane. 2 3 4 5 6 7 Create a new root level folder named Folder A. Incorporated 36 Jun-10 .pdf and press the space bar on the keyboard to open the properties dialog. Right click the document and select View from the pop-up menu. and then select Copy. You can copy applications between datasources. log in using the administrative credentials. The document is checked out and opened in Notepad. The same properties dialog that was used to create the application opens. Since the document was not checked out. It is not available in the document view. The document is displayed in Internet Explorer as a web page. checking the document in. You can change the name. Double click the file. extensions. ProjectWise Explorer Best Practices Copyright © 2010 Bentley Systems. select the Applications that are to be copied. Click Save. You had to exit ProjectWise Explorer for the changes you made previously to be applied. In the document properties dialog. and then select Paste. In Windows Explorer. 8 9 10 Close the browser. change the Application to HTML. and drop them. Working with existing applications You may modify an application at any time by right clicking the application name and selecting Properties from the pop-up menu. and then click Close. drag the files from that folder into the new ProjectWise folder. you are not prompted to check it in this time. Exit Notepad. right click. right click. Select ProjectWise Applications.ProjectWise Applications  Exercise: Verifying the HTML application 1 Launch ProjectWise Explorer. In the target datasource. right click it and select Delete. navigate to \Folder A in the class data set. and icon.

 Exercise: Automatic application assignment during import 1 2 3 4 In ProjectWise Explorer.ProjectWise Applications Note: Once created. and the results are stored in the ProjectWise datasource. select all documents in Folder A.html as is.htm’s extension from htm to txt. the files in question were manually assigned to the application. This was necessary because the files were imported into ProjectWise prior to creating the Application. The ProjectWise administrator creates the configuration for the Application once. Change ProjectWise_Explorer. Jun-10 Copyright © 2010 Bentley Systems. an Application name cannot be deleted if it is associated with any documents. The standard application may be PaintShop Pro. There are two ways to solve this problem. Automatic assignment is based on the extensions entered into the Application definition. Change ProjectWise_Administrator. Applications are associated with each document in ProjectWise to govern their behavior. When prompted. In Windows Explorer. they are assigned to the documents automatically. Drag the files from the Windows folder into the ProjectWise folder and drop them. The actions defined within the application take precedence and provide more flexibility than relying on the file extension. click Yes to delete all documents. but some users may prefer to use Photoshop. Incorporated 37 ProjectWise Explorer Best Practices . navigate to \Folder A in the class data set.htm’s extension to html. In the previous example. Applications and file extensions The file extension has no bearing on the action that ProjectWise Explorer takes when opening documents. Leave ProjectWise. Right click and select Delete. Note the application associated with each file. A good example would be editing image files. 5 6 7 8 User overrides for application actions There may be cases where a user would like to use a different application than the standard. When the Application definition exists prior to document import.

The document opens in WordPad. This is how you associate the programs you want to open certain types of files. Incorporated 38 Jun-10 . select Tools > Associations > Programs. bitmap files could use an Application named Image. checking the document in. Local overrides are maintained in the database. When defining application actions. Click OK to close the Program Associations dialog. When using Open With. From the available programs dialog. AutoCAD2007. This allows the user to track files by version rather than by extension. Double click Open. but all other users will continue to use Notepad. in \Folder A. make application names descriptive and use version names in the Application name. double click ProjectWise. rather than Adobe Photoshop. In ProjectWise Explorer. • • ProjectWise Explorer Best Practices Copyright © 2010 Bentley Systems. create multiple Applications in ProjectWise. the user would open the document using Open With.). MicroStation V8i. In this case. Notepad would be launched for any user who attempted to edit an html file. etc. all Open actions are presented in a list from which the user selects their favorite.html. the Description field is mandatory. You defined a local override of the global open action. etc. After the exercise. Prior to performing the exercise. for example. For multi-purpose files (tif. 8 Hint: • • When possible. on a per-user basis. Notepad was previously defined as the Open action for files associated with html. rather than Open. Select User Associations from the Select an association view option menu. the current user will use WordPad to open html files.ProjectWise Applications You could allow the user to override the global action or define multiple open actions for the application. MicroStationJ. txt. Example: MicroStationV8i. When working with multiple versions of applications. 3 4 5 6 7 Locate and expand the HTML application (from a previous exercise). For instance. Exit WordPad. select WordPad Document and click OK. jpg. This value is presented to the user when Open With is selected. use generic Application names.  Exercise: Defining local overrides for application actions 1 2 Continuing in ProjectWise Explorer.

An extension can only be mapped to a single Application. Action item definitions provide a field for entering additional command line parameters. This can be useful for passing such information as AutoCAD profiles. When defining ProjectWise applications. Incorporated 39 ProjectWise Explorer Best Practices . users see the name twice in their datasource list and won’t be able to tell them apart. whether global or user level. Module Review Now that you have completed this module. While not demonstrated in this module. it attempts to discover any ProjectWise Servers on the network by sending out a broadcast on the network.Module Review • • • • Extensions are only used during file import operations. What port is used? If you fail to specify a display name when creating a datasource. let’s measure what you have learned. what is an action association? 2 3 4 5 6 Jun-10 Copyright © 2010 Bentley Systems. What is the purpose of the ProjectWise V8i Network Configuration Settings dialog? True or False: If two users are sharing a client system. Each user should have a unique working directory. what do users see when they log in to ProjectWise Explorer? True or False: If two servers use the same display name. they should not share working directories. is maintained in the ProjectWise datasource. Questions 1 When ProjectWise Explorer launches. All Application configuration information.

Incorporated 40 Jun-10 .Module Review ProjectWise Explorer Best Practices Copyright © 2010 Bentley Systems.

An account uniquely identifies them. and forms the basis for assigning privileges and user preferences. Incorporated Managing User Accounts . you will be able to: • • • Understand and create different account types Define user properties settings Manage users Jun-10 41 Copyright © 2010 Bentley Systems. Document and folder access is based on the user’s ID. each user needs an account. This module discusses the set up of user accounts. including all the options available.Managing User Accounts Module Overview In order to access ProjectWise. Module Prerequisites • • Knowledge about ProjectWise Explorer’s interface Knowledge about document architecture Module Objectives After completing this module. All user preference information is stored in the database and is associated with the user’s ID.

let's define what you already know. the user that is logged in to ProjectWise Explorer is the owner of new files and folders. consists of a unique log in name and password. Each user account. If you use a description. in the New User Properties dialog. and various user properties settings and privileges. what do users see when they log in to ProjectWise Explorer? By default. When you create a user account. Incorporated 42 Jun-10 . regardless of the ProjectWise module from which they are connecting. Password. plus whether or not the user is currently connected to the datasource. it Managing User Accounts Copyright © 2010 Bentley Systems.Introductory Knowledge Introductory Knowledge Before you begin this module. Questions 1 2 3 What is an abstract document? If you fail to specify a display name when creating a datasource. and Security type. the account is active immediately and the user automatically receives a set of user properties settings and privileges based on the currently defined default user properties settings for that datasource. The Users list displays the general properties for each user. as is the E-Mail field. The datasource list is returned to the client in the format ServerName:DatasourceName. at a minimum. All user accounts for a datasource are listed under the Users icon in ProjectWise Administrator. User Accounts A ProjectWise user is a person with an account in the datasource. This includes the user Name. Users are created and maintained in the ProjectWise Administrator client application. Where do you change that? Answers 1 2 3 A document that has no file associated to it. Using the Manager option in the Process Bulkload File portion of the tool. All required user data is specified on the General tab. The Description field is optional.

without providing credentials. When a user has is logged in to the operating system using their Windows account they can log in to datasources in ProjectWise Explorer automatically. the system will automatically set the user’s password to their log in name. password verification. You can change the password for logical user accounts. To create these accounts. as user roles are determined by privileges and access rights. after entering the user name. • Windows synchronized accounts also use the user name and password from existing Windows domain or Active Directory accounts. Unlike regular Windows accounts. but are created using the user name and password credentials of an existing Windows domain account. description. Do not confuse account types with user roles. set the Type to Logical in the Security section of the General tab of the New User Properties dialog. Windows. or authentication. and then verify it. • Logical accounts are those whose user name and password are stored in the ProjectWise database. Account types refer to how the account is stored in ProjectWise and how the user logs in. and password. set the Type to Windows and then type the Windows domain to which the user belongs. a descriptions and an e-mail address if desired. using single sign on.Account Types will display in most user dialogs instead of the name. To create these accounts. Windows accounts are those whose user name and password are not stored in the ProjectWise database. the ProjectWise User Synchronization Service manages Windows synchronized accounts. along with their ID. Account Types There are Logical. The user name and password for a logical account are stored in the ProjectWise datasource. after entering the user name. is done by the operating system itself. Enter a password. An e-mail address is required only if you are sending system messages through an external e-mail system. name. Incorporated 43 Managing User Accounts . a descriptions and an e-mail address if desired. For Windows user accounts. This lets you disable users • Note: The “Account is disabled” option on the General tab lets you create users and Jun-10 Copyright © 2010 Bentley Systems. then decide whether they can access the datasource. Note: If you do not set a password. and Windows synchronized account types.

In this case. Assuming all information is correct. if they worked on the documents offline. Incorporated 44 Jun-10 . In this case. the user name and password are stored in the ProjectWise datasource. This is also handy if you Free someone’s documents. ProjectWise Integration Server. To understand how this is possible. their user name. because they do not have to maintain a separate ProjectWise password. However. they must contact an administrator before resuming work. Users start the log in process by entering the datasource name. user name. If the user account exists. Managing User Accounts Copyright © 2010 Bentley Systems. and finally their password. the password is not stored in the ProjectWise datasource. Authentication for Windows accounts With a Windows account. the user is logged in. it is necessary to discuss the ProjectWise authentication process and explain the transactions that occur between ProjectWise Explorer. users start the log in process by entering the datasource name.Account Types who are not active without deleting the account in case it is needed later. Enable this option for that user so that. They can be forewarned that their offline work will be overwritten by the server copy when they log in. and the datasource when a user attempts to log in. the password is compared against that stored in the database. the user name is stored in ProjectWise and the user is assigned a ProjectWise user ID. their domain server name. Authentication Using Windows accounts minimizes an administrator’s efforts to maintain user accounts. ProjectWise Integration Server checks the database to see if the user account exists in the specified database. and their password The remainder of the process is as follows: • • • • ProjectWise Explorer sends the credentials to ProjectWise Integration Server. Authentication for Logical accounts With a logical account. Users typically prefer Windows accounts as well.

along with the password entered by the user to the domain controller for validation. In a production environment. when the user changes their Windows password. modified. Further. The ProjectWise User Synchronization Service is not required for the Windows authentication process described to take place. ProjectWise stores the user’s domain security ID. ProjectWise needs to store the ID from the Windows user database corresponding to the user. The remainder of the process is as follows: • • • • • • ProjectWise Explorer sends the credentials to ProjectWise Integration Server. and notifies ProjectWise Integration server of their status. Rather than have another column in the table for this purpose. The Windows domain controller then checks the credentials. Assuming all information is correct. Using ProjectWise User Synchronization Service ProjectWise User Synchronization Service lets you create ProjectWise user accounts that use Windows domain or Active Directory accounts. ProjectWise Integration Server checks the database to see if the user account exists in the specified database. SID. or deleted accounts. Its purpose is simply to relieve the administrator from having to create a ProjectWise Windows account for each user in the Windows domain. It can be configured to synchronize accounts from the Windows domain to ProjectWise. though. ProjectWise then sends the SID retrieved from the database. you can use ProjectWise User Jun-10 Copyright © 2010 Bentley Systems. Once these ProjectWise user accounts are created. In this case. It does not mean that passwords are synchronized between the Windows domain and ProjectWise.Account Types You might expect that the password field in the database for this user would be empty. the Windows SID is retrieved from the database. they can log in to ProjectWise immediately using the new password. The term synchronize refers to monitoring the Windows domain for new. If the user account exists. Windows accounts are normally created automatically using the ProjectWise User Synchronization Service. ProjectWise allows the log in without ever storing the user’s password. the user is logged in. in the password field. Incorporated 45 Managing User Accounts .

Launch ProjectWise Administrator. but it does not have to be installed there. the ProjectWise User Synchronization Service Administrator and the ProjectWise User Synchronization Service Engine. how and when accounts will be synchronized. Both can be installed on the same system. install ProjectWise User Synchronization Service from the Server Setups. and then configure the User Synchronization Service. Then. they cannot log in to ProjectWise. Note: Note that if a user’s Windows account is disabled. Managing User Accounts Copyright © 2010 Bentley Systems. There are two folders in which all User Synchronization activity and status is displayed. even if synchronization has not been run. They are under the Windows Security System icon in ProjectWise Administrator. make sure the ProjectWise User Synchronization Service is started in the Services dialog. Note: The ProjectWise User Synchronization Service Administrator portion must be installed on a system where ProjectWise Administrator is installed. The User Synchronization Service folder contains a folder for Synchronized Accounts and one for Ignored Accounts. Identify the Windows accounts you want to synchronize and any accounts you want the User Synchronization Service to ignore.. Right click User Synchronization Service and select Properties to specify which User Synchronization Service installation to use.Account Types Synchronization Service to keep the accounts synchronized with any changes to their domain or Active Directory account. and is managed through the User Synchronization Service snap-in in ProjectWise Administrator. After installing. the administrative user account you want the User Synchronization Service to use. The ProjectWise User Synchronization Service Engine runs as a native Windows service. The ProjectWise User Synchronization Service has two parts. Run a synchronization. install ProjectWise Administrator.  How to install and run the User Synchronization Service: First. on the same system. Incorporated 46 Jun-10 . ProjectWise User Synchronization Service can be installed on the same system as ProjectWise Integration Server. log in to your datasource. or they can each be installed separately. Windows accounts are always validated against Windows. • • View the results of a synchronization in the Recent Synchronization Results folders.

To bypass this automatic log in a user can select Datasource > Log in as. open \ProjectWise\bin\dmskrnl. To enable single sign for a particular datasource. For single sign on to work in ProjectWise Administrator. Incorporated 47 Managing User Accounts . [db0] Description=pwclass01 InterfaceType=ODBC Name=pwclass01 Type=Microsoft SQL Server DBUserName=sa DBUserPassword=000056c80000df920002a28f00028e43 DBUsrPwdDecrypt=1 DBAdminUserName=sa DBAdminUserPassword=000056c80000df920002a28f00028e43 DBAdmPwdDecrypt=1 SSO=1 It is not necessary to restart the ProjectWise Integration Server service for this change to take effect. etc. Single Sign On When single sign on is enabled for a datasource. and who is currently logged in to the operating system as that user. which begins with [dbo]. Single sign on is disabled by default for all datasources on an Integration Server. [db1]. Jun-10 Copyright © 2010 Bentley Systems. the user with a Windows account must also be a member of the Administrator group. a user with a Windows account in a datasource.cfg and type SSO=1 at the end of the section containing settings specific to that datasource. can double-click a datasource in ProjectWise Explorer and be automatically logged in without being prompted for a user name and password.Account Types and how the User Synchronization Service will handle ProjectWise accounts that cannot be synchronized with their respective Windows accounts.

enter the following: Name: user1 Description: Logical user 1 Type: Logical Password/Verify Password: Your choice Note: Note that when no password is specified. 3 Managing User Accounts Copyright © 2010 Bentley Systems. identify the latest version first so ProjectWise loads its . Note: For single sign on to work when using ProjectWise Administrator. When using multiple versions of an Oracle database. it is set to the same value as the user name. You will see the message “Cannot log in to the datasource”. a user must also be a member of the Administrator group. In the New User Properties dialog. Log in using the user1 credentials.  Exercise: Test the new user with ProjectWise Administrator 1 2 Log out of ProjectWise Administrator. A document is owned by the user whose ID is 5. rather than the user whose name is John. Incorporated 48 Jun-10 . The user name may change. but the user ID remains constant. each user in ProjectWise receives a unique ID that won’t be duplicated. right click on Users in the console tree and select New > User. For more information. Click OK. User IDs Similar to document and folders.  Exercise: Creating a new user 1 2 Logged in to ProjectWise Administrator with the administrative credentials. The new user is created using logical security. 3 Click OK.dll first. see the on-line Help topic Enabling / Disabling Single Sign On for a Datasource.Account Types Hint: There can be a [dbo#] section for as many databases as you are using.

The administrator should define important settings for the user and. not allow them to change them. you should configure the Default user’s settings to the needs of a specific project or your organization. User Properties Settings Use the user Properties dialog’s Settings tab to change user properties and privileges to something other than the default. A first layer of security to prevent unauthorized administrators is simply to not install the ProjectWise Administrator application on users’ systems. In the Select Working Directory dialog. If a user does gain access to the Administrator application.  Exercise: Test the new user with ProjectWise Explorer 1 2 3 4 Minimize ProjectWise Administrator. Taking the time to get the default user’s settings correct in the beginning saves you work in the future. Highlight the folder and click the New Folder icon. A new sub-folder appears. expand My Computer and navigate to a folder where you would like to create user1’s working directory. but no additional settings were specified. The working directory is one such setting. A ProjectWise administrator grants administrative rights to other users by including them in the Administrator group. Log in to ProjectWise Explorer using the user1 credentials. Incorporated 49 Managing User Accounts . Name the new folder user1 and click OK to close the dialog. Remember that when you create a Jun-10 Copyright © 2010 Bentley Systems. Before creating many users. in most cases. 5 The new user account is successfully created. You saw this when you logged in for the first time and were prompted to select or create a working directory. they still cannot log in unless they have administrative rights. All other settings are inherited from the default user. only the minimum required fields were populated.User Properties Settings 4 Log out and log back in using the administrative credentials. When you created this user.

Note: Be sure that you select Users in the console tree to configure the default 2 Double click on Working Directory to expand it and display the available settings.User Properties Settings new user. Default user properties  Exercise: Review the user settings 1 In ProjectWise Administrator. right click on Users in the console tree and select Properties. and it always appears first in the list. the category is available for the user to change from ProjectWise Explorer. To define the default user. Create this user first with the settings appropriate for most users. You can refer to this information as you further define user properties settings. other users’ properties can be adjusted for their role. Settings categories The following information is presented as a reference. they inherit settings from the default user. Managing User Accounts Copyright © 2010 Bentley Systems. not a user name in the list view. If disabled. After creation. The first item listed is “Allow user to change working directory”. the category will not appear in ProjectWise Explorer. If enabled. open the Users Properties dialog from the Users item in the console tree. Each category has a similar setting. Incorporated 50 Jun-10 . user.

below the specified path. select the folder icon. ProjectWise provides access to system variables that let items like user names be specified in the default user properties settings. Highlight the directory you want to set as the working directory and click OK. a user can select or change their working directory in ProjectWise Explorer after selecting Tools > Options. after logging in.User Properties Settings Working directory category The working directory is the local directory on the user’s system that ProjectWise uses to store copies of files while they are edited or viewed. When you are setting a default working directory for the user in ProjectWise Administrator. When using ProjectWise Explorer In ProjectWise Administrator. If the ProjectWise Explorer working directory is not defined here. you need to expand this setting. this same setting can be used by the user to change the location of their working directory. These settings control the location of that working directory. Allow user to change working directory category When enabled. then the user will be prompted to either create it or change it. the first time they log in to this datasource in ProjectWise Explorer. An easy way to accomplish this is to include the user name in the working directory path. When un-checked. then the user will be prompted to define their own location for it upon log in. Incorporated 51 Managing User Accounts . Path selection Double click the icon to open a navigation dialog. this setting is used to preset the user's working directory when using ProjectWise Explorer. It is mandatory that each user have a distinct working directory. In ProjectWise Explorer. ProjectWise will recreate the storage area structure as required. select the Jun-10 Copyright © 2010 Bentley Systems. the user cannot modify the assigned directory. Hint: It is usually best to disable this setting so there is no confusion for users and no data loss. If you define the ProjectWise Explorer working directory here.

then the user will simply be prompted to select another location for the working directory. You can enter plain text. To include the user name in the path. C:\pw-wrkdir\$USER. case sensitive. A suggested standard for working directory names is as follows. Incorporated 52 Jun-10 . or both.Descr$ . When accessing ProjectWise over the web Used to preset the user's working directory when using ProjectWise Web Parts. The value you enter should specify the path to and including the folder name you want the user to use. You can use any or all of the following variables to help create a unique working directory folder name for your users: • • • $User. then your user number would be 5 If multiple datasources are in use.User Properties Settings little thing to the right of it (an empty text field). it is also a good idea to include the datasource name or abbreviation in the working directory path. Then you can set what you want the user's default ProjectWise Explorer working directory to be. The user can always change the location of their working directory by selecting Tools > Working Directory from the Content web part. Note that if you specify a drive that does not exist on the user's computer.Name$ . however. if you were the fifth user to be created in the datasource. a variable. and wait for the field to become editable. changing the location of the working directory from Web Parts does not change the value set for this user Managing User Accounts Copyright © 2010 Bentley Systems. For example. then the user will be prompted to set their own working directory upon logging in. C:\pw-wrkdir\datasourcename\username Hint: This standard is for multiple datasources as well as multiple users on a single client system.the user's number in the datasource. The user's working directory will be created automatically on their computer when they first log in to the datasource through ProjectWise Web Parts. If it cannot be created in the specified location for any reason. user1’s working directory would have been defined automatically as C:\pwclass01-wrkdir\user1. As each new user is created.the user's description $User$ .the user's ProjectWise username $User. to the end of the path.NAME$. add the string $USER.NAME$ Had this setting been in effect. their user name is substituted for the string in the working directory setting.

this variable will be expanded to the user's local folder that stores the data for local applications. For example. then select it again and wait for it to become editable.the user's ProjectWise username • • General category This category provides control of folder and document security for a user. the default Web Parts working directory for every user is set to: %LocalAppData%\Bentley\ProjectWise Web Parts\Working Directories\%Datasource% To change a user's default Web Parts working directory. Allow user to change general settings When enabled.name]\AppData\Local %Datasource% . ProjectWise Explorer displays the General settings category in the Tools > Options dialog for this user. the user cannot see the General settings category. You can enter plain text. a variable. The user can modify these settings. Note that if you specify a drive that does not exist on the user's computer. or both.the name of the datasource the user is logging in to %User% . You can use any or all of the following variables to help create a unique working directory folder name for your users: • %LocalAppData% . but then uses Web Parts from another computer. the working directory on the new computer will be created based on the value set for the user setting in ProjectWise Administrator. The value you enter should specify the path to and including the folder name you want the user to use. select the default location displayed. If the user changes their working directory using Tools > Working Directory from the Content web part. Incorporated 53 Managing User Accounts .User Properties Settings setting in the datasource. In a new datasource. expand this setting. on Windows Vista this would expand to C:\Users\[user. When disabled. Jun-10 Copyright © 2010 Bentley Systems. then the user will simply be prompted to select another location for the working directory.

an existing pre-V8 XM Edition job will not run until the user whose credentials are stored in that job likewise has the User Credential Expiration Policy setting set to No Expiration. If the user properties setting General -> Allow user to change general settings is also enabled. so that jobs in which their credentials are stored can connect to ProjectWise Integration Server and run through without being disconnected. open the user Properties dialog in ProjectWise Administrator and disable the Use Access Control setting. In the User Credential Expiration Policy dialog that opens. in which the user's connection will expire. select one of the options from the option list. once logged in. you may find that a folder has become invisible. To change the default setting. Hint: As an administrator testing and configuring security. Log back in to ProjectWise Explorer and you will see the folder again. When disabled. once the user logs in to ProjectWise. • • Use access control This setting controls how folder and document security affects a user.User Properties Settings User Credential Expiration Policy This setting allows administrators to control when a client's or service's connection to the ProjectWise Integration Server expires. the user can change their default setting for this item after they log in to a datasource in ProjectWise Explorer. the user is immune to access control and will therefore have access to all files and folders. connection does not expire until the user logs out. when you click OK. the UserLoginTokenTimeout setting in the dmskrnl. • Server Default means that. No Expiration means that once the user logs in. Distribution Service and Automation Service users must have their User Credential Expiration Policy setting set to No Expiration in order to create new jobs.cfg file on the ProjectWise Integration Server's system controls the time limit in which the user's connection will expire. If you set Custom Value but do not enter a time limit. double click User Credential Expiration Policy to display the default setting below it. Double click the default setting. in hours. the setting will automatically be set to No Expiration. Enable “Use access control” for the majority of users. In addition. and only enable “Allow user to change general settings” for users with full administrative access rights. Selecting Custom Value prompts you to enter a time limit. If you cannot see a folder. This option is for ProjectWise Distribution Service and ProjectWise Automation Service users. Incorporated 54 Jun-10 . Managing User Accounts Copyright © 2010 Bentley Systems.

Users can either make a previous become the active document or to delete a previous version. users can change the User Interface settings. the user can access ProjectWise from ProjectWise Explorer and ProjectWise Web Server as usual. if you allow this. the Edit button displays in the New Document Version dialog. It is a good idea to give users the ability to modify these settings. Hint: Enable this so that users can control their own interface. users can add documents to or remove documents from existing flat document sets. However. users have access to all settings in the category. if they try to access ProjectWise from ProjectWise Explorer or from a regular ProjectWise Web Server. Incorporated 55 Managing User Accounts . the user can only connect to ProjectWise through the ProjectWise Web View Server. User Interface category The User Interface category is a group of items that users typically prefer to control themselves. Jun-10 Copyright © 2010 Bentley Systems. Edit versions When enabled. they will not be permitted to log in. and also the ProjectWise Web View Server if desired. Allow user to change User Interface settings When enabled.User Properties Settings User can only log in through Web View Server When on. Edit Sets When enabled. When this setting is off.

the dialog does not appear even if the setting is enabled. Hint: Many administrators prefer to present an obvious error message to users. If enabled. Local Document Organizer will only open when you log out of a datasource from ProjectWise Explorer. Managing User Accounts Copyright © 2010 Bentley Systems. Clicking it shows the same error information as the dialog. If you enable Show in ProjectWise Explorer only. whether you are in ProjectWise Explorer or an integrated application. If there are no documents checked out. Show Selective Set Open dialog This setting gives the user control over the Check Out/Open process when using MicroStation or AutoCAD reference files. The user can also define whether selected references are Copied or Checked Out. If the setting is disabled. but an Information button displays in ProjectWise Explorer’s status bar. the Local Document Organizer will open when you log out of a datasource. If you do. This dialog allows the user to select which references in the set to open along with the parent document. Show progress indicator during file transfers If enabled. the progress of the file transfer displays whenever documents are being moved. the Selective Set Open dialog opens when the user opens the parent document of a logical set.User Properties Settings Show Dialog On Error If enabled. Users are prompted to check in all documents. The user can then use the Organizer dialog to Check In documents before finally logging out. there is no dialog. such as Iras\B. If disabled. Hint: Enable this setting when you are working with applications that edit reference files directly. Users will need to check out the raster reference files so that Iras\B can edit them. an error message dialog displays in ProjectWise Explorer whenever users encounter an error. Incorporated 56 Jun-10 . all references are copied out when the user opens the parent document of a logical set. you can enable Show dialog on error for the default user. Show Local Document Organizer on Logout If Show always is enabled.

If the shortcut uses a URN link. URL links find the item using the item's datasource path. if a description exists for a document or folder. you will see the datasource path. If the shortcut uses a URL link. Uniform Resource Name.User Properties Settings Display descriptions When enabled. Uniform Resource Locator. Jun-10 Copyright © 2010 Bentley Systems. There is no reason to display this tab in the document properties dialog unless File Property Extraction is enabled for the datasource. URN links find the item in the datasource using the item's GUID. link. the File Properties tab displays on the document properties dialog. you will see the item's GUID. the description displays in place of the document or folder name in ProjectWise Explorer. This feature provides the ability to index ProjectWise documents using attributes stored on the Windows file system. Use URN links Enable this setting so that dragging a document or folder from ProjectWise Explorer onto the desktop creates a shortcut using a URN. link is created. Hint: Think about your project structure and naming conventions before enabling this setting. the datasource opens to the folder that was active when the user last logged out of the datasource. This tab shows Windows file properties for the selected document. When this setting is off. Show file properties If enabled. Right click and open the shortcut's Properties dialog and look at the Target field on the Shortcut tab to see the link type. a URL. Select last used folder If enabled. Incorporated 57 Managing User Accounts . Note: Windows file properties are an optional feature that must be enabled from ProjectWise Administrator.

the document properties dialog opens to the same page that was active when it was closed. Managing User Accounts Copyright © 2010 Bentley Systems. a default image displays. Select Last Used Attribute Page If enabled. There is no reason to display this item unless Full Text Indexing is enabled for the datasource. it removes the ability to exit the dialog without saving changes. Attribute Form Save changes without confirmation If enabled. They also appear in integrated applications’ document selection dialogs. This feature provides the ability to view documents in the preview pane prior to opening the document.User Properties Settings Show document thumbnail If enabled. If a user selects New > Document. Incorporated 58 Jun-10 . Note: Full Text Search is an optional feature that must be enabled from ProjectWise Administrator. This feature is used to search the datasource for documents containing the specified text. If there is no thumbnail image. Note: Document thumbnails are an optional feature that must be enabled from ProjectWise Administrator. Another side effect of enabling this setting is encountered when creating new documents. Useful for administrators who often check security settings or the audit trail. users are prompted to save any changes. There is no reason to display this item unless Thumbnail Extraction is enabled for the datasource. extracted thumbnail images display in the preview pane when a document is selected in ProjectWise Explorer. uses No Wizard. Note: While this might seem like a desirable behavior. It provides the ability to search for documents based on text within the documents. partially fills out the form. then closes without saving. If disabled. the new document is saved anyway. Useful for users who must fill in attributes. users won’t be prompted to save changes made from the document properties dialog. All changes are saved. Show full text search If enabled. ProjectWise Explorer displays the Full Text tab on the Search by Form dialog.

For this to work. when those users are attempting to log in with their Windows domain account. When enabled. you must also go to the system on which ProjectWise Web Server Components for Web Parts is installed and specify that the user is the delegate user. Administrative category Allow user to change administrative settings If this setting is enabled for a user other than the administrator. It simulates single sign on for users using Web Parts. the Search by Form dialog opens to the General tab.User Properties Settings Search Form Initially open attributes page If enabled. this setting does not display. Jun-10 Copyright © 2010 Bentley Systems. they can modify the settings in this category. it authorizes the user to request passwords for other users connecting to a datasource from a Web Part. the Attributes tab displays when users open the Search by Form dialog. and they’re logged in to ProjectWise Administrator. Datasource Usage of Recycle Bin Enable this to use the recycle bin to hold items deleted from the datasource. Incorporated 59 Managing User Accounts . If not. Enable as delegate user This setting is for use with ProjectWise Web Server Components for Web Parts. If the user is the administrator.

the user can create. or other Bentley software. once logged in to a datasource in ProjectWise Explorer or ProjectWise Administrator. The SELECT Server that the client is activating through can be configured by using the License Management Tool that is delivered with ProjectWise Explorer \ProjectWise\bin\licensetool. and can only see the name and description of storage areas. Incorporated 60 Jun-10 . the user can’t see the location of storage areas. Client Licensing This setting lets the administrator specify how license usage is activated and recorded for each user.exe. the ProjectWise client will activate and log its usage to the SELECT Server that the computer on which the ProjectWise client is installed is configured to use. or modify storage areas for the datasource. See all properties When enabled. Network category Note that the Network settings for an individual user only work if the respective Network setting was enabled globally in the datasource. MicroStation. Managing User Accounts Copyright © 2010 Bentley Systems.User Properties Settings Storage Area Create/Delete/Modify When enabled. the ProjectWise client will activate and log its usage to the SELECT Server that the ProjectWise Integration Server is configured to use. When disabled. the user can see all properties of all storage areas in the datasource. delete. Activate and record usage through client's configured SELECT Server When enabled. Activate and record usage through connected Integration Server When enabled.

Enable Delta File Transfer Enabling this setting enables delta file transfer for this user. Hint: Performance improvements will be most noticeable with large amounts of data. by only sending the changes needed to update the file. Note: Delta file transfer improves performance when sending large files over networks with high latency or low bandwidth connections. rather than the entire file. Allow user to change client/server network settings When enabled. Jun-10 Copyright © 2010 Bentley Systems. the datasource setting of the same name must also be turned on.User Properties Settings This is in the Network category on the Settings tab of the datasource Properties dialog. Note: Data compression improves performance over networks with high latency or low bandwidth connections by compressing the data that is being sent to or retrieved from the ProjectWise database. Compress client/server request data This user properties setting enables data compression for the user. which enables delta file transfer for all ProjectWise Explorer clients connected to this datasource. you also need to enable the datasource settings of the same name. For data compression to work. the user can change the default settings set for them under the Network category. such as thousands of documents in a folder. The data is decompressed when it reaches its destination. which enables data compression for all ProjectWise Explorer and Administrator clients connected to this datasource. For delta file transfer to work for this user. Document category These settings control a user’s interactions with documents in ProjectWise Explorer. Incorporated 61 Managing User Accounts .

or when Delete is disabled. Hint: If Modify is enabled and Delete is disabled. users cannot delete documents. or copy them to other folders.User Properties Settings Hint: These settings act as a first level of security. When disabled. Delete When Delete and Modify are both enabled. users can create documents and also move and copy them to other folders. they cannot create documents. Allow User to Change Document Settings When enabled. Modify When enabled. all documents become read-only. regardless of the user’s read/write privileges and the user can neither modify nor delete documents. users can modify documents and their attributes. the user can change the default settings set for them under the Document category. Create When enabled. When Delete is disabled. the user cannot move documents to other folders. move them. users can delete documents. When disabled. you can have the right to modify without having delete rights. Managing User Accounts Copyright © 2010 Bentley Systems. If Document -> Create is disabled. users cannot create documents anywhere in the datasource. When Delete is enabled but Modify is disabled. Incorporated 62 Jun-10 . even in folders where they have full control.

Checked in documents are saved to the server before being delete locally. then they cannot move documents because move is a copy/delete command combination. Hint: If a user cannot delete documents. Free When on. If enabled. the user can change the Workflow State of documents. Remove Final Status When enabled. Jun-10 Copyright © 2010 Bentley Systems. Find this command on the Document > New menu. the New Version command is available. so there is no reason to save them to the recycle bin. the Delete command is available in the main Document menu and in the document list pop-up menu. Use Recycle Bin on Free This setting only applies to freed documents. The user can set the final status of a document. the Set Final Status command is available in the Document > Change State menu. the user can remove final status for a document. Change State When enabled. freed documents are stored in the user’s Windows recycle bin. Create Version When enabled.User Properties Settings When enabled. If this setting is disabled. Incorporated 63 Managing User Accounts . Find this command on the Document > Change State menu. It is context sensitive and will only be active after the user has selected a document that has been set to final status. When disabled. Set Final Status When enabled. changes made to a freed document cannot be recovered because the document is not saved to the server or the local recycle bin. the delete setting is inactive. the user can free documents they have checked out or exported.

and a local document copy exists. even if a local copy exists. Use up to date copy on copy out If enabled. Use up to date copy on check out If enabled. Incorporated 64 Jun-10 . the local document copy (in the user’s working directory) is not deleted. the copy of the document in the user's working directory is retained when the document is freed by choosing Document > Free in ProjectWise Explorer. If a local document copy does not exist. the document is always retrieved from the server. or from an integrated application. and reduce network traffic. the local document copy is used when check out is performed in the case where the local copy is found to be up to date. When a user frees a document from the Organizer dialog. Leave this on so delta file transfer sends only necessary information. the local document copy is used when copy out is performed. When a user checks in a document from the Organizer dialog. by default documents are deleted from the user’s working directory after the file has been successfully verified on the server. This holds true when the document is checked in from either ProjectWise Explorer. the action the user selects overrides the setting here for Leave local copy on free.User Properties Settings Leave local copy on check in During check in. When this setting is enabled. Managing User Accounts Copyright © 2010 Bentley Systems. it is retrieved from the server regardless of the how this is set. Leave local copy on free When enabled. the action they select overrides the setting here for Leave local copy on check in. When this setting is disabled. it is retrieved from the server regardless of the State of this setting. but retained to build a local cache of frequently accessed documents. Hint: This setting can be used to improve performance and reduce network traffic. If a local document copy does not exist. in the case where the local copy is found to be up to date. and a local document copy exists. Hint: This setting can be used to increase performance.

etc. even if a local copy exists. Document List category These settings control the behavior of the document list view within ProjectWise Explorer. Save As. Show subfolders This setting lets ProjectWise Explorer emulate Windows Explorer by showing folders. the document is always retrieved from the server. canceling the ProjectWise dialog results in the application opening its own dialog. Hint: This setting can be used to increase performance. the user can turn on or off the Shareable setting for any V8 DGN document they have access to. users can change settings for the Document List. users working in ProjectWise-integrated applications can only access ProjectWise folders and documents. in the documents view. and can only save the open file back to ProjectWise.User Properties Settings When this setting is disabled. This is enforced by modifying all file access dialogs (File > Open.) to present their ProjectWise equivalent. Incorporated 65 Managing User Accounts . This setting is disabled if document sharing is not enabled at the datasource level in ProjectWise Administrator. Modify shareable flag When on. as well as documents. Jun-10 Copyright © 2010 Bentley Systems. thereby allowing the user access to non-ProjectWise documents. through the document properties dialog in ProjectWise Explorer. Allow user to change document list settings When enabled. Use captive environment When enabled. they return to the application. The document list is on the right side of the application. and reduce network traffic. If the user selects Cancel. When disabled.

Managing User Accounts Copyright © 2010 Bentley Systems. Hint: This setting may be useful when working with a large database. Select the action that double click should initiate in the ProjectWise Explorer. if a user checks out a number of documents. and users must manually refresh the application window by choosing Refresh from the View menu or pressing F5. Refresh display These settings determine when the contents of the application window are refreshed. During Operation If enabled. The default is to check out and open the document. Incorporated 66 Jun-10 .User Properties Settings Hint: In order for this setting to be useful. their status and icon do not change in the document list until all documents are checked out. the application window refreshes after each item in the operation is processed. this setting disables the automatic refresh of ProjectWise windows. By Command If enabled. users should display Name as the first column in the view. After Operation If enabled. Showing sub-folders and not showing them Double Click Action Double click on Double click action and a selection list appears. For example. if the user checks out a number of documents. the application window refreshes after the entire operation on the documents is complete. For example. the status and icon of each one changes in the document list as each document is checked out. as removing automatic refresh results in a faster response.

the user cannot create folders. The user can have modify rights without delete rights. Folder category These settings control the user’s interactions with folders in the ProjectWise Explorer. Incorporated 67 Managing User Accounts . the user can modify folders. Modify When enabled. tooltips are displayed when the user's mouse hovers over individual cells in ProjectWise Explorer's document list. Jun-10 Copyright © 2010 Bentley Systems. When disabled. only the latest version of a document displays.User Properties Settings Show Tooltips When enabled. if Modify is enabled and Delete is disabled. all versions of a document are displayed in the document list. folder privileges. When off. Allow user to change folder settings When enabled. this user can change the settings for the folders. Create When enabled. the Create command is available to the user in the Folder menu or in the datasource’s console tree pop-up menu. Hint: The absence of Modify rights prevents the user from deleting folders as well as modifying them. When disabled. For example. the user cannot modify or delete folders. they can change the Workflow/State. Show all versions When enabled.

users cannot delete folders. or to change the Workflow State of documents in the folder. Hint: This setting is useful to hide the folder structure from users. Managing User Accounts Copyright © 2010 Bentley Systems. Hide folder hierarchy in user interface When enabled. the Delete command is available in the main Folder menu and in the datasource console tree pop-up menu. Access to this tab enables the user to select a different Workflow to apply to the folder. Queries will still retrieve the documents to which users have access. When disabled. Change Workflow / State When enabled. you should also disable the Delete setting in the Document category. When Delete is enabled and Modify is enabled. and when the Modify setting for folders is enabled. To make sure that the user does not accidentally delete documents. Hint: Disabling Delete for folders does not prevent the deletion of documents within the folder. these settings are inactive. users can delete folders. or when Delete is disabled. the Documents folder and all of the folders in the datasource are not displayed. When disabled the folders display normally. Message Folders category This category contains the settings that control user access to the internal ProjectWise messaging system. the Workflow & State tab displays in the Folder Properties dialog. When Delete is enabled and Modify is disabled. Incorporated 68 Jun-10 .User Properties Settings Delete When enabled. but the structure containing them will not be available.

sent through ProjectWise Messenger. the user can delete Global folders. Access items When enabled. This appears as an additional item in the console tree. Delete When Delete is enabled and Modify is enabled. Move When enabled. Disable message polling Turn this setting on only if you do not want ProjectWise Explorer to automatically check to see if you have a new message from another ProjectWise user. the user can change their default settings for the Message folders category. however. the user can create Global folders. the Global Folder displays in the console tree. ProjectWise Explorer displays the Global Folders folder. Show message folders in user interface When enabled. Modify When enabled. or when Delete is disabled. Incorporated 69 Managing User Accounts . the user can modify Global folders. they can have modify rights without delete rights if Modify is enabled and Delete is disabled. Jun-10 Copyright © 2010 Bentley Systems. the user cannot delete Global folders. Hint: Disabling Modify prevents users from deleting Global folders as well as modifying them. Create When enabled. the user can drag and drop a personal folder to a new location within the Message folder. When Delete is enabled and Modify is disabled.User Properties Settings Allow user to change message folders settings When enabled. Inbox and Sent items for this user.

the Create command is available in the Folder menu and in the console tree pop-up menu. Other user’s folders are the private folders of other users. Managing User Accounts Copyright © 2010 Bentley Systems. Global folders are set up for all users to access.User Properties Settings Modify items When enabled. There are settings that expand when you double click these items. and the Private. However. Allow user to change custom folder settings When enabled. Global and Other user’s folders Private folders are the user’s own private file structure. a user can change the settings for Custom folders. ProjectWise Explorer displays Custom folders as an additional item in the console tree for the user. Hint: These types of folders are useful for simplifying complicated folder structures. This allows users to create new personal folders. Custom Folders category This category contains the settings that control the users own custom folders. the user can add items to and remove items from the Global folders. or another user’s folder is selected in the console tree. which can be thought of as favorites. they are deleting the actual folder or document. Global. Private. users must be aware that if they delete something here. Create When enabled. Show custom folders in user interface When enabled. Incorporated 70 Jun-10 .

Delete When enabled. or Another Users Hierarchies folder is selected in the console tree. Global Hierarchies. and a folder previously created in the Private Hierarchies.. If the drag and drop method is used and the user tries to move a Personal folder to the Global Hierarchies folder. When disabled. Global Hierarchies.. the folder can be moved.. using drag and drop to an alternative position within the Private Hierarchies.. the Delete setting does not display and the user cannot delete a folder. Add new items When enabled.. or Another Users Hierarchies folder is selected in the console tree.. and a folder previously created in the Private Hierarchies.. Add Document. users cannot modify the properties of a folder. indicating that the user has insufficient privileges to complete the action if Delete is pressed. an error message displays. the Properties of the folder may be modified by selecting Properties from the Folder menu or the datasource console pane pop-up menu. and a folder previously created in the Private Hierarchies. When disabled. the folder is copied. Global Hierarchies. and a Personal folder previously created in the Private Hierarchies Folder is selected in the console tree. or to a user in the Hierarchies of other Users folder.User Properties Settings Modify When enabled.. not moved. Add URL. or Another Users Hierarchies folder. Jun-10 Copyright © 2010 Bentley Systems. commands display in the Folder menu. Move When enabled. An error message displays. Incorporated 71 Managing User Accounts . or Another Users Hierarchies folder is selected in the console tree. When disabled. The user must have sufficient privileges in the target folder. the Delete command is available in the Folder menu and in the console tree popup menu allowing users to delete the folder. the Add Folder. and in the console tree pop-up menu allowing the user to add items to and remove items from the personal folders. Global Hierarchies. indicating that the user has insufficient privileges to complete the action.

Allow user to change global user list settings When enabled. See Items When enabled. the user can create. the Global Hierarchies or other users private hierarchies folders display in the Custom Hierarchies folder for this user. Delete access user list When enabled. Create.User Properties Settings When disabled. the folders do not display. Modify. the user can create. Global user lists category User lists are a method of grouping users. Modify. Create. Incorporated 72 Jun-10 . Delete address book list When enabled. Address book lists are used by the ProjectWise internal messaging system. the user can change the default settings set for them under the Global user lists category. An error message displays. When disabled. Access user lists allow security to be assigned using user lists. modify or delete items in the address book in ProjectWise Messenger. the settings do not display and the user cannot add or remove items. modify or delete users from an access user list. indicating that the User has insufficient privileges to complete the action if the drag and drop method is used to add an item. Managing User Accounts Copyright © 2010 Bentley Systems.

Jun-10 Copyright © 2010 Bentley Systems. a user can change the settings for the Default Action.User Properties Settings Document Creation Conflicts category This group of settings control how ProjectWise reacts if an attempt is made to overwrite an existing document. such as a user importing/copying a document to a folder already containing a document with the same document and/or file name. Document Creation Conflicts settings are divided into three categories. Default Action These settings control the default action when a duplicate is encountered. They may also occur when a user imports a file into ProjectWise without using the New Document Wizard. Action Skip a document: When enabled. Incorporated 73 Managing User Accounts . if documents are to be imported/copied and a version of one of the documents exists in the target folder. Each of these items expands to display additional settings when double clicked. Document creation conflicts can occur when a user moves or copies a document within ProjectWise Explorer. When a document creation conflict occurs. the import/copy of the particular document is skipped. Allow user to change default action settings When enabled. this rule is invoked by the name duplication.

When disabled. Default Version Rules These settings are used when Create a new version is selected as the default action when a duplicate is found. or a number of documents. a suffix. a new document is created using the selected Document Creation Rules settings i. For instance. the user can select options for the new document version. They give options for the action to be taken when a document creation conflict occurs and the option to create a new version is selected. Create a new document: When enabled. if a single document. the Select an action dialog does not display. Do not show select an action dialog When enabled. the selected rule applies only to the current document and the user is prompted for a decision about every duplicate found. or a number of documents. or change the name.e. this user can change the settings for Default version rules. Managing User Accounts Copyright © 2010 Bentley Systems. if the Define Version Rules dialog displays. are to be imported/copied and a version of one of the documents exists in the target folder. Incorporated 74 Jun-10 . The old file still exists as the older version. if a single document. a new version of the particular document is created. The user is offered a choice regarding how to handle first duplicate found. are to be imported or copied and a version of one of the documents exists in the target folder.User Properties Settings Create a new version: When enabled. if multiple documents are being copied/imported/moved at one time the previously selected rules apply to all documents. This will apply to subsequent duplicates. Apply common rules for the whole document selection When enabled. and the actions selected by the administrator are automatically carried out. Allow user to change default version rules When enabled. add a prefix.

02. Then add the fixed text to the Version String Format line. if a new version of the particular document is to be created. the document name of the source document is used for the new document version. Remove target document attributes When enabled. The version string will read 01. Set Width to 2. if a new version of the particular document is to be created. the target document’s attribute sheets are removed from the new document version.. if a new version of the particular document is to be created.  How to set a two digit whole number as the version number: First. given the following version string format. Enable Filled with leading zeros. select Decimal number. For example. Jun-10 Copyright © 2010 Bentley Systems.User Properties Settings Version string format Double clicking this item opens a dialog where you may specify a format string for the version that is automatically created. from the Type list. follow the preceding steps. or click the browse button and the Define Format dialog appears. 02a. You can enter the format that you want to use. In this dialog. Apply document name of the source document When enabled. you can define the variable to be used when a version needs to be created. If you wanted to have particular text or number as part of your version. and then click OK. the source document’s attribute sheets are added to the new document version. Incorporated 75 Managing User Accounts . 03. 03a. Apply source document attributes When enabled. the version string will read 01a..

Every document in a folder must have a unique document and file name. the file name of the source document is used for the new document version. Default Document Creation Rules These settings are used when Create a new document is selected as the default action.) selected by the administrator are automatically carried out. the name of the document must to be changed. if a new document is created using the Create a Document dialog. Managing User Accounts Copyright © 2010 Bentley Systems. if a new version of the particular document is to be created. etc. Incorporated 76 Jun-10 . Change name: When enabled. a user can change the settings for Default Document Creation Rules. Allow user to change default document rules When enabled. if a new document is to be created using the Create a Document dialog. Every document in a folder must have a unique document and file name. users can add a prefix to the current name of the document. Add prefix to the old name: When enabled. Do not show Define version rules dialog When enabled.User Properties Settings Apply file name of the source document When enabled. Document name format rule Double clicking on this opens additional settings. They give various options about the action to be taken when a document creation conflict occurs and the option to create a new document is selected. the Define version rules dialog does not display and the actions (apply file name of the source document.

For example. Name Format Double click to open a field where you can access the Enter Format dialog. if a new document is created using the Create a Document dialog. add a prefix to the old name. which are the same as those for the Document name format rule. which works the same as the Version String Format dialog. Jun-10 Copyright © 2010 Bentley Systems. Every document in a folder must have a unique document and file name. the Define document rules dialog does not display. Transfer source document attributes: When enabled. Do not show define document rules dialog: When enabled. File Name format rule Double clicking will open additional settings. Double click the first one to open a field where you can access the Enter Format dialog. users may add a suffix to the current name of the document.User Properties Settings Add suffix to the old name: When enabled. if a new document is to be created using the Create a Document dialog. Incorporated 77 Managing User Accounts . and the actions selected by the administrator are carried out. any environment attributes are copied from the source document to the new document. which works the same as the Version String Format dialog. File name format Double clicking will open additional settings.

this group of settings controls individual user rights with respect to the ProjectWise Audit Trail. Managing User Accounts Copyright © 2010 Bentley Systems. Incorporated 78 Jun-10 . this user can change the settings for the Audit Trail. See actions of other users When enabled. This functionality is found on the Users tab of the Audit Trail Customize Report dialog in ProjectWise Explorer. In addition to the master settings. See private actions When enabled. the user can include other users’ actions in the Audit Trail report. Reports Allow user to change report visibility settings When enabled. allowing the user to determine which reports will display. Comments Allow user to change comment settings When enabled.User Properties Settings Audit Trail category Audit trail replaces the history function that existed in previous versions of ProjectWise. Allow user to change audit trail options When enabled. the user can change the settings for Comment usage. the user can include the user’s own actions in the Audit Trail report. the Reports item displays under the Audit Trail category.

users are prompted to enter comments when changing the State of documents. Delete Rights Allow user to change delete rights settings When enabled. the user can change the settings for Delete Rights. the user will not be allowed to carry out the action without entering comments.User Properties Settings Allow comments for check in When enabled. The Clear Audit Trail item is added to the Folder and Document menus for that user. Allow comments for version create When enabled. Require comment When enabled. users are prompted to enter comments when creating new versions of documents. Incorporated 79 Managing User Accounts . Can delete audit trail records When enabled. Show Audit Trail tab in Document Properties window When enabled. users are prompted to enter comments when setting final status on documents. the user can delete audit trail records from the database. Jun-10 Copyright © 2010 Bentley Systems. When disabled. users are prompted to enter comments when checking in or importing documents. users cannot enter comments when checking in or importing documents. Allow comments for final status change When enabled. the Audit Trail tab displays in the document properties dialog. Allow comments for state change When enabled.

Show datasource level Managed Workspace Profile option The Workspace tab of the Folder or document properties dialog has Managed and Workspace Profile options for Workspace Type. fail on error. Export relative path errors handling You can choose to prompt the user. only the Workspace Profile setting is available. the Personal Workspace tab displays on the user Properties dialog in ProjectWise Explorer. the Audit Trail tab displays in the Folder Properties dialog. Allow user to change export error handling The user can change the default settings for the Export relative path errors handling setting. Show Personal Managed Workspace Profile page When enabled.User Properties Settings Show Audit Trail tab in Folder Properties window When enabled. When this setting is disabled. Managed Workspace Profiles category Allow user to change Managed Workspace Profile settings The user can change the default settings set for them under the Managed Workspace Profiles category. Can edit Personal Managed Workspace Profile variables A user can edit personal managed workspace profile variables. or ignore invalid relative path errors. Managing User Accounts Copyright © 2010 Bentley Systems. This does not include the Export relative path errors handling option. Incorporated 80 Jun-10 .

Establishing the Default user  Exercise: Define the default user 1 In ProjectWise Administrator.NAME$ 2 In the User Interface category. make sure the following are set.User Properties Settings Project permissions category Allow user to change project permissions The user can change the default settings for Project Permissions. set the Working directory as follows: Allow users to change the directory Make the path when using ProjectWise Explorer: C:\pw-wrkdir\pwclass\$USER. and leave all defaults as is: Jun-10 Copyright © 2010 Bentley Systems. Allow user to delete projects The user can delete projects in ProjectWise Explorer. on the Settings tab of the Properties dialog for the default user. Allow user to change project types and project properties The user can change a project's project type. Allow user to create projects and upgrade folders to projects The user can create projects by selecting Folder > New Project. Incorporated 81 Managing User Accounts . and also modify a project's properties. and can turn a regular folder into a project by selecting the folder and selecting Folder > Upgrade to Project.

User Properties Settings Show dialog on error: Enabled Select last used folder: Enabled 3 In the Document List category. Uncheck “Allow user to change working directory” and click OK. and leave all defaults as is: Show message folder in user interface: Enabled In the Custom Folders category. Click Apply. make sure the following is set. make sure the following is set. right click user1 in the list view and select Properties. and leave all defaults as is: Show subfolders: Enabled In the Message Folders category. 2 3 4 Select the Settings tab in the Properties dialog. set the Action to Create a new version and then enable Do not show ‘Select an action’ dialog. Incorporated 82 Jun-10 . and then OK. make sure the following is set and leave all defaults as is: Show custom folders in user interface: Enabled In the Document Creation Conflicts category. Default Action section. Managing User Accounts Copyright © 2010 Bentley Systems. 4 5 6 7 Modifying user properties  Exercise: Modify user1’s properties 1 In ProjectWise Administrator. Double click the Working Directory category.

The new account has been created and added to the Administrator group. In the dialog that opens. Click OK to finish creating the new account. Jun-10 Copyright © 2010 Bentley Systems. and then click OK. Incorporated 83 Managing User Accounts . Log out of ProjectWise Administrator. and then click Select. This user can access the ProjectWise Administrator application and perform all tasks with the exceptions listed previously. select a group or user list. Select the Member Of tab. On the General tab. Use the keyboard Ctrl or Shift keys to select multiple user names in the list view. User groups and lists are discussed later in the module. select the Administrator group. enter the following: Name: admin2 Description: Secondary administrator Type: Logical Password/Verify Password: admin2/admin2 3 4 5 6 Select the Settings tab and make sure that they can change their working directory.  Exercise: Testing the secondary administrator account 1 Log in to ProjectWise Administrator using the secondary administrative user credentials. All of the users who are members of that group or user list are automatically selected in the Users list. click Add. You can also select all the users that belong to a particular group or user list by right clicking the Users icon and selecting Select Users by Groups / Lists.Secondary Administrative Accounts Modifying properties for multiple users You can modify the properties for several users in a single operation. Secondary Administrative Accounts  Exercise: Creating a secondary administrative account 1 2 Continuing in ProjectWise Administrator. right click Users in the console tree and select New > User.

but permanent. Deleting Users Deleting a user account is a simple. the user ID will never be reused. even secondary administrative rights should be limited to trusted individuals. Minimize ProjectWise Administrator.  Exercise: Adding documents using the new account 1 2 3 4 Log in to ProjectWise Explorer as the test1 user. Incorporated 84 Jun-10 . The secondary administrator account can perform most administrative functions. Managing User Accounts Copyright © 2010 Bentley Systems. let’s add several documents to the datasource using the test1 account. Once deleted. On the General tab. When a user account is deleted. any documents owned by that user ID are transferred to the ID of the user performing the delete operation. Even recreating a user by the same name will not restore the user. This would even include creating additional administrators. enter the following: Name: test1 Description: test1 user Type: Logical Password/Confirm Password: test1/test1 4 5 Click OK. navigate to the \Test1 folder in the class data set. drag the sub-folders from that folder into the new ProjectWise folder. Accept working directory creation. Before doing so. the user ID is not returned to the available pool. When a user account is deleted. so it is impossible to create another user with the same ID. operation. In Windows Explorer.Deleting Users 2 3 Right click Users in the console tree and select New > User. a user account cannot be restored. In the following exercise. For this reason. Remember that document ownership is based on user ID’s. Remember that the constant item for user accounts is the user ID. In other words. Create a new root level folder named Test1. and drop them. the test1 user is to be deleted.

Important: In a production environment. it can be passed to the user’s supervisor to determine the best way to handle the files. Select Users in the console tree. Click OK to close the user Properties dialog. ProjectWise provides search capabilities that enable the administrator to produce a list of all the files owned by a given user. Once the list has been generated. it is a good idea to find out how many documents this user owns before proceeding. Exercise: Deleting the test1 user 1 2 3 Return to ProjectWise Administrator. 8 9  Close the document properties dialog. Enable the Account is disabled check box. Select the file D-border. All documents take on their ownership from the user that originally created them.dgn. This includes document import operations such as drag and drop. Double click the user test1 to open the user Properties dialog. right click. 4 5 6 7 Select No so the user test1 is not deleted. Note: When a user is deleted. This prevents the user from logging in while you decide how to process the files they own. Jun-10 Copyright © 2010 Bentley Systems. User test1 owns the document. the user is also deleted from all groups to which the user is a member. should this user own any files. Test1 also owns the ansi and iso folders. you will take ownership of those files since the user is deleted. You receive a message indicating that. Select the Security tab. Incorporated 85 Managing User Accounts . Unlike deleting the account. Log out of ProjectWise Explorer. where you are logged in as the secondary administrator. this action can be undone if necessary.Deleting Users 5 6 7 Navigate to the ProjectWise folder \Test1\ansi. and select Properties. Right click the user test1 in the list view and select Delete to delete the user.

txt.Deleting Users  Exercise: Identify the files owned by test1 1 2 3 Log in to ProjectWise Explorer using the secondary administrator’s credentials (admin2/admin2). Deleting the Administrative user The primary administrator account has special privileges and you cannot delete this account. The Search by Form dialog appears. Document ownership is determined by the Created By field. 11 Select Yes to delete the user and take ownership of any documents still owned by that user. Launch Notepad and paste the list into it. Incorporated 86 Jun-10 . You want to locate the field for document ownership. Accept working directory creation. that user cannot be deleted. 4 5 6 7 8 Set Created By to test1. right click the user test1 in the list view. Log out of ProjectWise Explorer. Click the arrow next to the Advanced Search icon in the Search toolbar at the top of ProjectWise Explorer and select Search Form. Secondary administrators can be deleted. save the document as test1docs. 9 10 Return to ProjectWise Administrator. if there is only one user in an administrator group. You are now ready to delete the test1 user. Managing User Accounts Copyright © 2010 Bentley Systems. Right click in the document list and select Copy List to > Clipboard Tab Separated. Click Close to dismiss the Search by Form dialog. However. and select Delete. Now you have a record of the files. Click OK to start the search. and exit Notepad.

The Groups icon contains all of the user groups that exist in your datasource. both administrative and end user. When an empty database is made available for use by ProjectWise. nor will it be able to create storage areas. the primary administrator can grant these privileges to the secondary administrator using the Administrative category within user Properties dialog. From this account. Group. This category is only accessible from the ProjectWise Administrator. and all settings are ultimately associated with this item. This method is typically used to delegate certain administrative responsibilities to other users. A Group is simply a collection of users. User groups Similar to Windows. The user ID is the only constant. Once a user is a member of the Administrator group. and user preferences are all associated with the user account. Take an existing user account and add it to the Administrator group to create an administrator account. In addition. the New Datasource Wizard creates ProjectWise tables in the specified database. and cannot contain other groups. This account is the primary administrator account and is treated specially by ProjectWise. you may create additional accounts. security can be established at the User. If necessary. Any user given access to this application can create. security settings. modify. and delete user accounts. It will always have a user ID of 1. or User List level. and will have all privileges. secondary. and contains the administrative user account you named during Jun-10 Copyright © 2010 Bentley Systems. it creates the Administrator account and the Administrator group. Two exceptions are that the new. the Administrator group is created by default. Incorporated 87 Managing User Accounts . ProjectWise Groups are created to contain users who have the same access requirements. Document ownership.Group and List Membership Group and List Membership User accounts provide a unique ID for each user and are the primary building blocks of the system. When the datasource is first created. administrator account cannot affect the server’s use of the recycle bin. User account maintenance is accomplished using ProjectWise Administrator. A user cannot log in to the ProjectWise Administrator unless they belong to the Administrator group. they can log in to the ProjectWise Administrator and perform most administrative functions. As you will learn in the chapter on Folder and Document Security.

specify the domain to which the Windows group account belongs. Set the Type to Windows. Then. Incorporated 88 Jun-10 . click Apply. be sure to add the descriptions so they are in the database for future use. You can create a group in the datasource to group together users who need the same access rights to folders and documents. type a unique name for the new group.  Exercise: Add additional users Note: The following users and groups are used in other modules. Then. You can also add a user to a group by opening the Properties dialog for a given user. Click Apply. Hint: To minimize the effort spent administering ProjectWise.  How to create a user group using the credentials of a Windows group account: First. identify the users and then click OK. set the Type to Logical. create the group.Group and List Membership datasource creation. and then OK.  How to create a logical user group: First. In the Select Users dialog. Then. Hint: The existence of user groups also makes it easier when creating access lists and mailing lists Establishing groups is a two step process. so they must be created. right click the Groups icon and select New > Group. click Add.  How to add users to a group: First. Managing User Accounts Copyright © 2010 Bentley Systems. First. Enter the following for the new user. 1 2 3 In ProjectWise Administrator. For this class. o n the Members tab of the Group Properties dialog. On the General tab of the New Group Properties dialog. Click Apply. in ProjectWise Administrator. and then add users to the group. right click the Groups icon in the console tree and select New > Group. and then OK. type the name of the Windows group account. and then selecting the desired group. right click a group in the list view and select Properties. In the Windows domain field. log in using the primary administrative credentials. assign security to groups instead of individuals. selecting the Member Of tab. In the console tree. right click Users and select New > User. and then OK.

In the Select Users dialog. Create the following two users: Name: Engineer Description: Engineer Name: Project Manager Description: Project Manager 6  Make sure these users have the right to change their working directory. enter the group name Design. right click and select Delete. Right click on Groups in the console tree. select New > Group. Select the Members tab. select the name in the document view and click the Delete key or. and select New > Group. Exercise: Create User Groups 1 2 3 4 5 6 Right click on Groups in the console tree. Jun-10 Copyright © 2010 Bentley Systems. right click and select Properties. and then click OK to exit both dialogs. Changes are made in the <groupname> Properties dialog. On the General tab.Group and List Membership Name: Drafter Description: Drafter 4 5 Click OK to create the user and close the dialog. and create a groups as follows: Group: Management Member: Project Manager Modifying Groups Select the group name in the document view. Deleting Groups To delete a group. Incorporated 89 Managing User Accounts . add the users Drafter and Engineer. Click Add.

 Exercise: Create an Access User List 1 2 Right click on User Lists in the console tree and select New > User List. Description and Type are established. the User List Name. User lists can contain any combination of users. Groups. Mailing User Lists are used for the ProjectWise internal messaging system. You can filter either using the List items of type option at the top of the dialog. and other User Lists who need the same Access rights to folders. etc. and then click OK to exit both dialogs: Management (group) admin (user) Note: The icons [preceeding names show whether the item is a user (single head) or a group (double heads). type the following: Name: Project5900 Description: Project 5900 members 3 4 5 Select the Members tab. making them more flexible. and User Lists) are added to the List. Incorporated 90 Jun-10 . and even other user lists. On the General tab of the New User List Properties dialog. documents. Second.Group and List Membership User Lists User Lists are similar to Groups. Managing User Accounts Copyright © 2010 Bentley Systems. Creating a User List is a two part process. Groups. add the following Members. Deleting and modifying User Lists User Lists are modified and deleted by selecting the User List in the list view. Where Groups can contain only users. In the Select Security Objects dialog. groups. similar to creating a Group. Click Add. as they are logical groupings of entities within ProjectWise. the relevant members (Users. There are two types of user lists. First. • • Access User Lists are used to group together Users. then right clicking and selecting Properties to modify or Delete to delete.

csv files. Then.The Database User Account Selecting users by group or list This option in ProjectWise Administrator lets you identify and select all the users that belong to a particular group or user list. Jun-10 Copyright © 2010 Bentley Systems. Next. select whether to see. If the user name or password for the database user account changes. groups. Note: Click the Export icon at the top of the Select Users by Groups / Lists dialog to export lists to . click the Select button at the bottom of the dialog.  How to see which users are in a group or user list: First. in the Select Users by Groups / Lists dialog. you need to change those credentials in ProjectWise Administrator. right click the Users icon and select Select Users by Groups / Lists. The Database User Account The database user account is determined during creation of the datasource.txt or . There are options in the dialog that let you look for only those users who are connected or only those whose accounts are enabled. The users in the group or user list are highlighted in the right pane of the ProjectWise Administrator. lists or both. and is used by the ProjectWise Integration Server to connect to the database. Incorporated 91 Managing User Accounts .

What is the difference between a logical account and a Windows account? With a Windows account. let’s measure what you have learned. click Apply. the password field in the database is not empty. Which user properties setting is useful to hide the folder structure from users? Queries will still retrieve the documents to which users have access.Module Review  How to update the database user account: First. What can you do to minimize the effort spent administering ProjectWise security? 4 5 6 7 8 Managing User Accounts Copyright © 2010 Bentley Systems. however. the password is not stored in the ProjectWise datasource. change the credential that you want to update. Incorporated 92 Jun-10 . Module Review Now that you have completed this module. Then. but the structure containing them will not be available. open the datasource Properties dialog and select the Database Users tab. Questions 1 2 3 Define a ProjectWise user. What is stored there? Why is it important to define a default user? What can you do if a folder becomes invisible to you while you are configuring security? True or False: Moving documents is a copy/delete command combination. and then click OK.

Incorporated Environments . This module discusses creating and applying environments.Environments Module Overview An environment contains custom attributes that users can apply to documents. you will be able to: • • • • • • • Define and work with environments Create interfaces Modify property column properties Create attribute sheets Define document codes Understand settings in the Attributes Properties Dialog Adjust environment and attribute user properties settings Jun-10 93 Copyright © 2010 Bentley Systems. Module Prerequisites • • • Knowledge about ProjectWise Explorer’s interface Knowledge about document architecture Knowledge about user accounts Module Objectives After completing this module.

If you select a parent folder. These items include properties such as Document Owner (created by). organization specific. Changing an assigned environment is not recommended. and Department. to designate an environment. let's define what you already know. or recommended. This framework is referred to as an environment. it is not necessary. Incorporated 94 Jun-10 . you should not designate an environment for the files you are importing into it. Application. They are standard. An environment is a collection of supplemental. Hide folder hierarchy in user interface. True. These items are used internally by ProjectWise. when searching for documents. and cannot be modified. ProjectWise provides a framework for extending the default list of attributes. 3 Environment Overview ProjectWise provides a number of standard properties that you can use to classify documents. it will already have an environment assigned to it. Which user properties setting is useful to hide the folder structure from users? Answers 1 2 These tabs are the user’s means of accessing extended document metadata. File Name. Questions 1 2 3 What are the Attributes and More Attributes tabs in the document properties dialog? True or False: When you import files into an existing folder. To provide more flexibility. as well as by users. In this case. document Environments Copyright © 2010 Bentley Systems.Introductory Knowledge Introductory Knowledge Before you begin this module.

Documents at the root of those folders or projects will have blank Attributes and More Attributes tabs in their Document Properties dialog. Document code restrictions. Incorporated 95 Environments . in ProjectWise Explorer you can assign the <none> value for environments to any folder or project. It may be best to only have one interface. Attributes can be searched. The fields in an environment table are called attributes. rather than adding additional columns to the built-in ProjectWise document table. Defining Environments There are four main steps to complete when setting up an environment. each environment is stored in its own table. Environments are not a required feature of a datasource. If you want. The environment can also be called a table or schema. There are several terms used in conjunction with environments: • • • The attribute itself. which is the layout of the attributes. Jun-10 Copyright © 2010 Bentley Systems. and then apply to folders and projects in ProjectWise Explorer. Each column in the row is an attribute. Users can populate attribute fields interactively or they can be populated automatically. or metadata. Think of an environment as a table with a row in it for each document that uses the environment. This way the default ProjectWise table structure is fixed. and the custom fields are stored in a separate table. AutoCAD. and it is specified at the time a folder is created. Each folder can have a different environment assigned to it. or attributed fields. or metadata. for classification that are defined by the environment. and can be displayed in specified fields in their respective documents. and Microsoft Office. meaning one arrangement of attributes. Since the environment provides a means of extending the default fields that are stored for each document. They can also be used by MicroStation. letting you quickly retrieve specific documents. which are a combination of custom attributes which uniquely identify documents within an environment. All documents placed in the folder will have additional items.Defining Environments attributes that you establish in the datasource in ProjectWise Administrator. An interface.

or you can create some during creation and create the rest later. right click Environments in the console tree. 3. Click Next and on the Finishing New Environment page. enable “An environment that defines attributes for documents”. an interface. type the name MyCivil. enabling the Common Environment option means that this environment is the default environment that will be used whenever a folder is created in ProjectWise Explorer if no other environment is specified. Only one environment can be the common environment. Incorporated 96 Jun-10 . A wizard takes you through the creation process. You can change these options after the environment is created in the environment's properties dialog. New interfaces are automatically added to each existing environment. select the desired table. If Create attribute records upon document creation is enabled. If disabled. Create the environment. On the Choosing environment type page. Create an interface. enable “Use existing table”. attributes are created when the first one is entered. and then click Next.  How to Create an environment using existing database tables: In ProjectWise Administrator. and arrange them in. 4. Add attributes. select New > Environment. and then click Next. and then click Next in the wizard. Add attributes to. 2. Using existing database tables A customized table must exist in order to use an existing table when creating an environment. You can create environments using existing database tables or by creating new database tables. On the Naming the environment page. enter an optional description. Environments Copyright © 2010 Bentley Systems. You can create all of the attributes as part of the environment creation process. the attributes will be created when a document is created.Defining Environments 1. click Finish. and then click Next. On the Selecting database table page. On the Choosing environment settings page.

 Exercise: Creating a new column in the database 1 2 Continuing in the New Column Properties dialog. right click Environments in the console tree. the attributes must have the same data type. 5 Reusing names across environments This lets users search across environments by a single search condition when “Look in this environment only” is disabled in the search dialogs. and then click Next. type 11. Leave this diasabled 3 In the Length field. The table is automatically named for the environment.  Exercise: Create an environment using new database tables 1 2 3 4 In ProjectWise Administrator. On the Designing new table page. You cannot have dwg_no as INTEGER in one table and as CHAR in another table. select “An environment that defines attributes for documents”. When Use native data types is enabled. It also lets the values from different environments display in a single column in the search results. You cannot have chkd_by as VARCHAR2 in one table and as NVARCHAR2 in another table. select New > Environment.Defining Environments Using new database tables Each attribute you create corresponds to a column in the database. type the name dwg_no. and then click Next in the wizard. type the name Bldg. Jun-10 Copyright © 2010 Bentley Systems. however you can reuse an attribute name across multiple environments. enter an optional description. enable Create new table. select VARCHAR. Attribute names must be unique in an environment. When you want to reuse attribute names across multiple environments. On the Choosing environment type page. On the Selecting database table page. They must also have the same character set. the available types will reflect the kind of database the datasource is using. click Add to open the New Column Properties dialog. On the Naming the environment page. In the Data type section. and then click Next. Incorporated 97 Environments . and then click Next.

all support unicode characters and the length specified in each case represents the number of characters. Create more columns as follows. VARCHAR. 20 proj_no. The allowable maximum depends on the kind of database the datasource is using. click Finish. Environments Copyright © 2010 Bentley Systems. Expand the Bldg environment in the console tree and click Attributes. Note: VARCHAR and CHAR data types support unicode characters. On the Choosing environment settings page. 6 drw_date. 50 dwg_type. in most cases. The “Required” property can be set later to force a user to input a value. 50 field1. check the actual titleblock to see how many characters will fit in a particular section of the titleblock. VARCHAR. the length indicator can be in characters. CHAR. The wide character data types. just click Next. CHAR. Allow Nulls is enabled by default so that the field can be left blank. VARWCHAR and CHARW. 4 5 Click Add. clicking Add after each one: chkd_by. is in bytes. Incorporated 98 Jun-10 . except when the underlying database is SQL Server 2000. INTEGER 6 7 8 9 Click Close. and then click Next. Hint: If you will be using environment attributes with titleblocks (attribute exchange rules). Don’t disable it unless you are sure there will always be information populating this attribute. On the Finishing New Environment page. You see the columns you have added to the database. Depending on the value of the NLS_LENGTH_SEMENTICS parameter in Oracle 9i.Defining Environments This is the maximum number of characters that will be stored for the attribute. The length specifier.

Jun-10 Copyright © 2010 Bentley Systems. expand the Default Interface and click ‘Attributes’ tab.Interfaces Creating environments by importing script files You can export environments so they can be imported into another datasource using ProjectWise Administrator. navigate to the class data set. click Close. but cannot change it. In the Open dialog. and are used to arrange the display of some or all of the environment's attributes.  Exercise: Create another environment by importing 1 2 Right click Environments in the console tree and select Import. select pwclass. Incorporated 99 Environments . Interfaces are created separately from environments. When you export or import an environment. You can create multiple interfaces for the same environment. When multiple interfaces exist. 3 4 Interfaces An environment defines a list of attributes. When finished. You can display certain fields as read-only so that users can see a value. the attributes. Expand the new environment. You can display all the attributes in the environment. you select which attributes to display. users can select which interface to use as the active interface by choosing Interface from ProjectWise Explorer's Tools menu. When an interface has been set up for an environment. users in ProjectWise Explorer can see the attributes in that interface on the Attributes and More Attributes tabs of the Document Properties dialog. The message window shows the progress. and click Open. and any document codes are also processed. expand the Attribute layout item. You see the layout users will see on the Attributes tab in the document Properties dialog.aam. or only a subset. Creating an Interface During this process. interfaces with attribute page layouts. along with where and how to display them. each presenting a different attribute layout. An interface arranges the presentation of those attributes to the user.

expand the Attribute layout item for the Bldg environment. The next step is to define the interface. Environments Copyright © 2010 Bentley Systems. If multiple interfaces are required. You should try to avoid the situation where users have to switch interfaces frequently. This lets you define different interfaces for this particular environment if you want to do so. name the interface Bldg. it is best if they are intended for different classes of users. You will see ‘Attributes’ tab and ‘More Attributes’ tab folders. Click the ‘Attributes’ tab folder. You see a list of all available interfaces. In the New Interface Properties dialog. The interface is added.  Exercise: Create an interface 1 2 3 In ProjectWise Administrator. Incorporated 100 Jun-10 . Click Interfaces in the console tree. Different interfaces can show different attributes for different types of users. 2 Expand the Bldg item. You are ready to design the Attributes tab for the Bldg interface for the Bldg environment. right click Interfaces in the console tree and select New > Interface.Interfaces Hint: It may be cumbersome for users when multiple interfaces are implemented.  Exercise: Defining the interface for the Bldg environment 1 In the ProjectWise Administrator. and then click OK. You select the attributes from a particular environment that you want displayed in each interface. 3 4 Right click in the document view and select Add Attributes.

6 7 8 9 Click ‘More Attributes’ tab in the console tree. Right click in the list view and select Add Attributes. 4 In Windows Explorer. 5 6 7 8 Jun-10 Copyright © 2010 Bentley Systems. and dwg_type attributes and click OK to add them to the form. Minimize ProjectWise Administrator.Interfaces 5 Select the chkd_by. Incorporated 101 Environments . After reviewing the Attributes tab. navigate to the Site Design folder in the class data set. Set the active Interface to Bldg. and drop them. dwg_no. The interface is functional and can be tested in ProjectWise Explorer. using the Bldg environment. Select the Attributes tab. In ProjectWise Explorer. Each of the attributes can be moved by clicking on it and dragging. You see the attributes you added to the interface. drag the files from that folder into the new ProjectWise folder. In ProjectWise Explorer.  Exercise: Test the interface 1 2 3 Log in to ProjectWise Explorer using the administrative credentials. open the first document in the \Site Design folder’s properties dialog. You are graphically designing the form that will appear in the properties dialog on the Attributes tab. select the More Attributes tab. Close the Document Properties dialog. create a new root level folder named Site Design. You can resize by pulling the handles. Select the attribute field1 and click OK.

Click the input field to resize it so it is the same length as the label. others.). Labels and prompts There is a lot you can do to make an environment user friendly and to insure data consistency.Interfaces 9 Exit ProjectWise Explorer. Click the center handles to resize vertically. Use the check box on the Interface tab to hide an attribute if it will be used across environments and you want to see it in some but not in others. set the Label font to Arial Black and the Label font size to 10.  Exercise: Change the attribute label 1 2 3 In ProjectWise Administrator. Environments Copyright © 2010 Bentley Systems. Hint: Changing the font causes an attribute to appear different from the 4 5 Change the Label text from dwg_no to Drawing No: Click Apply. resizing the label horizontally. Hint: To use an & sign in the Label text field. Use this feature to indicate and important or required field. Incorporated 102 Jun-10 . You immediately see the changes. Double click the dwg_no attribute in the form on the right to open the properties dialog. and then click OK. Click the label and drag the right handle. enter two (Acme && Co. The following exercises explore options for refining the environment/ interface combination. On the Interface tab. select the Bldg environment’s ‘Attributes’ tab item for the Bldg Interface. = Acme & Co. 6 7 The Interface tab is only available on the Attribute Properties dialog when viewing the attribute's properties from within an interface.

Add the prompt: Select a name Select the Value tab. and then click Add to build the list of fixed values. change the Label text to Checked By:. you must configure the expanded size. and then click the text labels and input fields for the Drawing No: and dwg_type attributes. This list can be changed by manually editing the list in ProjectWise Administrator. Apply. and then click OK: Value: Site team Add these additional list items. change the Type from None to Fixed. In the Value list section at the bottom of the dialog. A fixed list implies that the list cannot be changed. Before it can be used.  Exercise: Build a pick-list 1 2 3 Double click the chkd_by attribute in the form to open the properties dialog.  Exercise: Modify the attribute’s appearance 1 2 Click in the form to release the attribute. and then OK to exit the dialogs. Handles will appear around them. you will build a pick-list from a fixed list of values you enter. Press the Ctrl key. On the Interface tab. Incorporated 103 Environments . Click the browse button to the right. Value: Engineering Value: Structural 4 5 6 7 8 9 Click OK. Enter the following.Interfaces Fixed pick-lists Next. The attribute now appears as a pick-list. Jun-10 Copyright © 2010 Bentley Systems.

click the Center Horizontally icon to move them over so you can expand the pick-list. Select the Attributes tab. Click it to see the order in which users will tab through the fields. • • You can use the Ctrl key or drag the pointer to multi-select items on the page. To the right side of the toolbar is the Tab Order icon. This item is the master item. Environments Copyright © 2010 Bentley Systems. the last set. will be bold. 7 8 Hints: Click in the form to release the attribute. When you use the tools. You can also shrink them using the handles. Minimize ProjectWise Administrator. You can move them using the arrow icons to the right so the order is logical. one set of handles. Open \Site Design\BSI300AE201-Elevations’ properties dialog. When you multi-select. If you want to hide labels. • •  Exercise: Test the modified attribute 1 2 3 Launch ProjectWise Explorer and log back in. 4 5 6 Click in the form to release the attributes. Click the Checked By pick list and select the bottom center handle. Incorporated 104 Jun-10 . you can remove the Label text on the Interface tab and just enter a space. Move these items to a blank corner of the page. Drag it down to the size you want the item to be when expanded. everything selected will move based on that item.Interfaces 3 In the Attribute Layout toolbar at the top.

Double click the dwg_type attribute to open the properties dialog. Using format strings Format strings can be used to force manually entered data to conform to a designated format. change Default value Type from None to Fixed. Select the Value tab. any data entered into the Type attribute field is forced to upper case. Exit ProjectWise Explorer. In the Format String field. type UpperCase. and then click Close. In the following example.Interfaces 4 5 6 7 Click the Checked By pick-list and select Site team. Select the Interface tab.  Exercise: Add a format string to an attribute 1 2 3 4 5 6 In ProjectWise Administrator. Click Save. it will be checked against the format string. Providing default values In many cases. Select the Editing tab. it is desirable to provide a default value for an attribute. Change the Label text to Enter Employee ID:. select the Bldg interface’s ‘Attributes’ tab. As the document metadata is saved. Double click field1 to open the properties dialog. Incorporated 105 Environments .  Exercise: Provide a default value for the size attribute 1 2 3 4 5 6 In ProjectWise Administrator. Jun-10 Copyright © 2010 Bentley Systems. Change the Label text to Drawing Type:. BSI300. Select the Interface tab. Type the Drawing No. and then OK. select the Bldg environment’s ‘More Attributes’ tab. At the top. 7 Click Apply.

Select the ‘More Attributes’ tab. Before testing this configuration. select the Bldg interface’s ‘More Attributes’ tab. and then click Close. Incorporated 106 Jun-10 . Click Save. Change Value list Type at the bottom of the dialog from None to Select. Dynamic pick-lists This exercise creates a dynamic pick-list using a query into the database. type Site. and then click Apply and OK. This document has not inherited the default value for drawing type. In the input field. 6 7 8 9 Click the forward button at the bottom of the dialog to see the next document in the folder. Select the Attributes tab. 10 Exit ProjectWise Explorer. Default values only affect new documents. Environments Copyright © 2010 Bentley Systems. Double click the field1 (label is Enter Employee ID) attribute to open the properties dialog. The case changes to upper case. Exercise: Test the modified attribute 1 2 3 4 5 Launch ProjectWise Explorer and log back in. Change Checked By to Site team. type eng285. make sure that all ProjectWise users have valid user descriptions. Select the Value tab.  Exercise: Add a dynamic pick-list 1 2 3 4 In ProjectWise Administrator. or existing documents that have not had any metadata entered.Interfaces 7 8  In the Default Value field. Minimize ProjectWise Administrator. Right click BSI300AE201-Elevations in the Site Design folder and open its properties dialog. Click Save.

Jun-10 Copyright © 2010 Bentley Systems.Interfaces 5 In the SQL SELECT Statement field. Exit ProjectWise Explorer. select the Bldg interface’s ‘Attributes’ tab. In this case. and then click Close. using the User Description. 6  Click Apply and OK. Select the ‘More Attributes’ tab. Exercise: Test the modified attribute 1 2 3 4 5 6 Launch ProjectWise Explorer and log back in. Triggered updates for environment attributes In the following exercises. The list will present a list of users. Add the drw_date and proj_no attributes to the ‘Attributes’ tab. Incorporated 107 Environments . the select statement populates a list by retrieving data from the ProjectWise users table. Expand the Enter Employee ID options and select the Engineer user. type: select o_userdesc from dms_user Some knowledge of the ProjectWise database tables is required to formulate SQL select statements. you configure other attributes. Right click BSI300AE201-Elevations in the \Site Design folder and open its properties dialog. rather than the User Name.  Exercise: Add attributes to the environment 1 2 In ProjectWise Administrator. Click Save.

Click browse. You cannot create required fields if any folders or documents in the datasource are already using the environment. To do this.  Exercise: Define a triggered update attribute 1 2 3 4 5 6 7 8 9 Double click drw_date attribute to open the properties dialog. and then click OK. Hint: Use this feature sparingly. you must use the Document Creation Wizard when creating new documents. the Drawn Date field will populate with the current date. Note: If using required fields. enable the Required setting on the General tab of the attribute’s Properties dialog. Click browse. Double click field1 to move it to the list of attributes that will trigger the Drawn Date field to update. you may want to force users to enter data into particular attribute fields. and click OK. Change the Label text to Drawn Date:. Select the Interface tab. The user does not have to populate a date field. Incorporated 108 Jun-10 . when a user opens a document’s properties dialog and selects a user ID on the ‘More Attributes’ tab. because entering data in required fields is time consuming for users. Required fields In some cases. Delete the files in the \Site Design folder Environments Copyright © 2010 Bentley Systems. In the Update field when area. Select the Value tab. Change the Update value Type in the center of the dialog from None to System variable. to the right of the radio button.  Exercise: Change folder properties 1 2 Launch ProjectWise Explorer and log in. select $DATE$.Interfaces This attribute will update in response to a system variable. Now. enable the “Specific Attribute(s) are updated” radio button. 10 Click Apply and OK.

double click the proj_no attribute to open the properties dialog. and then click Close. select No Wizard. the row is only created when a user enters data. With the folder selected. Enter a name in the Document Name field. On the General tab. In the current configuration. Click OK. Exit ProjectWise Explorer.  Exercise: Create new document with required attribute fields 1 2 3 4 5 6 7 Launch ProjectWise Explorer and log in. This is because the environment is currently set so that the row is not created when the document is created. In order to enforce the required field at document creation it is necessary to modify the environment itself so that the row is created as the document is created. enable the Required check box. The following exercise demonstrates that a required field can present a problem when creating new documents. and then click OK. click Save. You cannot create required fields if any folders or documents in the datasource are already using the environment. 4  Exit ProjectWise Explorer. Select the Interface tab and change the Label text to Project No:. Incorporated 109 Environments . Jun-10 Copyright © 2010 Bentley Systems. select Document > New > Document. In the Select a Wizard dialog. The new document was created without entering any data in the required field. Exercise: Create an attribute with a required field 1 2 3 In ProjectWise Administrator. Reassign the Bldg environment to the \Site Design folder.Interfaces 3 Change the folder’s properties so that it uses the Default Environment.

select Advanced Wizard.  Exercise: Creating new documents using the Advanced Document Creation Wizard 1 2 3 In ProjectWise Explorer. and then click Close. You receive a warning that the document cannot be created because there is no data in the required field. In the Select a Wizard dialog. an empty row is created in the environment table. not the interface beneath it. 7 8 Click OK to exit the dialogs. Now each time a document is created. Environments Copyright © 2010 Bentley Systems. With the Site Design folder selected. you can’t create documents without using the Advanced Document Creation Wizard. In the Select a Wizard dialog. 2 On the General tab of the Properties dialog. You are unable to save the document unless the required attribute has a value. You are unable to open the Attributes tab because the document has not been saved. 5 6 Click OK. This wizard collects all data before attempting to create the database records. Click OK. Incorporated 110 Jun-10 . select Document > New > Document. and then click OK.Interfaces  Exercise: Modify environment properties 1 In ProjectWise Administrator. This displays the properties of the environment itself. select Document > New > Document.  Exercise: Create a new document 1 2 3 4 Launch ProjectWise Explorer and log in. When using required fields. rather than attribute properties. Type a name in the Document Name field. right click the Bldg environment in the console tree and select Properties. Click No so the new document is not saved. enable “Create attribute records upon document creation”. and then click OK. select No Wizard. Select the Attributes tab. and then click Next. Be sure to right click on the environment itself. and then click Save.

As long as a required field is in effect. disable the Required check box. and then OK. select an employee ID. all new documents must be created using this wizard.  Exercise: Remove the required attribute 1 2 In ProjectWise Administrator. Incorporated 111 Environments . and then click Next. Enable “Use external file as a template” and click Browse. the attribute value can be edited by users even if a document is set to Final Status. 10 Click Next to accept the default document names. For the remainder of the module. you will remove the required setting for the attribute. Click Next. Click Apply. Jun-10 Copyright © 2010 Bentley Systems. Supply document attributes: Checked By: Site team Drawing No: BSI300 Project No: 300 9 Click Next. Modifying Property Column Properties Attribute properties display as columns in the list in ProjectWise Administrator. and then click Next. • If Editable if final is set to Yes. and click Open. open the properties dialog for the Project No attribute. 11 Click Next.Modifying Property Column Properties 4 5 6 7 8 Select the Site Design folder.dgn. select BSI300AE201Elevations. and then click Finish. Navigate to the class data set Site Design folder.

so the first step is to locate all folders that have the environment metadata associated to them. Incorporated 112 Jun-10 . You can use the Search by Form to find these folders in ProjectWise Explorer. If you modify the attribute in one place. Attribute Sheets When editing a document’s properties. you can right click on the environment in ProjectWise Administrator and select Delete. If set to Read-only. they cannot save their changes until they supply a value for this attribute. on the Attribute and More Attributes tab pages. the attribute value can be viewed but not edited. or to hide some of them from display. or from an interface of which it is a part. it must not be associated with any folders. To open an attribute's Properties dialog. the properties will be updated in the other. Once you have changed the folders environment association or otherwise addressed the problem. If Unique is set to Yes. You can modify the properties of an attribute from the Attributes list. there may be instances when you want to enter multiple values for the same attribute. Deleting Environments To delete an environment. You can do this by creating one or more attribute sheets for the selected document. the attribute value can be edited. when a user starts entering values for other environment attributes. If Access is set to Edit. double click the attribute or right click the attribute and select Properties.Deleting Environments • If Required is set to Yes. • • Note: To rearrange the order of these columns. right click anywhere in the Attributes list and select View > Customize. the value entered for this attribute cannot be entered for any other attribute in this environment. Environments Copyright © 2010 Bentley Systems.

If this is not the case. To delete an attribute sheet.Defining Document Codes Adding and removing attribute sheets You can add as many attribute sheets to a document as you require. Before you can add an attribute sheet. define the form of the code. Using this method. Multiple sheets list in the order in which they are created. you can build a multi-part code. Document > Attributes > Add Sheet will be disabled for the selected document. The code is seen in ProjectWise Explorer when a document is created using the Advanced wizard. so that each sheet can be directed towards a particular part of the document. which can be a combination of a number of attribute fields. You can also create a code that uses a single attribute to identify the document. without an icon. the document to which you are adding the sheet should have an environment row created in the environment table. Incorporated 113 Environments . You. Jun-10 Copyright © 2010 Bentley Systems. Click Save.  How to add an attribute sheet to a document: First. Repeat the procedure to create additional sheets. select a document in the document list and select Document > Attributes > Add Sheet. as administrator. below the selected document in the document list. you might add a sheet for each of the floors. For example. elevations and details of a house. Warning: If you select a sheet and select Document > Delete instead of Document > Attributes > Delete Sheet. Each sheet contains its own attribute data. Defining Document Codes Document codes uniquely identify documents within an environment. You can create a code by selecting existing attributes to create a serial number that defines the fields that are used to create a document code. The new sheet is created and appears. with characters used to separate the individual fields. Enter values on the Attributes tab or the More Attributes tab. and then Close. select the document in the document list and select Document > Attributes > Delete Sheet. you will delete both the original document and all the sheets attached to it.

Defining Document Codes

How to create a document code with a serial number: These steps define a document code that contains an engineering ID, the individual who drew the document and the drawing number. The document code will be stored in a placeholder attribute named doc_code. It will be used as a serial number that is applied every time a user creates document code for a document. First, expand the Environments icon, right click the desired environment, and select Define Document Code. Click Next in the Document Code Definition Wizard. On the “Choosing document code type” page, enable “Yes, I would like to define a serial number for this environment”, and then click Next. On the “Defining serial number context” page, move any attributes that you want to be used as the serial number to the right side of the dialog, and then click Next.

On the “Defining serial number” page, select the first attribute to be used in the serial number, and then click Next.

On the “Selecting other code parts” page, add any other attributes you want to be used as the serial number, and then click Next. To define a placeholder, on the “Defining placeholder” page, enable “Yes, use the following attribute to store generated document code”, select an attribute from the list, and then click Next. This attribute will store the product of the

Environments

Copyright © 2010 Bentley Systems, Incorporated

114

Jun-10

Defining Document Codes

combined attributes you select to define the serial number. If the selected item has no attribute field name in the environment table, you could use one of the extra fields, extra_a, extra_b, extra_c, or extra_d. If not, enable “No, I do not intend to use a placeholder”, and then click Next.

On the “Defining additional attributes” page, move any additional attributes you would like to include in the document code to the right, and then click Next.

On the “Defining code formatting” page, set the attributes’ order, and the symbol to use to connect them. A preview displays in the lower right. Enable allow empty value so users can leave any of the document code fields that are not automatically generated empty. Then click Next, and then Finish.

How to create a document code with no serial number definition: First, launch the wizard and, on the “Choosing document code type” page, enable “No, I do not intend to use a serial number for this environment”, and then click Next. You will see the “Selecting other code parts” page. Now follow the previous instructions for creating a document code using a serial number, using the “Selecting other code parts”, “Defining additional attributes”, “Defining additional attributes”, and “Defining code formatting” pages.

Jun-10

Copyright © 2010 Bentley Systems, Incorporated

115

Environments

Defining Document Codes

Setting up document code restrictions
In addition to defining which fields are used to create a document code, you can apply restrictions to the code. These are either allow or forbid restrictions.

Allow and forbid restrictions
• • An Allowed restriction limits users to a range of code numbers, which you, the administrator, have defined. A Forbidden restriction prevents users from using a designated range of code numbers. You can designate a number of allow restrictions and a number of forbid restrictions within these allowed ranges. For example, if the document code consisted of the office code GBR, a project code (EP1, EP2, etc.), a serial number and perhaps a sheet number, you might create: Allowed restrictions for GBR - EP1 # 0001 - 1000 and GBR - EP2 # 1001 - 2000 These would restrict document codes to numbers within the range 1 - 1000 for documents relating to the Project EP1, and 1001 - 2000 for documents relating to the Project EP2. All document codes would start with the office code GBR, and no document codes would be allowed outside these two ranges.

How to apply this type of Allow restriction: First, expand an environment, right click the Document code restrictions icon and select New > Restriction. In the New Restriction Properties dialog, type a unique description for the restriction. Set Restriction type to Allowed. Then, in the “Attributes that define the document code context” section, enter values for the attributes. In this example, GBR in the office_code attribute field and EP1 in the project_code attribute field. In the Lower and Upper range fields, type 0001 and 1000, respectively. Click Apply, and then OK.

If you wanted to reserve the codes GBR - EP1 #500 to #750 for another part of the organization, you could apply a forbid restriction to these codes. Users would then only be able to use the codes GBR - EP1#0001 to #499 and #751 to #1000 or any numbers in the GBR - EP2 range of document codes and could therefore make appropriate reservations if required.

Environments

Copyright © 2010 Bentley Systems, Incorporated

116

Jun-10

Defining Document Codes

How to apply this type of Forbidden restriction: First, expand an environment, right click the Document code restrictions icon and select New > Restriction. In the New Restriction Properties dialog, type a unique description for the restriction. Set Restriction type to Forbidden. Then, in the “Attributes that define the document code context” section, enter values for the attributes. In this example, GBR in the office_code attribute field and EP1 in the project_code attribute field. In the Lower and Upper range fields, type 500 and 750, respectively.

Reserved restrictions
Restrictions can only be applied and removed by the administrator in ProjectWise Administrator, but users can reserve document codes. Any user can apply or remove these reservations, so reserved document codes cannot be reused until the reservation is removed. This might be done when a user is expecting certain documents to be submitted by a subcontractor. The user could reserve a range of document code numbers for those documents, remove the reservation when they arrive, and apply the codes to the documents. Reserved numbers must be within the ranges made available by the administrator in ProjectWise Administrator, allowing for any allow or forbid restrictions that have been applied. Following the example, you might want to add a document code restriction relating to office GBR and project EP1, in which the range 900 to 1000 is reserved for a specific use.

How to apply a reserved restriction: First, expand an environment, right click the Document code restrictions icon and select New > Restriction. In the New Restriction Properties dialog, type a unique description for the restriction. Set Restriction type to Reserved. Then, in the “Attributes that define the document code context” section, enter values for the attributes. In this example, GBR in the office_code attribute field and EP1 in the project_code attribute field. In the Lower and Upper range fields, type 900 and 1000, respectively.

Jun-10

Copyright © 2010 Bentley Systems, Incorporated

117

Environments

Searching for Documents by Environment Attributes

Searching for Documents by Environment Attributes
You can search for documents based on any environment attribute value. To find documents that have no attribute records, in the Search Builder, specify NULL for attribute value and “find in this environment only” criteria. To find documents that have empty string attributes, specify ' ' in a value field. To find both NULL (non-existing) and empty attributes you will have to use two OR groups on the same search.

How to search for documents based on environment attribute values: First, in ProjectWise Explorer, open the Search by Form dialog. Then, select the tab, Attributes or More Attributes, that contains the attribute value against which you want to search. Set or enter the value to search for in the appropriate available fields. Click OK or Apply.

You can also enter custom expressions in these fields. Simplified expressions are always interpreted by the set of rules, and are transformed to fully qualified expressions at the search execution time. Following are the basic value patterns and rules for interpretation.

Simple value:
Simple value is normally transformed to $FIELD$=’value’ or $FIELD$=value depending whether the field is text, in single quotes, or numeric.

Value with a wild card *:
Such value is normally transformed to $FIELD$ LIKE ‘wild*card’

Value following the operator:
In this case, the specified operator will be used in the expression. For example, if you specify >value, then it transforms to $FIELD$>value It is worth to mention that you may chose to use = and LIKE operators explicitly, when you do not want the operator being picked by ProjectWise, depending on the presence of the * in the value.

Operator only:
Some operators do not use values. In this case, you only provide an operator. NULL is transformed to $FIELD$ IS NULL.

Environments

Copyright © 2010 Bentley Systems, Incorporated

118

Jun-10

Searching for Documents by Environment Attributes

Quoted value:
When you supply a quoted value, it will be interpret as a value, without trying to separate the operator. This is useful when the value coincides with the operator name. For example, `NULL´ is transformed to $FIELD$=´NULL´.

Full expression macros:
ProjectWise supports a few expression macros that are interpreted as fully qualified expressions. Currently all of them are designed for DATE fields. They should either be used in a criterion alone, or be combined using AND, OR operators with other fully qualified expressions. For example $RANGE_THIS_MONTH$; or $RANGE_TODAY$ OR $FIELD$ IS NULL. Following is the list of supported full expression macros: $RANGE_TODAY$ - expands to a fully qualified expression testing if $FIELD$ is today’s date $RANGE_THIS_MONTH$ - expands to a fully qualified expression testing if $FIELD$ is date this month $RANGE_THIS_YEAR$ - expands to a fully qualified expression testing if $FIELD$ is date this year $RANGE_HOURS(x)$ - expands to a fully qualified expression testing if $FIELD$ falls between now and x hours before. $RANGE_DAYS(x)$ - expands to a fully qualified expression testing if $FIELD$ falls between now and x days before. $RANGE_MONTHS(x)$ - expands to a fully qualified expression testing if $FIELD$ falls between now and x months before. For information about developing fully qualified expressions and about operators, see the on-line Help topic Advanced Searches > Searching for documents by environment attributes.

Jun-10

Copyright © 2010 Bentley Systems, Incorporated

119

Environments

Attributes Properties Dialog

Attributes Properties Dialog
You define Attributes’ properties in the Properties dialog that appears when you select an attribute, right click, and then select Properties. This section presents its contents in detail.

General tab
The Attribute Value section has four settings • • • • Unique: Enable this to ensure that any value entered is unique in the environment. Required: Enable this to ensure that an attribute value is always entered. Use this sparingly. Access: Select Edit so the attribute value can be edited. Select Read only so the attribute value can be viewed, but not edited. Editable if final: Enable this to make the attribute available for editing if a document is in Final State.

The Clear Attribute value when section settings control when the values of a particular attribute are cleared during various operations. • Copied inside document: Enable this to clear the value when the attribute is copied inside a document. For example, if the attribute contains a sheet number and needs to be copied for use with the next sheet, the value needs to be cleared so it is ready for the next sheet number to be entered. Copied inside environment: Enable this to clear the value when the attribute is copied inside an environment. For example, if the attribute contains a document number and needs to be

Environments

Copyright © 2010 Bentley Systems, Incorporated

120

Jun-10

Attributes Properties Dialog

copied for use with another document, the value needs to be cleared so it is ready for the next document number to be entered. • Copied or moved from other environment: Enable this to clear the value when the attribute is copied or moved to another environment. For example, if the value contained in the attribute is relevant only to the source environment, the value needs to be cleared so it is ready for a new value relevant to the target environment.

Value tab
This tab has three sections. These settings determine how and when the attribute takes on values.

Default Value section
The Type item is used to specify a default value for the field. When a user creates a new document, this value will appear without the user having to enter anything in the field. • • None: The attribute will not have a default value. Fixed: Lets the administrator specify a constant (fixed value) that is the default for the attribute. Users may override the default value, but the default value will remain constant. Select: Lets the administrator enter a standard Structured Query Language (SQL) SELECT statement in the field. Using this option, the default value can be pulled from a table in the database. One such example would be: select o_userdesc from dms_user where o_username = '$USER.NAME$'

Jun-10

Copyright © 2010 Bentley Systems, Incorporated

121

Environments

and date_of_birth for a number of authors. Incorporated 122 Jun-10 . the result of an SQL SELECT statement. You might use a pick list in the author field to select the author's name from the authors table by using the following SELECT statement: SELECT name FROM authors ORDER BY authors. click the browse button by the value entry. or when any field changes. It contains a table named authors. and what value is inserted. The value updated can be a fixed value. • The SELECT statements used to update a field or enter a default value will usually contain a WHERE clause to limit the number of records returned to a single value. • System variable: Lets the administrator enter a valid system variable to serve as the default value for the attribute. so that the update occurs when any of the fields change.Attributes Properties Dialog This would result in the current user’s description entered as the default value for the attribute field. Any field can be automatically updated when another defined field changes. Suppose the environment contains the fields author. title. that has the fields name. It has the same options as the Default value section to set the values. or you can set the field trigger to update whenever the record is updated. and date_of_birth. To see a list of valid system variables. a value returned by a user defined function or a system variable or project property. • Function: Lets the administrator to enter a function name within a DLL using the browse button in the value entry. you probably want to fill the title and date_of_birth fields automatically from the authors table. title. Having selected an author. This item is typically used when custom development work is being done using the ProjectWise SDK. Update Value section This section allows an administrator to set up rules that govern when the attribute is automatically updated. One such example would be: $DATE$ This would result in the current date entered as the default value for the field. You can define multiple fields to trigger the automatic update. You can do this by Environments Copyright © 2010 Bentley Systems.

You • Jun-10 Copyright © 2010 Bentley Systems. The system variable $EDIT#field_name$ provides the means of specifying the value of another field in the current record.' Note: This assumes that the name field in the authors table is unique.name = '$EDIT#author$.name = '$EDIT#author$.dll. In this case. Incorporated 123 Environments . you enter the name of the function and the name of the file containing it into the parameters field. When using this system value in a SELECT statement. then the UpdateLogFile function is called when the field is triggered. Suppose the environment table contains the fields drw_date and chkd_by. In this case. you enter the name of the system variable or project property in the parameters field. These fields can be automatically updated when any change is made to a record by setting the trigger to update when the attribute record is changed (the default value) and setting the source of update to System Variable.dll.Attributes Properties Dialog making the author field a trigger field for the title and date_of_birth fields and using the SELECT statements: SELECT title FROM authors WHERE authors. For example.update. you must enclose it in single quotes” '$EDIT#field_name$' • You can also call a function when a field is updated.' and SELECT date_of_birth FROM authors WHERE authors. If you designate the log_file field's automatic update source to be a function and enter the parameters UpdateLogFile. • The value for an update can also be derived from a system variable or project property. suppose you have another field in the environment table called log_file and you have written a function called UpdateLogFile contained in a dynamic link library update.

• Environments Copyright © 2010 Bentley Systems. the fixed value. it is not relevant when creating a list of values from which the user will select. They cannot key in a value that is not in the list. Incorporated 124 Jun-10 . Since this method only produces one result. this section also has the following settings: • Limit to list: This option forces the user to select an item from the list. The user will then be prompted to select the fields to trigger the attribute update. • Value List section This section lets the administrator generate pick-lists in association with the Attribute. The pick-list can be generated using the same methods as described previously for Default value with the exception of the Fixed method. In addition to the methods for generating the pick-list. Update field when some attribute column(s) is updated: Selecting this option will update the attribute when specific fields in the record are updated. • Update field when the attribute record is updated: Selecting this option will update the attribute when any field in the record is updated.Attributes Properties Dialog would enter the system variable $DATE$ as the parameter for the drw_date field and $USER$ as the parameter for the chkd_by field. Multiple selection: This option will allow the user to select multiple items from the list you create. Two options that control when the attribute is updated. or to leave the item blank.

text entered by a user can be converted to upper case by entering the format string UpperCase. Environment and Attribute User Properties Settings There are categories of User Properties settings that apply to environments.day. • Control Type determines whether the field is a check box.Environment and Attribute User Properties Settings Editing tab This tab lets you control the display of the attribute and to control how it is stored in the database table. and edit field or a multiline edit field. The shorter of the two is applied to the field. Control Font Size lets you establish the font size for each field. • • • • Extra Values tab The Extra Values are used for SDK Programming and will not be covered in this module. Format String lets you force text entered into the field to adhere to a specific format. Incorporated 125 Environments . Control Font lets you select a different font for each field from the option list. Note. A multiline edit field is a word wrapping input box with the scroll bar. however. Jun-10 Copyright © 2010 Bentley Systems. Maximum Input String Length lets you limit text entered into the field to a specified number of characters. that the maximum string length will not override the length of the field as defined in the database table. Other values are LowerCase / date / date. You can use C formats to format the value. For instance.

users won’t be prompted to save changes made from the document properties dialog. All changes are saved. Environments Copyright © 2010 Bentley Systems. Note: While this might seem like a desirable behavior. User Interface-> Search Form Initially open attributes page If enabled. the Search by Form dialog opens to the General tab. It is recommended that each user be allowed to change settings in this category. then closes without saving. it removes the ability to exit the dialog without saving changes. If not. This category is provided to group those items that users typically prefer to control themselves. Note that these settings all fall under the User Interface Category. Incorporated 126 Jun-10 . users are prompted to save any changes. uses No Wizard. Once you’ve experimented with these settings. the Document Properties dialog opens to the same page that was active when it was closed. the new document is saved anyway. If disabled. Another side effect of enabling this setting is encountered when creating new documents.Environment and Attribute User Properties Settings User Interface-> Attribute Form Save changes without confirmation If enabled. If a user selects New > Document. the Attributes tab displays when users open the Search by Form dialog. you should modify the default user’s properties to reflect the desired basic settings. Select Last Used Attribute Page If enabled. partially fills out the form.

why would you use required fields sparingly? What are attribute sheets? What is a document code? Jun-10 Copyright © 2010 Bentley Systems. let’s measure what you have learned.Module Review Module Review Now that you have completed this module. Incorporated 127 Environments . Questions 1 2 3 4 5 6 Define an environment. explaining the relationship to a database. Name the four main steps used to create an environment. What is an interface? When creating an interface.

Incorporated 128 Jun-10 .Module Review Environments Copyright © 2010 Bentley Systems.

ProjectWise provides a number of methods for bringing existing data into the managed environment. Incorporated Importing Legacy Documents . For flexibility. This module discusses them.Importing Legacy Documents Module Overview Perhaps the easiest way to import existing data. into ProjectWise is to drag and drop it from Windows Explorer. there may be situations where it is more convenient to import legacy data using a noninteractive process. Module Prerequisites • • • Knowledge about ProjectWise Explorer’s tools Knowledge about document architecture Knowledge about environments Module Objectives After completing this module. However. you will be able to: • • Import documents interactively and non-interactively Scan for references and link sets Jun-10 129 Copyright © 2010 Bentley Systems. legacy documents.

which opens the ProjectWise Tools dialog. data and resources related to a given real-world project.Introductory Knowledge Introductory Knowledge Before you begin this module. Projects are a kind of super-folder that provide a single place to manage and organize documents. Both are containers for documents and other folders in the datasource. Importing Legacy Documents Copyright © 2010 Bentley Systems. Incorporated 130 Jun-10 . Questions 1 2 What is a MicroStation reference file? What is the difference between a folder and a project in ProjectWise? Answers 1 A file attached to another file so you can see the information it contains in the context of the master file to which it is attached. 2 Non-interactive Import ProjectWise's bulk-loading tools are used to identify and then simultaneously import quantities of files and folders into ProjectWise. Access it by selecting Start > Programs > Bentley > ProjectWise V8i > Tools > User Tools. let's define what you already know. Reference files are used in MicroStation and AutoCAD to display information that is contained in one design in another. The BulkLoad tool Use this tool when you want to import a large number of documents without interaction at the desktop.

Click the Bulkload icon and click Execute. you will indicate the top level directory that you want to scan. 3 Select the class datasource and log in using the administrative credentials. In the Scan directory field.doc. Once this bulkload data file exists. if you want to limit the scan to Word files.Non-interactive Import In the ProjectWise Tools dialog. The Bulkload dialog  Exercise: Open the Bulkload dialog and log in 1 2 Select Start > Programs > Bentley > ProjectWise V8i SELECTseries > Tools > User Tools. enter the file extension in the File filter text field. you can process the file using the Process BulkLoad File tool. The bulkloading process involves the following steps: • • • Create a bulkload file Process the bulkload file Scan MicroStation and AutoCAD files for reference attachments The BulkLoad tool scans the file system and creates an ASCII file that specifies all of the folders and files that you want to import into ProjectWise. • • • • The first field in the dialog lets you specify a file to record the bulkload list. Jun-10 Copyright © 2010 Bentley Systems. enter *. the Bulkload dialog appears. Once logged in. For instance. Incorporated 131 Importing Legacy Documents . which imports the specified files and folders. double click the Bulkload icon. Enable Scan subdirectories to scan all the sub-directories of the directory listed in the Scan directory field. You will log in to the datasource where you want to load the data. The Bulkload tool builds a bulkload data file that you can process immediately or save and process when needed. To filter file names. You can enter the path or browse to the directory.

Process Bulkload File options While it appears as part of the BulkLoad wizard. click Next to create the bulkload data file and invoke Process Bulkload File tool. Incorporated 132 Jun-10 . Scan Directory: Navigate to the class data set \Plant folder File Filter: *. This causes the bulkloader to ignore the existing directory structure. the Process BulkLoad File dialog is a separate tool.  Exercise: Use Bulkload to import files 1 Set the following in the Bulkload dialog: Save Bulkload File As: C:\temp\Plant files. You can access it at any time directly from the ProjectWise Tools dialog. Once the results are correct. set parameters using the Bulkload tool.* Only Files: Disabled (this includes all files) Scan Subdirectories: Enabled 2 Click Next.Non-interactive Import • Enable Only files to place all the scanned files into one ProjectWise folder. Do not enable it if you want to preserve the directory structure. To do this. and then click Cancel. The file is created in the directory specified. Importing Legacy Documents Copyright © 2010 Bentley Systems. This lets you create a bulkload file. The display in the Result portion of the dialog will vary based on the switches selected. and then process it later.

Close the User Tools dialog. you may want to determine which of the recently imported DGN or DWG files have references attached to them in ProjectWise Explorer using the Scan for References and Link Sets wizard. Results display at the lower left of the dialog. However. Plant. By default. Exercise: Process the bulkload file 1 • • •  Set the following in the Process Bulkload File dialog: Environment: Default Environment Storage: Exton 2 Click Finish. you must specify an existing folder. Since new folders are created. you must select a storage area from the Storage options. Incorporated 133 Importing Legacy Documents . If running independently. use the Manager options to do so. Hint: At this point. When running this tool using the wizard. All files are imported into Jun-10 Copyright © 2010 Bentley Systems. the data file created in the previous step will automatically appear here. you must select an environment for the documents from the Environment options. If you want to specify a different manager. the user that is logged in is the owner of the new files and folders. • Use the Parent folder options to specify a folder to act as the parent folder for the data. if you have chosen the Import Files Only option. logged in using the administrative credentials. You can also select <none> to import the folder structure at the root level. In ProjectWise Explorer. The files and folders are imported into the datasource. you will browse to a previously created bulkload data file. Since new folders are created. is used. the original name. Since you did not specify a parent folder. The Import and rename duplicates in the option in the Process Bulkload File dialog is necessary only if you enabled Import Files Only.Non-interactive Import The left pane shows the parent folder and sub-folders of the documents imported from the bulkload file into ProjectWise. Folders are displayed in a hierarchy under the parent folder. 3 4 5 Click Close. examine the resulting directory structure.

• Clicking Advanced Wizard and clicking Set as Default specifies that the Advanced Document Creation Wizard will be used when creating documents. • Clicking No Wizard and clicking Set as Default specifies that no document creation wizard will be used when creating documents. Importing Legacy Documents Copyright © 2010 Bentley Systems. Important: Changing an assigned environment is not recommended. Incorporated 134 Jun-10 . Selecting No Wizard here also ensures that if you attempt to create a new document in an integrated application. users are no longer prompted to select a wizard each time a new document is created. Note: Also. it will already have an environment assigned to it. No wizard will be used. Once a default wizard has been selected. and that copying or moving documents in ProjectWise Explorer using drag and drop will automatically perform the copy or move. or recommended. The Document Creation tab is used when creating documents. to designate an environment. it is mandatory to select an environment for the documents. The Wizard Manager The Wizard Manager lets you select a default wizard and change that selection later if you want. if you select a parent folder. the application will open whatever ProjectWise dialog it normally uses to create new ProjectWise documents. In this case. note that an object’s creator is its owner and their permissions can never be changed or removed. However. it is not necessary. Open it by selecting Tools > Wizard Manager. In this case. that clicking OK in the Create Multiple dialog will automatically create the specified number of documents with no files attached.Interactive Import the designated ProjectWise folder. This means that selecting Document > New > Document in ProjectWise Explorer will open the Create Document dialog. there is the possibility for duplicate file names. Note: If you are importing at the root level. Interactive Import The interactive method for populating metadata for documents is to drag and drop files between the Windows Explorer and the ProjectWise Explorer.

If that is the case. the field will automatically populate with the file that you are dropping into the target folder. Here you select a template on which the new document is based. to be used as the template. In most cases. When the wizard is invoked using Document > New you are required to select a file. When the wizard is invoked from a drag and drop operation. This template can be an existing ProjectWise document or an external file.Interactive Import Selecting Advanced Wizard here also ensures that if you attempt to create a new document in an integrated application. Advanced Document Creation Wizard The Advanced Document Creation Wizard is a series of pages that take you through the document creation process. either ProjectWise or external. you can expand the tree and select a folder in which to place the document or documents. You can hide this page in the future using the option in the Advanced Document Creation Wizard Properties dialog. you will have already selected the desired folder in ProjectWise Explorer before starting the wizard. On the Select Target Folder page. this page is redundant. Jun-10 Copyright © 2010 Bentley Systems. Clicking Next opens the Select a Template page. the application will open the Advanced Document Creation Wizard. Click Next on the Welcome page to step through the process. Incorporated 135 Importing Legacy Documents .

Interactive Import If document code rules are in place for the selected environment. the Define Document Code page opens. Click Next. which is equivalent to the More Attributes tab. This page is followed by the Define Secondary Document Attributes page. The next page is the Define Document Attributes page. By default. Next is the Document Properties page where you can give the source document a name to use in ProjectWise. which is equivalent to the Attributes tab in the document properties dialog. ProjectWise will enter the file name that precedes the file extension as both the document name and the document description. The full file name is the Importing Legacy Documents Copyright © 2010 Bentley Systems. Here you enter any environment attribute information that is common to all files being imported. Select the required document code information and select Show Advanced Generate Options to enter/select advanced options. Incorporated 136 Jun-10 .

If you are creating a new DGN document from inside MicroStation. The wizard has now gathered all information required to create documents. select the Standard interface from the Interface option list at the top of the application window. using the standard environment. Jun-10 Copyright © 2010 Bentley Systems. you also have the option to Check Out the new document as Shared.  Exercise: Import legacy files using the Advanced Wizard 1 2 In ProjectWise Explorer. which automatically opens the new file with the associated application. Incorporated 137 Importing Legacy Documents . Import standard. The key option on this page is Apply selected options to succeeding documents. you might want to enable the Launch associated application check box. If shareable documents is enabled for the datasource. The final page is the Create a Document page. You can change these values if required. Enabling this lets ProjectWise apply the information that you entered in the wizard pages to the remaining documents that you dropped into the folder.Interactive Import ProjectWise file name. Note: If you were creating a single document. and if you are creating a new DGN document.  Exercise: Import the environment 1 2 In ProjectWise Administrator.aam from the class dataset folder. right click Environments in the console tree and select Import. Create a new root level folder named DragDrop1. you also have the option to Create the new document shareable. You can also select an application to which to associate the document.

The Wizard Pages options control whether users see selected pages when the required information is already known. 3 In Windows Explorer. navigate to the \DragDrop1 folder in the class data set. Importing Legacy Documents Copyright © 2010 Bentley Systems. The General options let you control when the Document Creation Wizard is invoked. Click on Advanced Wizard. Enable Apply selected options to succeeding documents. which provides access to default settings for the wizard. Click the Properties button. and then click Next: Comments: Drag and drop method Type the phone extension 2809. it makes sense to set them on import. and drop them. drag the files from that folder into the new ProjectWise folder. Now you see the environment’s attributes. Click it to open the Advanced Document Creation Wizard Properties dialog. You will use the Advanced Wizard. and then click Next: Accept the default names. If attributes are common across files. and then click Next. On the Advanced Wizard Welcome page. 4 5 6 Enter the following Document Attributes. select Tools > Wizard Manager.  Exercise: Configuring the default Document Creation Wizard 1 2 3 4 In ProjectWise Explorer. You can set these now.Interactive Import The Attributes and More Attributes pages of the wizard will show any attributes defined for this environment. Enable both the Skip ‘Target Folder’ page if folder is already defined” and “Skip ‘Template page’ if template is already defined” options. Advanced Document Creation Wizard properties Selecting the Advanced Wizard option enables the Properties button in the Wizard Manager dialog. or later in the document’s Properties dialog. Make sure the DragDrop1 folder is selected and then lick Next on the next two pages. 7 8 9 10 Click Next. and then click Finish. Incorporated 138 Jun-10 . click Next.

 Exercise: Drag and drop files without a wizard 1 2 In ProjectWise Explorer. drag the files from that folder into the new ProjectWise folder. Using the Define Search dialog. In Windows Explorer.Interactive Import 5 Click OK. 3 Jun-10 Copyright © 2010 Bentley Systems. Importing without a wizard To change the default wizard you can disable Use Wizard in File Import Operation. when creating new documents using drag and drop. navigate to the \DragDrop2 folder in the class data set. you can also select the default search method for the user. Search Definition tab From here. and drop them. Incorporated 139 Importing Legacy Documents . and then click Close.brg file as a user preference. This form is typically used by more advanced users because more knowledge is required to create effective queries. each time a user attempts to find documents. either the Search Form or the Search Builder. If you set the default to No Default Wizard. and click OK. they are prompted to select which method to use. The files are created without attributes other than the file name. nor will you have any control over file names and descriptions. Select No Wizard. If you select No Wizard. you can set No Wizard as the default. create a new root level folder named DragDrop2. and description. This information is stored in the pwv8. document name. You do not have an opportunity to enter any attributes for those files. Alternately. The Search Form uses the same dialog used to display document properties. you can use virtually any system or custom attribute to find documents. the files are created immediately.

When stored in Windows folders. The first part of setting up the wizard is to identify any folders that need to be scanned. other than the time required to perform the scan. You can do this using a Priority Search. use the Scan References and Link Sets wizard.Completing the Process Completing the Process Reference files are used in MicroStation and AutoCAD to display information that is contained in one design in another. You should include any folders to which CAD files were recently imported. To scan DWG documents. you can set the scanner to scan only the MicroStation and AutoCAD documents in these folders. To make these relationships known to ProjectWise. In either case. the wizard will still scan the designated folders. the Scan Summary message that appears at the end of scanning will show that the scan “Resolved 0 references”. unless you are sure the files have no references. pointing to the proper location in ProjectWise. you can set the scanner to search for certain application types. ProjectWise Explorer’s Scan for References and Link Sets tool can be run on both DGN and DWG files to manage reference relationships. For example. The second part is to determine how you want to search for the referenced documents. once you bring designs into ProjectWise. all you need is ProjectWise Explorer. You’ll want to select all folders containing new CAD files. the linkages between the files are kept using full path definition or using a logical directory definition. Incorporated 140 Jun-10 . MicroStation V8i or ProjectWise Navigator V8i is required to scan DGN documents. but is not initially recognized or maintained by the ProjectWise database. or a combination of the two. However. If neither is installed. Importing Legacy Documents Copyright © 2010 Bentley Systems. the reference files used by that file can be copied out at the same time. a Proximity Search. and optionally sub-folders. their physical relationship is kept. Using the Scan References and Link Sets wizard When MicroStation files and their attachments are imported into ProjectWise. ProjectWise uses the term “set” to describe a grouping of master and reference files. There is no disadvantage to scanning a file that doesn’t include references. Once you have specified all folders. When users check a file out. these linkages need to be reestablished.

and the order in which those folders should be processed. The Proximity search provides options to search Current Folder. or the same folder.Completing the Process Priority search This process involves specifying folders in which to search for referenced documents. which shows the documents that are referenced into that particular document. Jun-10 Copyright © 2010 Bentley Systems. Incorporated 141 Importing Legacy Documents . ProjectWise's Scan References and Link Sets wizard supports live nesting of references in both MicroStation and AutoCAD. If you choose to use both Priority and Proximity search algorithms. but it can be cumbersome to define the search criteria. you’ll then specify which to use first. You can specify a different folder from the folders selected to search for master documents. the file's nest depth is also obtained and stored in the ProjectWise database. Combination search You can enable both searching options. use this if you do not know where files are. However. Note that search order becomes very important if file names are not unique. or even a specified number of folders above the Parent folder. Use this method if you know where files are. Before you begin using the scanning wizard. You can do this using the Priority search. make sure of the following. the most likely time to use the wizard is after importing quantities of files into ProjectWise. Note that if there are duplicate matches. As the wizard is scanning all of the specified folders and documents it creates a logical set for each master file. It makes sense to do a Priority search and then Proximity. the search stops at the first match. Proximity search This process lets you easily set search criteria to find referenced files in folders near (or the same as) the master document. You may want to run it periodically as documents are attached to and detached from master documents. Parent Folder. For each master file detected during the scanning process. This is true for files imported using either drag and drop or ProjectWise's bulk-loading tools. all sub-folders from the designated folders can be searched for referenced documents. You can use the wizard as often as you need. In addition.

you do not need to re-scan. MicroStation or ProjectWise Navigator is set as the Scan Reference engine under General Programs in the ProjectWise Administrator Application category. Incorporated 142 Jun-10 . However. click Add Documents. The next page in the wizard lets you select the folders containing the files to be scanned.Completing the Process • You are either an administrator or a user with Write and File write permissions. If this is the first time you are scanning a particular folder or group of folders. Select the folders and individual documents you want to scan for the presence of master documents. Enable the check box to the left of any item in the list you want to re-scan for any newly attached or detached references. you may want to re-scan if you know that Importing Legacy Documents Copyright © 2010 Bentley Systems. ProjectWise Explorer must be installed with iDesktop support for MicroStation. click Add Folder. choose to scan for master and referenced documents. • • • The scan process The Scan References and Link Sets wizard opens to a Welcome page. This is necessary because the path to each referenced file must be updated to point to the ProjectWise location for the file. To add documents individually. check boxes for items added to the list are automatically set. creating new sets when necessary and updating any existing sets that are found. To add a folder to scan. All of the master and reference files that you want to scan are imported into ProjectWise. On the Specify Scan Options page. the sheet icon. for DGN Link Sets. or for both. and you click Next to continue. This means that ProjectWise will scan all documents in that folder. By default. ProjectWise will bypass existing sets in that folder or document. and will only scan the documents that are not already identified as master documents. When you clear an item's check box. the open folder icon.

or removed from. Incorporated 143 Importing Legacy Documents . Priority search lets you select exactly which folders and the order in which reference scan will look for attachments. you’ll proceed to the Priority Search page. documents of all application types are scanned. Again. When you have finished enabling sub-folder scans and selecting document application types. Only documents of the selected application type are scanned.Completing the Process documents were referenced to. existing logical sets. When you have added all of the folders and documents you want to scan for master documents. From the Select Document Application Types option list. Turn on Enable Priority Search and then click Add Folder to select the folders you want to scan for reference documents. and select the type of documents to scan. You can select the check boxes individually. you can either select the check boxes individually or click Check All. or click Check All to select all items in the list. Enable the check box to the left of any folder in the list to include that folder's sub-folders in the scan. If no application type is selected. The Master Folder Settings page lets you include sub-folders of the selected folders in the scan. select the document application types you want to scan. Jun-10 Copyright © 2010 Bentley Systems. you proceed to the next page to specify folder settings.

Warning: If you have more than one file with the same name. select the folder in the list and click the up or down arrow. To move folders up or down in the search order. When you have finished with the Priority search page. Incorporated 144 Jun-10 . If Enable Priority Search is disabled on the previous page. It is critical to have the order of the priority search set correctly. Importing Legacy Documents Copyright © 2010 Bentley Systems. you’ll proceed to the Proximity search page.Completing the Process Enable the check box to the left of any folder if you want to search its sub-folders for references. It can be set to start in the folder found to contain master documents. A proximity search tells the scanner to where to start the search. When you perform an Advanced search that goes high in the folder structure and turn on the option to scan subfolders. you are ensuring that all neighboring folders of the selected folders are included in the scan. or in addition to. top folder first and bottom folder last. the folder just above that. The Proximity page can be used as an alternative. the Priority search page. you have no choice but to configure a proximity search on this page. The search is performed in the order that the folders are listed. To include sub-folders in the proximity search. or several folders above that. ProjectWise will attach the first one it encounters. enable Search all subfolders for References.

Priority then Proximity. In the Log File Name text field. or specify the starting point for the scan. If you select an existing log file. This page is used to set the order in which priority and proximity searches are performed. you can select Priority Only. If both are configured.Completing the Process Select the Current Folder. select Yes to view it or No. or Proximity then Priority. you are presented with a summary of what occurred in the scan. Parent Folder. Clicking Next will bring you to the last page where clicking Finish initiates the scan for master documents and their references. If you did not specify a log file. you proceed to the Search Order page. You can set the path by keying it in or you can browse to select a location for the log file. When the scanning is finished. and the option is grayed out. specify how many folders above the current folder you want to move before starting the scan. Progress displays in the wizard. the contents of the file are overwritten with the new scanning results. Incorporated 145 Importing Legacy Documents . it is created when the scan is initiated. click OK. If you type the name of a log file that does not exist. This item will only be available if both types have been configured. The scan is ready to run. Jun-10 Copyright © 2010 Bentley Systems. If you specified use of a log file. If you have only specified only one type of search to perform. that type displays in the Search Order option list. specify the path to and the name of an existing or new log file. When you have finished defining the proximity search. If you select Advanced. Proximity Only.

You receive a message at the end. Importing Legacy Documents Copyright © 2010 Bentley Systems. Check the box by the Refscan folder to search its sub-folders. and then click Next. 3 4 5  Exercise: Create and run the scan 1 2 3 In ProjectWise Explorer. and drop them. drag the sub-folders from that folder into the new ProjectWise folder. On the Priority search page. and then click Next. add the \Refscan\Drawings sub-folder to the list of folders to scan. select Tools > Scan References and Link Sets and. enable Include subfolders and click OK. In Windows Explorer. and then select the sub-folder Drawings. and then click Next. click Next Disable the Scan for DGN Link Sets check box. add the Refscan folder to the list of folders to search for references. 4 5 6 7 8 Check the box next to the Drawing folder and select MicroStation as the Application. After the folders have been imported. and then click Next. click Next. enter C:\temp\refscan. In the log file field. and then click Finish. When the Import Directories dialog appears. Hint: You can search the log file for the word “error” to find file with missing references. Leave Enable Proximity Search disabled.log. navigate to the \Refscan folder in the class data set. Click the Select Folder icon. 9 Close the log file and refresh the view in ProjectWise Explorer. and then click Next.Completing the Process  Exercise: Import the files 1 2 In ProjectWise Explorer. press F5 to refresh. Expand the refscan folder. These drawings include references to the border file and to extraction files. create a new root level folder named Refscan. Incorporated 146 Jun-10 . indicating the number of documents scanned and the number of references found. on the Welcome page.

or saved views that can be stored in a DGN file or a DGN library. note the icon has changed for all but one of the files in the \Drawings folder. right clicking an item in the Link Set tree is the same as right clicking a document in the document list and therefore opens the same right-click menu. This new icon indicates that these files have reference attachments. The options enabled on this Jun-10 Copyright © 2010 Bentley Systems. If there is no awareness of link sets existing in folders outside of any projects. or when you run the Scan for References Files and Link Sets wizard on newly imported DGN files that contain link sets. Since link sets are stored in ProjectWise documents and contain links to other ProjectWise documents. Incorporated 147 Importing Legacy Documents . A link set is a group of links to other files. then that project will not have a Link Sets tree. references. If ProjectWise is not aware of link sets in a project. Just enable the option on the Specify Scan Options page. Any link sets that exist in folders that are not in any project are displayed in the main Link Sets tree. Using the Link Sets tree Link sets are created in ProjectWise automatically when you create link sets in MicroStation in existing ProjectWise documents. the Scan for Reference Files and Link Sets wizard can also be used to scan newly imported DGN documents for the presence of link sets. In ProjectWise Explorer. the Link Set dialog is used to create and manage link sets. link sets and their links display in the Link Sets tree under the project in which the link set exists. In MicroStation. under the Documents root folder. The rest of the wizard pages work the same as they do when scanning for references. MicroStation link sets are supported in ProjectWise. models. In ProjectWise Explorer. and the Project Explorer dialog is used to create the actual links. and the specific links in each set. link sets and their links display in the Link Sets tree under the project in which the link set exists.Completing the Process When you refresh the view. Working with link sets As the name implies. the main Link Sets tree will not display. which is a sub-folder of the Documents root folder. Any link sets that exist in documents that are not in any project are displayed in the main Link Sets tree. You can expand any Link Sets tree to display all the link sets in that ProjectWise project.

After you select a DGN file and check it out in exclusive or shared mode. changed. Select Active File if you want to check out a link set but do not need to save any changes to it until you check in the DGN file or update the server copy. the link set also will be deleted. the Check In icon in the Link Sets dialog is available. which is not being checked in yet. When you are using ProjectWise Explorer to check out link sets and DGN files containing link sets. you cannot check in changes to the link set at this point because the link set resides in the open DGN file. Importing Legacy Documents Copyright © 2010 Bentley Systems. Incorporated 148 Jun-10 . Selecting the correct link set source Link sets come from one of three sources. Note that the Check In icon in the Link Sets dialog is gray and is unavailable. if you use ProjectWise Explorer to delete a DGN document that contains a link set. or explicitly deleted in ProjectWise Explorer. it is important that you select the correct source in the Link Sets dialog. When you are using link sets in the active file. You can check in changes to the link set or update the server copy at any time.Completing the Process menu depend on what your user properties settings and permissions are for the selected link set or linked document. You must use MicroStation to perform these tasks. If you plan to change a link set. you will be unable to modify the link set at this point. If you make changes to a link set in the active file. they cannot be saved until you select File > Update Server Copy or check in the DGN file. However. This functionality is the same as if you were using only MicroStation to open the link set. you can use Active File as the source of your link set. If Configured Libraries is the source of your link set. Note: Links sets and links cannot be created. it is easiest to use Selected File as the source of the link set.

Clicking the small arrow to the right of this icon lets you select whether to check in the DGN document or to just update the server copy and keep the document checked out. the Check Out icon. Incorporated 149 Importing Legacy Documents . Clicking the small arrow on the right side of this icon lets you check out the DGN file or refresh the local copy. When the icon displays a blue upward arrow. a Check In / Check Out icon appears on the Link Sets dialog. Jun-10 Copyright © 2010 Bentley Systems. appears. an additional icon does not appear in the icon bar. the Check In icon is gray and is unavailable. Note: If the link set is stored in the configured DGN libraries. you can either check in or update the server copy of the link set document when you have made changes to it. a blue upward arrow. All other icons on the icon bar are unavailable. If you have the link set's DGN file open but it is not available to be checked in. If you have the link set's DGN document checked out. If you have the link set's DGN file open in read-only mode. If you have the link set's DGN document open and someone else has checked it out and made changes to it. the Check Out icon is gray and is unavailable. When the icon displays a green downward arrow. you can either check out or refresh the local copy of the link set document. the Check In icon appears. You cannot edit link sets unless you are in the DGN library in which they are created. a green downward arrow.Completing the Process Checking link sets in and out in MicroStation When you are in an integrated session of MicroStation. All other icons are unavailable too.

How do you do this? 6 7 Importing Legacy Documents Copyright © 2010 Bentley Systems. the key option on the Create a Document page is Apply selected options to succeeding documents. the user that is logged in to ProjectWise Explorer is the owner of new files and folders. and create a relationship in the ProjectWise datasource accordingly.Module Review Module Review Now that you have completed this module. let’s measure what you have learned. By default. Questions 1 2 3 4 5 When should you use the Bulkload tool? True or False: You must run a bulkload data file right after you create it. What does it do? What are the results when you import documents using no wizard? After importing any MicroStation or AutoCAD files. you may want to determine which of the recently imported files reference other MicroStation or AutoCAD files. Incorporated 150 Jun-10 . you should not designate an environment for the files you are importing into it. When using the Advanced Wizard. Where do you change that? True or False: When you import files into an existing folder.

or in combination with. These searches can be used in addition to. you will be able to: • • • • Understand the extraction process Extract thumbnails. the metadata search capabilities provided by ProjectWise. Module Prerequisites • • • Knowledge about ProjectWise Explorer’s interface Knowledge about document architecture Knowledge about user accounts Module Objectives After completing this module.Document Indexing Module Overview Rather than using information entered manually by a user. This module discusses how to use indexing processes and how to use the data. Incorporated Document Indexing . advanced document indexing techniques use document content to index ProjectWise documents. full text. and file properties Process non-standard file types Monitor processing Jun-10 151 Copyright © 2010 Bentley Systems. Where metadata-based searches use information about the file. these techniques use information found in the file.

ProjectWise Integration Server delivers document processors for extracting text. you should not designate an environment for the files you are importing into it. to designate an environment. Incorporated 152 Jun-10 . If you select a parent folder. it is difficult to attempt to search all the storage areas efficiently. thumbnail images. It is more efficient to extract this information to the database for immediate retrieval. Hide folder hierarchy in user interface. ProjectWise has different categories of advanced document indexing: • Thumbnail indexing Document Indexing Copyright © 2010 Bentley Systems. Changing an assigned environment is not recommended.Introductory Knowledge Introductory Knowledge Before you begin this module. and the results are displayed in or accessed from ProjectWise Explorer. 3 Extraction Process Overview Since the distributed architecture of ProjectWise lets you store files at multiple locations. it will already have an environment assigned to it. Questions 1 2 3 What are the Attributes and More Attributes tabs in the document properties dialog? True or False: When you import files into an existing folder. it is not necessary. Which user properties setting is useful to hide the folder structure from users? Answers 1 2 These tabs are the user’s means of accessing extended document metadata. let's define what you already know. and file properties from documents in the datasource. Extraction jobs are configured from ProjectWise Administrator. or recommended. In this case. True.

PPT. PNG. • • • • • Image files (. the following extensions are supported by thumbnail extractions: • • • MicroStation/AutoCAD extensions DGN and DWG automatically supported Image extensions: BMP. DIB. Incorporated 153 Document Indexing . • Enable or disable extractions. .Extraction Process Overview • • File property indexing Full text indexing Each of these refers to data stored in the document’s file. JPEG. PDF files contain searchable text. In general. JFIF.tif. TIFF Microsoft Office document extensions: DOC. In order to search this information quickly. File property extraction depends on attributes added to the file by the native application. JPG. XLT How it works For each document processor. Not all file types include thumbnail previews. but not all. XLS. Not all of the items listed are found in each file type. Some. PCX. Each application vendor provides a different list of file properties.jpg) do not typically contain searchable text. it must be extracted from the file and stored in the ProjectWise database. you can do the following. Some file types that do contain thumbnail previews do not adhere to the Structured Store standard and require the native application to view the thumbnail. GIF. DOT. Supported file types The file type extensions supported by thumbnail extraction depend upon the operating system and any additional software that is installed. Jun-10 Copyright © 2010 Bentley Systems. TIF.

Incorporated 154 Jun-10 . If all documents are not processed during a scheduled extraction. Prevent files of specified file type extensions from being processed. Start an extraction manually. The first time you run an extraction on a datasource. the extraction engine filters out the documents it will not process based on any extension mapping settings you configure. If manually starting extractions. • If you configure or change any extension mappings between extractions. this process occurs until all documents queued for processing have been processed. any documents already processed during a previous extraction. whether by schedule or manually. and queues the rest of the documents for processing. whichever happens first. any documents still queued for processing will be processed taking the new extension mapping rules into account. whether a schedule has been defined or not. Force the reprocessing of all documents in a particular folder. all documents in the datasource are candidates for processing. When an extraction starts. will not be identified for processing during the routine inspection pass. the remaining documents will be processed during the next scheduled extraction. and then the next set. and inspects the datasource for any new or updated documents requiring processing. During document inspection. you must mark the folders containing them for reprocessing. the extraction engine sends the next set of documents to be processed. the extraction engine inspects the datasource for documents to process. until all queued documents have been processed. The next time an extraction starts. You set the number of documents that will be processed. the extraction engine processes any documents still marked for processing from a previous extraction. the extraction engine will only process the number of documents you have set to be processed at a time. so the new extension mapping rules will not be taken into account.Extraction Process Overview • • • • • Schedule an extraction to automatically start and run continuously at specified intervals of time. • If you have scheduled extractions. Map unrecognized file type extensions to extensions recognized by the extraction engine. You can mark as many folders as Document Indexing Copyright © 2010 Bentley Systems. and which have not otherwise been updated. or until the schedule runs out of time. However. To reprocess documents that have already been processed. When those documents have been processed.

the documents in those folders will remain queued for processing until they have been successfully processed. Server requirements The default configuration calls for all file extraction processes. Jun-10 Copyright © 2010 Bentley Systems. To offset the need for additional server resources. Rather than one large process that either succeeds or fails. or Automation Service Administrator. the administrator can configure extraction processes to run during time periods when the server is not heavily loaded. once marked. The queue information is stored in a SQL Server database dedicated to the Orchestration Framework. As a document is successfully processed through each stage. Orchestration Framework Administrator. Architecturally. The downside of this approach is that the indexes will not be updated as quickly. ProjectWise Orchestration Framework Service The ProjectWise Orchestration Framework Service is required to install any of these document processors. can be installed if you want to monitor the status of the extractions. it is removed from the queue for the current stage and added to the queue for the next stage. rather than having to start over at the beginning.Extraction Process Overview necessary. Incorporated 155 Document Indexing . Before enabling these extraction processes. care should be taken to ensure that sufficient server resources are available. and subsequent searches may produce incomplete results until the indexes are updated. Distribution Service Administrator. with the exception of the actual Microsoft full text index. This way a file extraction can resume where it left off in the event of a server reboot. the process is divided into many smaller steps. Using this tool. Orchestration Framework Administrator is installed by installing Orchestration Framework SDK. to run on the ProjectWise Integration Server. while not required for running extractions. ProjectWise provides the capacity to schedule extraction processes using the ProjectWise Orchestration Framework Service. This places significant additional load on it. The Orchestration Framework divides each file extraction process into multiple stages. each stage of the process is represented by a queue and a corresponding executable that resides in memory.

Hint: You may want to create a ProjectWise user account specifically for this purpose. you can use ProjectWise Orchestration Framework Administrator. Assuming that all prerequisites were met. folders. Specify the schedule for updating the index. To monitor the status of an extraction. you will find items for Thumbnail Extraction. and saved search results. Specify a ProjectWise user account that will have proper access privileges to all documents. Generally. If the ProjectWise Integration server does not have sufficient resources. • • Enable and disable the extraction on a per-datasource basis. thumbnails. It is recommended that dual CPU systems be used to host ProjectWise when file extraction processes will be heavily used. thumbnail. Within that configuration category. DGN indexing (a subset of Component Indexing) is more granular. you can run extraction processes on a separate server. File Property Extraction. these processes will consume all available CPU cycles. depending on which extraction processes are enabled. at full load. Incorporated 156 Jun-10 . file property extraction and full text indexing provide configuration items specific to the particular extraction process. Under full load. In addition to these common steps. and file property indexing are each enabled or disabled on a perdatasource basis. this number may increase by as much as 200 to 300 MB. Exact privileges vary depending on the extraction process. In addition. Specify non-standard file extensions and how to handle them. Full text. the ProjectWise Administrator will add a Document Processors item at the bottom of the console tree. The process for configuring each of these features includes the following common steps. which is installed when installing ProjectWise Document Indexing Copyright © 2010 Bentley Systems. the infrastructure to support extraction processes will consume approximately 100 MB of memory at idle.) Configuration Configure the full text. and Full Text Indexing. (Distributing those processes to additional systems is outside of the scope of this course. and file property indexing features from ProjectWise Administrator. • • • Specify performance tuning parameters. and can be configured to index specific files.Extraction Process Overview Exact hardware requirements will vary based on many factors.

this process is responsible for obtaining a temporary copy of each scheduled document from its storage area. Select View > Thumbnails. Select View > Thumbnails from the Windows Explorer menu. and then stores it as a binary object in the ProjectWise datasource. Navigate to the class data set folder Document Indexing\MS-V8. a good test is to view a file’s thumbnail from Windows Explorer prior to extracting it in ProjectWise. 3 4 Jun-10 Copyright © 2010 Bentley Systems. Since these are MicroStation/J files. Thumbnail extraction: This process is responsible for scanning the file. and are not generated by ProjectWise. and extracting the thumbnail image when it exists in the file.  Exercise: View thumbnails in Windows Explorer 1 2 In Windows Explorer. if one exists. Thumbnail storing: This process is responsible for storing the thumbnail in the ProjectWise datasource. ProjectWise Automation Service Administrator. navigate to the class data set folder \Document Indexing\MS-J. Since ProjectWise is only extracting preexisting thumbnails. and linking it to the document. Incorporated 157 Document Indexing . you will not see thumbnails.Thumbnail Extraction Distribution Service Administrator. The Orchestration Framework divides the thumbnail extraction process into the following stages. or the ProjectWise Orchestration Framework SDK. Thumbnail Extraction The thumbnail extraction process extracts the thumbnail image from the file. or deleted documents File retrieval: Since all extraction processes run on the Integration Server. It is not necessary to have the native application for a file type installed on the ProjectWise server. • Scheduling: This process checks the datasource for documents that should be scheduled for extraction. it should also display in ProjectWise Explorer. recently modified. This includes any new. or queues. If a thumbnail displays in Windows Explorer. • • • It is important to understand that thumbnails are being extracted from the file.

in minutes. Remember that this account should have privileges to access all documents. This security consideration is the reason for this special user. Prior to enabling thumbnail extraction. and that the specific privileges vary depending on the extraction process. the previously extracted thumbnail may no longer be up-to-date. As modified files are checked in to ProjectWise. you’ll create a new user account specifically for running extraction processes.  Exercise: Setting up a user account for extraction processes 1 2 In ProjectWise Administrator. the Orchestration Framework provides infrastructure to build a weekly schedule. On the Settings tab. and then click OK. the extraction process must be run on a regularly scheduled basis.  Exercise: Checking test files for document indexing 1 In to ProjectWise Explorer. It is recommended that the user properties setting General -> Use access control is disabled. so all documents are accessible to all users. which it is by default. Document Indexing Copyright © 2010 Bentley Systems. click Apply. To meet this requirement. navigate to the Document Indexing folder and select the MS-V8 folder. Right click the extraction user and select Properties. expand the General category. Set the following: Name: Extraction Description: Extraction user Security Type: Logical User Name/Password: your choice 3 4 5 Click OK. Incorporated 158 Jun-10 . the user properties setting Document -> Modify must be enabled. right click Users in the console tree and select New > User. At this point. During periods when extractions are allowed to run. disable Use access control.Thumbnail Extraction Typically. For thumbnail extractions. thumbnails are generated by the desktop application as the user exits the file and saves changes. This allows the administrator to define the days and hours the extraction processes are allowed to run. For ProjectWise to display up-to-date thumbnails. the administrator defines the frequency. with which the datasource is checked for updated documents. no security schema is in effect.

Automatic extractions  Exercise: Enabling thumbnail extraction for the datasource 1 2 Return to ProjectWise Administrator. Thumbnail extraction is now enabled. 5 6 Set “Check for updated documents every (minutes)” to 2. The Run radio button should be enabled. When it is.dgn. 2 Click CB1. Click OK. Once thumbnail extraction has completed. enable a period of time that includes the day of this class by dragging the pointer across the blocks. right click on Thumbnail Extraction in the console tree and select Properties. If Sleep is enabled. the process will hibernate until there are documents needing to be updated. To remove the color from the blocks. 4 In the schedule grid. enable the sleep radio button and click the block. Open the Windows task manager and select the performance tab to monitor the process. select \Document Indexing\MS-V8\CB1. Based on the configuration 7 8 Jun-10 Copyright © 2010 Bentley Systems. but even though the file contains a thumbnail. each block you click is non-run time. each block you click in the grid will become run time.dgn in ProjectWise Explorer to verify that the thumbnail is displayed. The preview pane shows metadata for the document. When you see the heavy CPU usage at two minutes.Thumbnail Extraction This folder was created and populated in a previous module. Incorporated 159 Document Indexing . set the following: Extraction enabled: Enabled ProjectWise User: Extraction User Password: <enter password> 3 Select the Scheduled Updates tab. On the General tab of the Properties dialog. expand Document Processors. it’s not displayed because the thumbnail extraction process has not been enabled.

This is the case even if no changes were made to the file. this document is added to the queue. double click \Document Indexing\MSV8\CB2. ProjectWise will check every minute to see if there are new or modified documents. checking the file in. Enable Extraction enabled and enter the extraction user’s name and password. and then select all the filled in day/time cells. Right click the Thumbnail Extraction icon again and select Start Processing Now. The next exercise uses MicroStation to demonstrate how ProjectWise updates thumbnails when files are updated. ProjectWise will flag it as having an out of date thumbnail.Thumbnail Extraction specified in the previous example. Note: To clear a time slot that is currently scheduled to run extractions. 3 4 Select File > Save Settings. MicroStation creates the thumbnail by including the contents of a Saved View named Preview. Configure any extension mapping rules. Because you checked the document out and back in.dgn. The next time the File Extraction processor checks for documents that need to be updated. Select File > Exit.  Exercise: Modify a thumbnail in MicroStation 1 In ProjectWise Explorer. and then click OK. Manual extractions  How to manually start thumbnail image extractions: Right click the Thumbnail Extraction icon and select Properties. the contents of the lowest numbered open view are used. 2 Click Fit View in the View 1 view controls. Incorporated 160 Jun-10 . 5 When you are done. change the scheduled update period so that extraction does not run every 2 minutes during class. Note that Views 1 and 2 are open. changing them back to not filled in. If no saved view exists with this name. Document Indexing Copyright © 2010 Bentley Systems. select Sleep. The existing thumbnail was created from the contents of View 1.

but you must enable it on a per-document basis. If you need to run an extraction before the next extraction is scheduled to occur. no scheduled extractions will occur. When the Extraction enabled option is off. Document Properties dialog. Write. thumbnails require 3 . Incorporated 161 Document Indexing . • • • • • Hint: The Datasource Properties dialog’s Statistics tab lets you see the number of Full Text Extractions You can configure full text indexing extractions to start automatically based on a schedule. On average. In addition. Starting extractions manually will not cancel any upcoming extractions you have scheduled. the next extraction will occur as regularly scheduled. Full Text. Microsoft applications (Word. This setting is found in the File > Properties. nor will any manually extractions be allowed to start. Look for Thumbnails. PowerPoint. Jun-10 Copyright © 2010 Bentley Systems. and File Write privileges to the document. Thumbnail images are 96x96 bitmaps. you can also manually start the extraction. or if no extraction schedule is defined. It must also be given Read privileges to all folders.5k of storage each. files processed during extractions. and are stored as binary objects in the database.Full Text Extractions More about thumbnails: • For thumbnail extractions. the specified user account must have Read. on the Summary tab. after you manually start an extraction. or File Properties in the Categories column. the user properties setting Document -> Modify must be enabled. File Read. and to run for a specified interval of time. Excel) support thumbnails.

ProjectWise Integration Server then filters the file list before sending it back to the user. the Microsoft Indexing Server must be started at all times. and Whose owner is the Engineering department. When a user requests a full text search.Full Text Extractions Extracted text is stored in a special index catalog on the designated Indexing Service computer and can be searched on in ProjectWise Explorer's Search dialogs. and any other criteria entered by the user. Within ProjectWise. it responds back to the ProjectWise Server with the GUID of the documents. The Microsoft Indexing Server and its corresponding catalog can be installed on any available system. ProjectWise then sends the list of documents containing the text back to the requesting user. These files are XML subsets of the original documents. This filtering is based on the user’s access rights. containing only the text found in the native file. However. and then stored in the Microsoft ProjectWise catalog as XML files. and Containing the word “detail” This would be a more effective search than simply searching for all documents containing the word “detail”. when the indexing server is installed on any system other than the ProjectWise Document Indexing Copyright © 2010 Bentley Systems. rather than in the ProjectWise database. It is recommended that you set up a special account for extractions with the user properties setting General -> Use access control off. Incorporated 162 Jun-10 . and Document Read access. Due to the architecture. When queries are executed. text elements are extracted from native document files. it makes queries against the catalog. ProjectWise Integration Server queries the Microsoft server to see if any files in its ProjectWise catalog contain the text in question. the Microsoft Index server produces the file list. If the indexing server finds a file in its catalog. This allows you to combine traditional metadata-based search criteria with full text search criteria. ProjectWise never looks directly at the Microsoft catalog. One example would be to find all documents Whose type is drawing. Indexing Service architecture The Microsoft Indexing Server maintains a catalog of files that have been indexed. It is important to understand that the actual text index is stored in the Microsoft catalog. It is not mandatory for it to be installed on the same system as the ProjectWise Integration Server.

or deleted documents. or queues. • Scheduling: This process checks the datasource for documents that should be scheduled for extraction. If the file is a DGN or DWG file. this process is responsible for obtaining a temporary copy of each scheduled document from its storage area. • • Choosing a folder for the Microsoft Catalog The full text indexing feature uses three distinct local folders: Jun-10 Copyright © 2010 Bentley Systems. Incorporated 163 Document Indexing . depending on the file type. This includes any new. where the flow is linear. If sufficient hardware resources are not available to the integration server. all other processes supporting the full text index feature are installed on the ProjectWise Integration Server.Full Text Extractions Integration Server. Process stages The full text indexing process is divided into the following distinct stages. the process branches. Once this file is created. it must be registered or the ProjectWise Integration Server will not know where to find it. Text Extraction: At this point. By default. A dedicated process in memory services each queue. When a document is processed by the MicroStation processor queue. the file is scanned to generate a corresponding XML file. the document is re-queued into the Text Extraction queue as a native file type. If the file type is natively supported by the Microsoft Index server. these components can be deployed to other servers. Unlike thumbnail extraction. depending on the file type. • Index Update: This process is responsible for updating the Microsoft ProjectWise Catalog to include the new (or modified) XML file. the file is added to the MicroStation processor queue. File Retrieval: Since all extraction processes run on the Integration Server. then the text extraction queue is responsible for scanning the file and extracting the text into the XML file. There are no links from the ProjectWise datasource record to the Microsoft ProjectWise Catalog. the full text indexing process may branch. recently modified.

Full Text Extractions • • • For the text index catalog For the text index proxy files To temporarily store the documents whose text is being indexed When you install ProjectWise Indexing Service. For example.(ProjectWise Integration Server computers only) Under the same key. which contains the text extracted from the document. Then for each document that gets processed.Close the Windows Registry Editor. Document Indexing Copyright © 2010 Bentley Systems. create a string called ExtractionTempDir. 6. then the recommended solution is to preset where these items will be. Incorporated 164 Jun-10 . For example. D:\ProjectWise-Full-TextIndex-Storage\Data. and for its value enter the path to the folder in which you want the text index catalog to be created and maintained. 4. before installing ProjectWise Indexing Service or ProjectWise Integration Server.Under that key. As you run text extractions. ProjectWise copies out the documents from the datasource and stores them in a local folder on the ProjectWise Integration Server computer. or when you install ProjectWise Integration Server with Full Text Indexing enabled. and for its value enter the path to the folder in which you want ProjectWise to store and maintain the text index proxy files. For example. D:\ProjectWise-Full-Text-Index-Storage. D:\ProjectWise-Extraction-Temp-Directory. 5.Create the following registry key: HKEY_LOCAL_MACHINE\SOFTWARE\Bentley\ProjectWise\Automated File Processing 3.Open the Windows Registry Editor on the computer on which you are about to install ProjectWise Integration Server or ProjectWise Indexing Service. and for its value enter the path to the folder in which you want ProjectWise to temporarily store the files downloaded for extraction. ProjectWise creates a proxy file. The default location for these text index proxy files is "C:\Documents and Settings\All Users\Application Data\bentley\index-storage\Data". create a string called FtrIndexDataDir. 2. ProjectWise sets the default location for the text index catalog to "C:\Documents and Settings\All Users\Application Data\bentley\index-storage". create a string called FtrIndexCatalogDir.Under the same key. If you need to have these items stored in a different folder or on a different drive.  How to preset the location of the text index catalog and the text index proxy files: 1.

2. Note: When you create a new directory. • • Not enough estimated space on the C: drive for the XML files. although the default location is typically sufficient for the ProjectWise Catalog. go back to the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\ContentIndex\C atalogs\bentley_index registry key and modify the value of the Location string Jun-10 Copyright © 2010 Bentley Systems. stop the (Microsoft) Indexing Service. go to the folder where your existing catalog. the directory will contain data and that data must be moved too. stop the ProjectWise Orchestration Framework Service. It is possible to move the folder after enabling full text indexing. full text indexing process isn’t enabled.wci folder currently lives (for example. and look at the path specified in the Location string. Possible reasons for moving the catalog are as follows. "C:\Documents and Settings\All Users\Application Data\Bentley\indexstorage"). Once enabled.Find the registry key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\ContentIndex\C atalogs\bentley_index.In the Registry Editor. 3.On the ProjectWise Integration Server computer. It is much easier to designate a new directory prior to enabling full text indexing. The folders specified in the FtrIndexDataDir and ExtractionTempDir strings will be created when the first extraction occurs.wci folder lives. "D:\Bentley\index-storage"). Incorporated 165 Document Indexing . open your Windows Registry Editor.On the ProjectWise Indexing Service computer.On the ProjectWise Indexing Service computer.wci folder to (for example. 7.In Windows Explorer. 6. It is a policy not to store application data on the C: partition. the original directory can be removed if the  How to move just the full text index catalog: 1.In Windows Explorer. and copy it to the new folder you just created. This is the path to where your catalog. 5.Full Text Extractions The folder specified in the FtrIndexCatalogDir string will be created automatically when you install ProjectWise Integration Server or ProjectWise Indexing Service. 4. create a new folder where you want to copy the existing catalog. but it is preferable to do so beforehand.

In the Registry Editor. 7. 10. find the registry key HKEY_LOCAL_MACHINE\SOFTWARE\Bentley\ProjectWise\Automated File Processing or For 64-bit operating systems. go to the folder where your existing proxy files live.Restart the (Microsoft) Indexing Service and the ProjectWise Orchestration Framework Service. 11. Document Indexing Copyright © 2010 Bentley Systems.wci folder to (in this example. "D:\PW-text-index-proxy-files"). Incorporated 166 Jun-10 . "D:\Bentley\index-storage"). open your Windows Registry Editor. modify the value of the FtrIndexCatalogDir string so that it points to the folder you just copied the existing catalog.For 32-bit operating systems. find the registry key HKEY_LOCAL_MACHINE\SOFTWARE\Bentley\ProjectWise\Automated File Processing or For 64-bit operating systems.In Windows Explorer. 3. 2.Close the Registry Editor.Under that key. This is the path to the folder where your text index proxy files currently live (for example. look at the path specified in the FtrIndexDataDir string. "D:\Bentley\index-storage"). 4. stop the ProjectWise Orchestration Framework Service.On the ProjectWise Indexing Service computer. "C:\Documents and Settings\All Users\Application Data\Bentley\index-storage\Data"). for 32-bit operating systems.Full Text Extractions so that it points to the folder you just copied the existing catalog. If you need to move just the text index proxy files 1. and copy them to the new proxy files folder you just created. stop the (Microsoft) Indexing Service. 6.In Windows Explorer.On the ProjectWise Indexing Service computer.Under that key. find the registry key HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Bentley\ProjectWise\Au tomated File Processing 5.On the ProjectWise Integration Server computer. create a new folder where you want to copy the existing proxy files to (for example. find the registry key HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Bentley\ProjectWise\Au tomated File Processing 9.wci folder to (in this example. 8.

wci folder is in the same folder as your existing text index proxy files.In the Registry Editor.Close the Registry Editor. 9.5 10. go back to the registry key HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Bentley\ProjectWise\Au tomated File Processing 11. go back to the registry key HKEY_LOCAL_MACHINE\SOFTWARE\Bentley\ProjectWise\Automated File Processing or For 64-bit operating systems. Set the value of this string to .Under the same key.  How to change the folder where documents go to be processed: 1. 8. modify the value of the FtrIndexDataDir string so that it points to the new text index proxy files folder (for example: D:\PW-text-indexproxy-files).On the ProjectWise Integration Server computer.In the Registry Editor. leave it alone for now.For 32-bit operating systems. create a new string value. If you need to move the catalog.Under that key. "If you need to move the full text index catalog". for 32-bit operating systems. modify the value of the ExtractionTempDir string so that it points to the new folder in which you want ProjectWise to temporarily store Jun-10 Copyright © 2010 Bentley Systems.Restart the (Microsoft) Indexing Service and the ProjectWise Orchestration Framework Service. Incorporated 167 Document Indexing .Under that key. and for the name. 12. 13. open your Windows Registry Editor. use the procedure above called. find the key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\ContentIndex\C atalogs\bentley_index\Scopes and delete all values under it. find the registry key HKEY_LOCAL_MACHINE\SOFTWARE\Bentley\ProjectWise\Automated File Processing or For 64-bit operating systems.. find the registry key HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Bentley\ProjectWise\Au tomated File Processing 3. 2. enter the path to the new text index proxy files folder (in this example: D:\PW-textindex-proxy-files).Full Text Extractions Note: If the catalog.

On the General tab. Enabling full text indexing The Index Server list on the General tab of the Full Text Indexing Properties dialog shows all the ProjectWise Indexing Service computers currently registered in ProjectWise Administrator for use with the ProjectWise Integration Server. it is not necessary to register the server. 4. you can click Register to register it.Full Text Extractions files downloaded during the extraction process (for example. or you can select any other system in the list. and displays as <localhost> when you open ProjectWise Administrator on the same system. Because it has Full Text Indexing installed. Incorporated 168 Jun-10 . set the following: Indexing enabled: Enabled ProjectWise User: Extraction User Password: <enter password> Note: Since the Indexing Service is running on the ProjectWise Integration Server. The system you select to register must either have ProjectWise Indexing Service or ProjectWise Integration Server with Full Text Indexing is installed. This folder will be automatically created upon the next extraction. D:\ProjectWiseExtraction-Temp-Directory). Document Indexing Copyright © 2010 Bentley Systems. the ProjectWise Integration Server itself is automatically included in this list. By default.Close the Registry Editor.  Exercise: Enable full text indexing for the datasource 1 2 In ProjectWise Administrator. If the system you want to use is not listed. You can use the ProjectWise Integration Server as your Indexing Service. right click the Full Text Indexing Document Processor in the console tree and select Properties. the Index Server is set to <localhost>. ProjectWise assumes the Index Server is on the same system as the Integration Server.

ProjectWise will check every two minutes to see if there are new. right click My Computer. In this case. enter: valve Jun-10 Copyright © 2010 Bentley Systems. 3 Select the Scheduled Updates tab. Based on the configuration specified in the previous example. 5 In the Enter your free text query below field. you’ll need to name the Integration Server explicitly. Querying the Microsoft Catalog You can also query the Microsoft Catalog directly to verify that the Indexing Server is functioning properly. Click OK. the process will hibernate until it detects that there are documents that need to be updated. localhost does not point to the Integration Server. Expand Services and Applications in the console tree. The Run radio button should be enabled. Set “Check for updated documents every (minutes)” to 2. In the schedule grid.  Exercise: Directly querying the Microsoft Catalog 1 2 3 4 On the desktop. Expand the bentley_index item and select Query the Catalog. Do this using the Microsoft Management Console. Open the Windows task manager and select the performance tab to monitor the process. you can search for ProjectWise documents by entering text on the Full Text tab of the ProjectWise Explorer Search by Form. 4 5 6 7 8 Once full text indexing has completed.Full Text Extractions If you are running the ProjectWise Administrator on a system other than the Integration Server. Expand Indexing Service in the console tree. or deleted documents. Incorporated 169 Document Indexing . enable a period of time that includes the day and time of this class by dragging the pointer across the blocks. When you see the heavy CPU usage at two minutes. modified. and select Manage from the pop-up menu.

and are formed using the ProjectWise Document GUID as the name and the extension DMSINDEX. Full text searches from ProjectWise Explorer You can use Windows Explorer and navigate to the index storage folder. Select the Full Text tab. In the Save Search dialog. These are the actual XML files. 4 5 6 At the bottom right of the search form select Saved Search > Save As.  Exercise: Executing a full text search through ProjectWise Explorer 1 2 3 In ProjectWise Explorer.Full Text Extractions 6 Click Search. Incorporated 170 Jun-10 . but before proceeding. This verifies that the Microsoft Indexing Server is functioning properly. select the Personal folder Type the saved search name: Contains valve 7 8 9 Click Save. You will see a list of documents containing the specified text. Now that the search has been saved. Click Close to dismiss the Search by Form dialog. type: valve Select “Including any of the words” from the Return documents option menu. click Advanced Search and click Search Form. Note that the file names do not match the ProjectWise document name. you find the sub-folder for each datasource for which full text indexing is enabled. Recall that the designated folder for the ProjectWise catalog is C:\BentleyFTR. the specified user account needs only Read privileges. The search is ready to run. More about full text indexing: • For full text indexing. click OK to start the search. In this folder. you can save the search so that it can be run again in the future. In the Look For field. 7 Close the Computer Management console. Document Indexing Copyright © 2010 Bentley Systems.

yet it was not processed by either of the extraction processes enabled thus far. only the master file is processed. the thumbnails are too small to be useful. change the scheduled update period so that indexing does not run every 2 minutes during class. This procedure applies to all three extraction processes. In addition to including non-standard extensions. right click Thumbnail Extraction in the console tree. you can also exclude standard file types.Processing Non-standard File Types • • • The full text index is not stored in the ProjectWise datasource. Incorporated 171 Document Indexing . Set the following: Application: <any> Jun-10 Copyright © 2010 Bentley Systems. It is necessary then. Full text searches are not case sensitive. Documents having reference files will only be indexed against the text in the master file. In order to process this file. in many cases. Exercise: Change the scheduled update interval 1 •  When you are done.sht is a MicroStationV8 file. An example would be to exclude Microsoft Word documents from thumbnail extraction because. When processing DGN and/or DWG files. Processing Non-standard File Types It is common practice to create MicroStation files with extensions other than . The File Type Association tab in the Extraction or Indexing Properties dialogs is where you do this. so database size is not affected. It is not necessary to provide a license for the MicroStation installation on the ProjectWise Integration Server.sht extension must be registered with each of the extraction processes.  Exercise: Registering non-standard file extensions 1 2 3 In ProjectWise Administrator. and select Properties. to configure all ProjectWise Extraction processes to recognize files with non-standard extensions. The file CB14. Select the File Type Associations tab. the . and click Add.dgn.

even though nothing was extracted from them. 6 Existing . Click OK to close the dialog.Processing Non-standard File Types Extension: sht Process the files as if they have the following extension: Enabled and enter dgn in the input field 4 5 Click OK. Remember. Incorporated 172 Jun-10 . and then back in Mark the entire folder for re-processing In this example. ProjectWise will not repeatedly queue files for extraction processes. Document Indexing Copyright © 2010 Bentley Systems. Select all . only to discover that it isn’t configured for the file type. For the sake of efficiency. ProjectWise clears the up-to-date flags for all indexes as the documents are checked in. At this point.  Exercise: Updating the indexes to include the sheet files 1 2 In ProjectWise Explorer and navigate to the \Document Indexing\MS-SHT folder. there are only three files that need to be re-processed. you are not required to make any changes to the file. In order to force the document to be processed again. you must do one of the following. the configuration changes are in effect and any new sht files are processed at the next regularly scheduled interval. Set the Scheduled Update period to occur in the current time period. these documents are marked in the database as having been processed. • • Check the files out. you may want to change this. It is easy to check them out and back in.sht documents.sht documents will not be included in the process because they have already been processed. More specifically. When you are done.

not thumbnail extraction. they are processed at the next regularly scheduled interval. This process is the same as previously explained for . Set the following: Jun-10 Copyright © 2010 Bentley Systems. Once the files are checked in. 6 When processing is complete. Right click and select Check In from the pop-up menu. AutoCAD files are not registered with Windows as being associated with MicroStation. In addition.sht files. The easiest way to provide full text indexing for AutoCAD files is to register them as non-standard MicroStation file types. Processing AutoCAD Documents No special configuration is required to extract thumbnails from AutoCAD drawings. Click the Saved Search named Contains valve.  Exercise: Run the saved search 1 2 In ProjectWise Explorer. select all the documents again. and then expand the Personal folder. expand Saved Searches. Incorporated 173 Document Indexing . select each of the files to verify that the thumbnails have now been extracted.Processing AutoCAD Documents 3 4 5 Right click and select Check Out from the pop-up menu. so full text indexing requires special configuration. ProjectWise will automatically extract it. right click Full Text Indexing in the console tree and select Properties. In this case. Select the File Type Associations tab. Once checked out. and click Add.  Exercise: Registering the DWG extension for full text indexing 1 2 3 In ProjectWise Administrator. You should also verify that the sht file extension was correctly configured for full text indexing. so the extraction process will not send these files to the MicroStation extraction engine by default. it is only necessary to register the extension for full text indexing properties. AutoCAD files are not recognized by the Microsoft Indexing Server. When a thumbnail exists in an AutoCAD file.

The Windows file system defines a common set of attributes for all files such as Filename. the list of attributes available for a given file may vary from file type to file type. metadata stored in the file header in the Windows file system can be imported into ProjectWise. Incorporated 174 Jun-10 . When processing has completed. Size. and then check them in. but will only affect new documents. When importing these properties into ProjectWise. Document Indexing Copyright © 2010 Bentley Systems. Windows provides API’s for application programmers to extend the standard attribute list. File Property Extraction With this capability. and then check them in.  Exercise: Verifying the DWG extension 1 2 3 4 5 In ProjectWise Explorer. Modified (date). and Accessed (date). Check the documents out. The new rule appears in the list.File Property Extraction Application: <any> Extension: dwg Process the files as if they have the following extension field: Enabled and type in dgn 4 Click OK. Check the documents out. this will vary from application to application. navigate to the \Document Indexing\AC-14 folder. Therefore. Navigate to the folder \Document Indexing\AC-2000. the administrator must decide which properties are worthwhile and which should be discarded. Again. In addition. Created (date). Extracted file properties data displays on the File Properties tab on the respective file's Document Properties dialog in ProjectWise Explorer. Click OK. 5 The configuration changes are immediately active. run the saved search to find all drawings containing the text valve. and can be searched on like any other property from ProjectWise Explorer's Search dialogs.

• Enabling file property extraction in ProjectWise is a simple process. so you may be tempted not to import this information. etc. enable all periods for file property extraction Check for updated documents every (minutes): 2 4 5 Click OK. or deleted documents. you can maintain both. Edit Time. It shares all the common configuration parameters discussed previously for thumbnails and full text. the document created date is the date the file was imported into ProjectWise. Based on the configuration specified. Therefore. Set the following on the General tab: Extraction enabled: Enabled ProjectWise User: extraction Password: <enter password> 3 Select the Scheduled Updates tab and make the following configuration changes: On the schedule. Incorporated 175 Document Indexing .File Property Extraction Some of the Windows metadata may not be useful in ProjectWise. right click File Property Extraction in the console tree. ProjectWise does not maintain a file created date. and select Properties. Keywords. When processing is complete. there are many reasons why it may be advantageous to import key Windows metadata fields.  Exercise: Enabling file property extraction 1 2 In ProjectWise Administrator. File property extraction differs only in that the administrator must also specify which attributes to extract. you can view the results by selecting various documents in ProjectWise Explorer. the date the file was actually created is inaccessible from ProjectWise. ProjectWise will check every two minutes to see if there are new. With file property extraction. MicroStation has custom metadata fields for Title. Subject. • When existing documents are imported into ProjectWise. and in what order to display them. the process will hibernate until it senses that there are documents needing to be updated. However. Jun-10 Copyright © 2010 Bentley Systems. which to display. However. Extracting this data into ProjectWise makes it searchable and potentially reportable. and viewing their properties. modified. Once file property extraction has completed. this information cannot be used in the Windows Find Documents dialog.

verify the files by viewing their properties. right click CB1. Incorporated 176 Jun-10 . This can be reviewed by selecting the Property Sets item from ProjectWise Administrator. Document Indexing Copyright © 2010 Bentley Systems. Close the Document Properties dialog. Select the File Properties tab. The order number specifies the order in which these items will appear in the ProjectWise Explorer File Properties dialog. 3  Exercise: Importing additional documents for file property extraction 1 2 In ProjectWise Explorer. You can reorder the items simply by changing the order number. You will see the entire list of properties stored with a MicroStation V8 file. and drop them. select Document Summary Information. When the first file of each new type is processed. select Summary Information. You see items named Summary Information and Document Summary Information. All extraction processes will process the new files during the next regularly scheduled update.dgn. You see a composite list of all attributes found under this heading for all document types. 3 In the console tree. select Property Sets under File Property Extraction. 2 In the console tree. In Windows Explorer. navigate to the \FilePropertyExtraction folder in the class data set.  Exercise: Reviewing and configuring Property Sets 1 In ProjectWise Administrator.File Property Extraction  Exercise: Reviewing file properties 1 2 In ProjectWise Explorer. Note that MicroStation versions prior to V8 did not support the COM Structured Store format so you can’t extract properties. ProjectWise establishes a place in the datasource to store the custom attributes associated with the file type. create a new root level folder named FilePropertyExtraction. You will also see an Order number column. 3 Once processing is complete. drag the files from that folder into the new ProjectWise folder. and select Properties. navigate to the folder \Document Indexing\MSV8.

You can confirm this by viewing any document’s file properties from ProjectWise Explorer. It does not include text. In the document view. Incorporated 177 Document Indexing . File Read. and then reorder the remaining items. File property extraction is limited to file types supporting the COM Structured Store concept. right click Date Created and select Properties. This is an example of an item that you may want to move to the top of the list. You can then modify the list as appropriate for your organization. you will have to force them to be updated. In the console tree. It is recommended that the administrator import one file from each type and allow the file property extraction to run. and then click OK. 900. AutoCAD. This is an example of an item that is used internally by some application. PowerPoint. The exact impact on the database size is proportional to the number and size of the properties extracted. It also includes common Microsoft formats such as Word. select Summary Information. and Write privileges. The Do not extract setting is effective immediately. but will have no effect on documents already indexed. Afterwards. select Properties. 9 To do this. in the Order Number field and click OK. and Excel. These changes are a sample of the many configuration possibilities. but not MicroStation/J or earlier. for example. • • • Jun-10 Copyright © 2010 Bentley Systems. In addition. More about file property extraction: • For file property extraction. 4 5 Select Link Dirty? From the right click menu.File Property Extraction You see a composite list of all attributes found under this heading for all document types. or common raster formats. This includes MicroStation V8. An administrator should further define the File Property Sets to remove all unwanted attributes. File properties are stored in the ProjectWise datasource. enter a number that is less than any current order number. html. 6 7 8 Enable Do not extract. the specified user account needs Read. the Property Sets are populated with all attributes found in any of the document types. the user properties setting Document -> Modify must be enabled. It is most likely of no value to ProjectWise users. The reordering operation is effective immediately. To see the effects of this setting on existing documents.

open the Automation Service Administrator by selecting Start > Programs > ProjectWise V8i > Automation Service > Automation Service Administrator. Once connected. For details on installing this item. Select Connections > Connect > Orchestration Framework Browser. In order to monitor extraction processes. right click Instances. Select the Details tab. the ProjectWise Orchestration Framework Service was installed prior to the ProjectWise Integration Server. It is not necessary to use the Hidden setting in combination with Do Not Extract to hide the item. and select Monitor. there are no documents that need to be updated. install the ProjectWise Automation Service Administrator. It should not be necessary to establish extension mapping rules for file property extraction. In order to support document processing.  How to set up for monitoring: First. and any other ProjectWise components. • • Monitoring Extraction Processes So far. the Automation Service Administrator will update to reflect the new connection. In the console tree. This tool can be installed on any system if the prerequisites have been met. right click the desired Document Processor and select Mark Folder Documents for Reprocessing. Document Indexing Copyright © 2010 Bentley Systems. During this installation. ProjectWise provides the Automation Service Administrator for monitoring extraction processes. Then. see the ProjectWise Installation Guide delivered with the software.  How to mark a folder for re-processing: In the ProjectWise Administrator console tree.Monitoring Extraction Processes • Use of the Do Not Extract item causes the attribute field to be removed from the properties dialog. Incorporated 178 Jun-10 . you monitored the extraction processes using the Windows task manager. a database was created for storing extraction queue definitions. Right now. All Com Structured Store file types should be recognized regardless of their extension. The Hidden setting should be used when you want to extract an attribute but do not want to display it to the user. This database is independent of the ProjectWise datasource. You’ll mark the entire folder structure for re-processing. you must connect to that database now. You are now ready to monitor the full text indexing process.

In the Mark Folder Documents for Reprocessing dialog. then they should be removed from the user’s view. the up-to-date flag for full text indexing for all documents will have been cleared. If one or more extraction features are not implemented for your ProjectWise datasource. Incorporated 179 Document Indexing . and then click OK. Therefore. and then click OK. These settings determine which tabs to display in the ProjectWise Explorer Document Properties and Search by Form dialogs. the desired folder. and then choosing Start Processing Now from the right click menu. and select. all documents are processed at the next regularly scheduled update. It is best not to make a license available on the server so that this does not happen. Note: You can start processes at any time by selecting the item in ProjectWise Administrator. it will use the license when indexing.File Extraction User Properties Settings Navigate to. Jun-10 Copyright © 2010 Bentley Systems. Return to the Automation Service Administrator and watch for items to process through the queues. enable Include subfolders. User Interface category The User Interface category provides settings to limit the display of extracted information. File Extraction User Properties Settings There are categories of user properties settings that apply to file extractions. Note: If you license MicroStation on the Integration Server. After completing these steps.

Disabling this setting will remove it from the Search by Form. Documents having reference files will only be indexed against the text in the master file. Document Indexing Copyright © 2010 Bentley Systems. Show full text search: Full Text Search does not appear on the Document Properties dialog since it has no meaning there. only the master file is processed. • • Module Review Now that you have completed this module. Incorporated 180 Jun-10 . These items are displayed on the File Properties tab. let’s measure what you have learned. What must you do to force documents to be processed again? Which of the following can you extract from AutoCAD files with no additional configuration? Thumbnails Full text File properties 6 7 8 Name two ways to monitor extraction processes. Show document thumbnail: Document Thumbnails appear only in the Preview pane of ProjectWise Explorer and not as a tab on the Document Properties dialog. Disabling this item will remove the tab from the dialog. where is the actual text index stored? Where does the Indexing Service run? True or False: When processing DGN and/or DWG files. Questions 1 2 3 4 5 What must be installed to install any of the document processors? When you create a user account for the extraction user.Module Review • Show file properties: File properties appear in the ProjectWise Explorer Document Properties dialog. which user properties setting should be disabled? When you extract full text. Disabling this setting will remove the thumbnail from the preview pane.

Module Prerequisites • • • Knowledge about ProjectWise Explorer’s interface Knowledge about document architecture Knowledge about user accounts Module Objectives After completing this module. This module discusses its implementation and use. you will be able to: • • • • Enable Audit Trail for a datasource Perform Audit Trail maintenance Retrieve datasource statistics Set Audit Trail User properties settings Jun-10 181 Copyright © 2010 Bentley Systems. In order to take advantage of it. Audit Trail is disabled by default. Since it has the potential to track all access of all types and for all documents. it must be enabled on a per-datasource basis. Incorporated Audit Trail . It stores all document access data in the ProjectWise datasource.Audit Trail Module Overview The Audit Trail feature allows the system to track and record all access to documents. For this reason. this feature can quickly accumulate large amounts of data.

• • Document: This category provides access to all settings regarding document transactions. In the datasource properties dialog. some document transactions roll-up to the folder. Incorporated 182 Jun-10 . Document ID’s are said to be globally unique. Folder: This category provides access to all settings regarding folder transactions. Audit Trail Copyright © 2010 Bentley Systems. Datasource settings The Audit Trail datasource settings are divided into categories as follows. you will enable Audit Trail and execute steps that generate Audit Trail data. In the following exercises. Questions 1 2 3 What is an abstract document? What is a GUID? Where do you set datasource properties? Answers 1 2 A document that has no file associated to it. In addition. Right click a datasource and select Properties from the pop-up menu to open it. Every document is assigned an identification number within ProjectWise. and are thus often referred to as GUID’s.Introductory Knowledge Introductory Knowledge Before you begin this module. This can help you to determine which settings are best for your production system. let's define what you already know. 3 Enabling Audit Trail for a Datasource An administrator should carefully plan the implementation and decide how much information should be retained prior to enabling this feature.

Keep in mind that all Audit Trail information is stored in the datasource. once established. • Each of these categories contains global settings for the datasource. Click the Settings tab. are seldom changed. enable the following: Log Document Create. Copy out) Log Document Workflow/State change Log Document Version change Log Document Delete 5 In the Folder category. if necessary. enable: Log Create Jun-10 Copyright © 2010 Bentley Systems. Truncating: This category provides access to Audit Trail maintenance settings. 3 4 Expand the Audit Trail category. Document sets are most commonly created when reference file attachments are made from CAD applications. Incorporated 183 Audit Trail .Enabling Audit Trail for a Datasource • Document Set: This category provides access to all settings regarding document set transactions. Access them by selecting Properties for the datasource itself in ProjectWise Administrator. Modify. These settings can be revised in the future to limit the amount of data. right click the datasource in the console tree and select Properties. These settings are in effect for all users and. and Move Log Document Check in Log Document Access (Export) Log Document Access (Check out. You must now decide which events will be tracked. In the Document category.  Exercise: Enable Audit Trail for the datasource 1 2 In ProjectWise Administrator.

leave all settings disabled. enabled. users are prompted for additional comments each time an event occurs. Enable Allow user to change audit trail settings Expand the Comments category. Navigate to Folder A. but like required environment fields. It is the administrator’s option to accept this behavior or modify it so that event logging is completely transparent. The administrator does have the option to require comments. In the Truncating category. Open the Properties dialog for user1. expand the Audit Trail category. From this point forward.  Exercise: Reviewing user properties settings with Audit Trail enabled 1 2 3 4 5 In ProjectWise Administrator. Click OK. 6  Click OK. With this combination of settings users have the opportunity. Routinely logged events An event is logged whether users enter comments or not. Note that the Require comment item is disabled. all events enabled in the exercise will be logged in the datasource. By default. On the Settings tab. When a user performs one of these operations. The Comments settings are now available and enabled for all events that were enabled for the datasource. Over use of required fields and comments may result in avoidance of the system. Exercise: Enter or skip Audit Trail comments 1 2 Log in to ProjectWise Explorer as user1. Audit Trail Copyright © 2010 Bentley Systems. but will not be forced to. select Users in the console tree. this option should be used sparingly. enter comments. Audit Trail is now enabled for the datasource. Incorporated 184 Jun-10 . “Keep all records”. they are prompted for comments. leave the default setting.Enabling Audit Trail for a Datasource Log Modify Log Delete 6 7 8 In the Document Set and User categories.

Right click on the first document and check it in. Right click on the first document and check it in.Enabling Audit Trail for a Datasource 3 4 Right click on the first document and check it out. Jun-10 Copyright © 2010 Bentley Systems. • • The file is marked as checked in. Freeing documents and Audit Trail A document may be checked out checked and back in without any changes being made. Right click on the first document and check it out. where a document has been checked out but no changes were made. even though the event is tracked in the Audit Trail. 5 6 7 8 9 If Require Comment is necessary for certain operations. The Audit Trail event will still be recorded. There are several advantages to this. type: No changes Click OK. If Require Comment is enabled. If a user checks out file for quality review and discovers no changes are necessary. but selected Check Out instead of View. but not transferred back to the server. Because the Audit Trail -> Comments -> Require comment user properties setting is disabled. this time click OK without entering a comment. If a user wanted to view the file. This saves network traffic and increases performance. you were able to complete the operation without entering a comment. • • • If a user checks out a file and discovers that it is not the intended document. The Check in dialog’s Comments tab appears. but there will be no prompt to enter comments. In the Comments field. In any case. consider disabling Allow Comments for settings that do not require comments. the user should opt to Free the document rather than checking it in. Incorporated 185 Audit Trail . the user will not have to enter comments because the Free command is not eligible for comments. When prompted for comments.

user. right click on the first document and check it out. they can Free the document and then check it out again. You are not prompted by Check In Document dialog. or date. Audit Trail review The first document in folder A now has transactions in the Audit Trail. Incorporated 186 Jun-10 . The Customize option lets you limit the report by action type. Hint: Delimited text files are useful for importing into other applications such as Microsoft Excel. by displaying the Audit Trail for the folder. The Audit Trail report for the document is retrieved from the datasource and displayed in the Properties dialog. and when. Audit Trail Copyright © 2010 Bentley Systems. Deleted documents In addition to document access records. right click the first document and select Properties. In this case. 3 Close the Document Properties dialog. Select the Audit Trail tab. Exercise: Using the Document Free command 1 2 3  In ProjectWise Explorer. you can use the Audit Trail to determine who deleted a document. click Yes to free the document. so you can review the history of the document. When prompted. in Folder A. in Folder A.  Exercise: Reviewing the Audit Trail 1 2 In ProjectWise Explorer. From the Audit Trail report display you can Save as an HTML page or text file and Print to an available printer. Select Document > Free.Enabling Audit Trail for a Datasource • A user may have made changes to a file but they need to revert it back to the state it was in before they checked it out.

expand the Audit Trail category. This minimizes the report since the document was deleted.  Exercise: Reviewing the Audit Trail for deleted documents 1 2 3 In ProjectWise Explorer. This Audit Trail report displays all transactions for all documents in the folder.Log Logouts If these are enabled. click Yes to delete the document. Open the Properties dialog for folder A and select the Audit Trail tab.Enabling Audit Trail for a Datasource  Exercise: Displaying the Audit Trail for a folder 1 2 In ProjectWise Explorer. On the Settings tab. not all users should be granted the ability to view this tab. 4 Close the Folder Properties dialog. Jun-10 Copyright © 2010 Bentley Systems. right click the first document in folder A and select Delete. Frequently viewing a folder Audit Trail with many transactions can have an adverse effect on performance. select Tools > Options. 3 4 5 Make sure that “Enable Show Audit Trail tab in Folder Properties window” is enabled and click OK.Log Logins and User . Incorporated 187 Audit Trail . 6 Close the Folder Properties dialog. Where the Audit Trail report formerly included all transactions for the document. an entry is added to the audit trail log whenever a user logs in or out of this datasource. The settings here control display of the Audit Trail tab in the Document and Folder Properties dialogs. Right click on folder A and select Properties. it now only includes the deleted transaction. When prompted. Additional datasource settings Audit Trail->User . Select the Audit Trail tab. Hint: Since a folder Audit Trail can involve large amounts of data.

When this setting is on. Each organization or project team will need to decide how long this data should be maintained in accordance with the organization’s records management policy.Audit Trail Maintenance Audit Trail-> Truncating . Double click the first hourglass to set how many days. Incorporated 188 Jun-10 . In the dialog that opens. Audit Trail Maintenance ProjectWise provides database settings for managing Audit Trail data and limiting it to a reasonable size. will be moved to the table specified.Truncate Type Keep records for specified period specifies how long you would like to keep the audit trail records. To specify the secondary audit trail table to use. and/or seconds to keep the records. turn this option on and click the pencil icon. audit trail truncation runs every hour on the Integration Server when the server has idle time. Keep all records if enabled. enter a name for the secondary audit trail table and click OK. This configuration category provides a mechanism Audit Trail Copyright © 2010 Bentley Systems. the oldest records will be deleted until the number of records is reduced to the maximum again. when purged from the main audit trail table in the database. If off. If the table does not already exist in the database. Once the specified number is surpassed. all records in the audit trail will be kept. Keep specified number of records specifies how many records you want to keep in the audit trail at one time. There is no general rule for determining the right amount of data to keep. Truncating the Audit Trail Audit Trail maintenance settings are found under the Truncating category in the datasource Audit Trail settings. it will be created as necessary when the records expire. Audit Trail-> Truncating If move truncated records into secondary table is on. or years to keep the records. minutes. months. the audit trail records. then audit trail records will be permanently deleted when they are removed from the main audit trail table. Double click the second hourglass to set how many additional hours.

this item lets you limit the total size of the audit trail. or Years. all Audit Trail transaction data is stored in the primary audit trail table in the database. Months. The time can be specified in Days. Double click the icon in the input field under the option to open the Enter Period dialog. This is accomplished by specifying the number of records to keep. Incorporated 189 Audit Trail . If it is during an active period of ProjectWise use. Keep records for specified period This setting lets you specify the time period for keeping Audit Trail records. Keep all records Enable this to keep all records. or discarded.Audit Trail Maintenance either to limit the total number of records. Keep specified number of records Rather than specify an expiration time value for audit trail records. Jun-10 Copyright © 2010 Bentley Systems. when they are older than the specified time. individual records are truncated. With this setting in effect. the oldest records are truncated until the number of records is within the specified limit. you may want to add 8 or 12 hours so the purge occurs during an off period. When the audit trail record count exceeds this value. or to limit the amount of time they are kept. Hint: Think about the time at which you are setting this. With this setting.

set the time period to 180 days. truncation moves at most 50. Audit Trail Copyright © 2010 Bentley Systems. Enable the setting Move truncated records into secondary table. Incorporated 190 Jun-10 . Select the Settings tab. rather than discarding them. Truncating sub-category. set Truncate Type to Keep records for specified period. When records are moved to the secondary table. While not available through ProjectWise Explorer. if the move to the secondary table is unsuccessful. double click the hourglass. In the Audit Trail category. This value can be modified per datasource using the following SQL statement: UPDATE dms_gcfg SET o_intval=newMaxValue WHERE o_paramno=147 Move truncated records into secondary table This setting lets you transfer truncated records to a secondary audit trail table. This setting can be used in combination with either of the other truncation modes. When enabling this option it is necessary to specify a new table name. Note: When audit trail truncation runs. double click the pencil icon to enter a table name.000 rows per hour to avoid performance issues. It is not necessary to create the table. Click OK. This helps maintain a reasonable level of performance without actually discarding the data. In the Enter period dialog.Audit Trail Maintenance Note: By default. ProjectWise will create this table for you. they can no longer be retrieved through ProjectWise Explorer. these records can still be viewed or reported on through direct database access. Underneath the setting.  Exercise: Defining Audit Trail maintenance rules 1 2 3 4 5 6 7 8 In ProjectWise Administrator. with the proper schema to store audit trail data. open the Properties dialog for the datasource. Under the setting. ProjectWise will not delete the unmoved records from the dms_audt table.

The statistic update time is displayed in the bottom left corner of the tab. You can view various datasource statistics such as Number of Users.Datasource statistics 9 In the Enter text value dialog. they only reflect information about the database. and then click OK. By default. The Statistics tab shows the statistics of the datasource based on the last time statistics were updated. You can also manually update the statistics by clicking the Refresh button on the Statistics tab. Incorporated 191 Audit Trail .  How to update statistics: To manually update the statistics.xml. during which time you will be unable to use ProjectWise Administrator. Or. Maximum Documents Per Folder. but this can be changed through the StatisticsFrequency setting in the Integration Server's dmskrnl. Refreshing statistics can take a few minutes for large datasources. Jun-10 Copyright © 2010 Bentley Systems. during which time you will be unable to use ProjectWise Administrator. click the Refresh button on the Statistics tab. The new settings are now in effect and audit trail records older than 180 days are moved to a secondary table named audit_secondary. . These statistics can be exported in .cfg file. or . statistics are updated every 12 hours. Items With Audit Trail. Note that refreshing statistics can take time for large datasources. but will be created by ProjectWise when it is needed. This table has not been created yet.cfg file and change the StatisticsFrequency setting which is in the general server configuration information section. The statistics do not have anything to do with the storage device.csv. 11 Click Apply.txt format. enter: audit_secondary 10 Click OK. Datasource statistics Since a ProjectWise administrator is often not a DBA. etc. you can see statistics about the datasource on the Statistics tab in the datasource Properties dialog. you can open the Integration Server's (\Program Files\Bentley\ProjectWise\bin) dmskrnl.

this user can change the settings for the Audit Trail. Comments Allow user to change comment settings When enabled.Audit Trail User Properties Settings Audit Trail User Properties Settings Now that Audit Trail settings are in effect for the datasource and have been exercised. Audit Trail Copyright © 2010 Bentley Systems. This functionality is found on the Users tab of the Audit Trail Customize Report dialog in ProjectWise Explorer. See private actions When enabled. Reports Allow user to change report visibility settings When enabled. users can change the settings for Comment usage. users can include the user’s own actions in the Audit Trail report. Incorporated 192 Jun-10 . users can include other users’ actions in the Audit Trail report. users can see the Reports item in the Audit Trail category. you should reexamine the default user properties settings you can set in ProjectWise Administrator. Allow user to change audit trail options When enabled. letting them determine which reports will display. See actions of other users When enabled.

When disabled. users are prompted to enter comments when setting final status on documents. users cannot enter comments when checking in or importing documents. Allow comments for state change When enabled. Allow comments for version create When enabled. Require comment When enabled. users are prompted to enter comments when checking in or importing documents. Allow comments for final status change When enabled. Jun-10 Copyright © 2010 Bentley Systems. users are prompted to enter comments when changing the State of documents.Audit Trail User Properties Settings Allow comments for check in When enabled. Can delete audit trail records When enabled. the user can delete audit trail records from the database. Incorporated 193 Audit Trail . Delete Rights Allow user to change delete rights settings When enabled. The Clear Audit Trail item is added to the Folder and Document menus for that user. users are prompted to enter comments when creating new versions of documents. users will not be allowed to carry out the action without entering comments. the user can change the settings for Delete Rights.

Audit Trail Copyright © 2010 Bentley Systems. the Audit Trail tab displays in the Folder Properties dialog. Questions 1 2 3 4 True or False: Users must enter comments for Audit Trail events to be logged. True or False: If Require Comment is enabled. log out of ProjectWise Explorer. Why might you want to limit the number of users who can view a folder’s Audit Trail? True or False: If you elect to move audit trail records to a secondary table.Module Review Show Audit Trail tab in Document Properties window When enabled. Module Review Now that you have completed this module. you must first create the table in the database. the Audit Trail tab displays in the Document Properties dialog. Incorporated 194 Jun-10 .  Exercise: Log out of ProjectWise Explorer 1 When you are done with this module. users can’t use the Free command. let’s measure what you have learned. Show Audit Trail tab in Folder Properties window When enabled.

It determines which users can see which documents and folders. you will be able to: • • • Select an approach to access control Understand and implement object security and workflow security Set user and datasource settings related to access control Introductory Knowledge Before you begin this module. This module examines the different types of access control and their application. let's define what you already know. Incorporated Access Control . and what those users are permitted to do with those documents and folders.Access Control Module Overview Access control is the means by which ProjectWise enforces security in the datasource. Module Prerequisites • • • Knowledge about the ProjectWise Explorer’s and ProjectWise Administrator interface Knowledge about document architecture Knowledge about user accounts Module Objectives After completing this module. Jun-10 195 Copyright © 2010 Bentley Systems.

The various levels of access rights allow you to control access broadly. While ProjectWise can handle complex security settings. no access control settings are configured. When you create a new user. Access Control Overview When a datasource is first created. In ProjectWise Explorer. Access Control Copyright © 2010 Bentley Systems. and workflow states. workflow and state. Regardless of where you set security. Security in ProjectWise is exclusive. or narrowly by assigning rights according to each folder. Create this user first with the most appropriate settings for most users. therefore all users you create will have access to all folders and documents in the datasource. Where are these rights defined? Why is it important to define a default user? Answers 1 2 These rights are listed in the Folder and Document categories of the user properties settings. add the users whose access permissions you want to configure. across all states or folders. the method is basically the same. and on either the Folder or Document Security tabs. fewer security settings result in better performance when creating new folders or changing security settings. Security can be applied in various places In ProjectWise Administrator. It is only applied when some users are explicitly given permissions to certain items that other users are excluded from accessing those items. workflows. they inherit settings from the default user.Access Control Overview Questions 1 2 Within ProjectWise. You open the Properties dialog for the item. It can be applied globally to the datasource. security can be applied to specific folders and documents. Incorporated 196 Jun-10 . each user has rights to perform particular operations based on their user properties settings. and to specific environments.

and workflow security. at any level in ProjectWise Explorer. that user would not be able to delete documents in any folder in the datasource. it automatically inherits the permission set from the previous level. This permission set can then be edited and will become the object’s own permission set. Then. you set workflow#1 so it is only accessible to certain users in the datasource. For example. this strategy is very restrictive. If the administrator were to take away document Delete rights for a user. also referred to as object security hierarchy if your datasource is not workflow driven. These rights are listed in the Folder and Document categories of the user properties settings. As each new level is created. and then selectively take them away at the folder or individual document level. Incorporated 197 Access Control . folder and document permissions can be set for the entire datasource in ProjectWise Administrator. consider combining user rights with Document. each user has rights to perform particular operations based on their user properties settings. also referred to as workflow security hierarchy. The administrator typically assigns document and folder security. In ProjectWise Administrator. Any folders. Note: User rights override folder. and stateD. you can use a workflow-based approach to access control. say that workflow#1 has stateA. stateB. Users are rarely given the right to change these settings. you can grant Delete rights at the user level. Note: A document that is not part of a workflow. new permissions can be set which the lower levels inherit. while providing more flexibility. then from the environment if any. It is important to understand that these settings apply to all folders and all documents within the datasource. then from any parent folder. As an alternative. Using this strategy. Folder. Then you can decide which of those users have access to each Jun-10 Copyright © 2010 Bentley Systems. While effective. • If your datasource is workflow driven. stateC. will inherit its permissions from the folder it is in. Security Permissions • Use an object-based approach. This strategy is equally effective. or Workflow Security to determine a user’s final access rights. ProjectWise searches for permissions from the bottom up.Security Permissions Within ProjectWise. they cannot be given back at the folder level. If rights are removed at the user level. sub-folders and documents in ProjectWise Explorer will inherit these permissions. and has no permissions applied. document. and then from the datasource. In this approach.

Folder security In order to complete these exercises. With this model. but read/write in the Edit state. its state. as it allows an administrator to define an access control list for each folder or document. and what permissions each user has for folders or documents in that state. then the document folder’s workflow and state. the folder and document security you defined for it will be applied to the selected folder and its documents. The access control list for a document changes as the document moves through the states in the workflow. With workflow security. the ACL for any given document will not change unless an administrator explicitly changes it. but it actually sets security for the folder and the documents in it.The Object Security Hierarchy state in the workflow. Its workflow. Incorporated 198 Jun-10 . Create a root level folder named Security Project. In contrast to folder security. the access control list for a document object is determined by the current state of the document within the workflow. Document security functions like folder security. It is very similar to Windows security. In other words. the ACL for any given object (folder or document) remains constant throughout the life cycle of the object. a document will inherit permissions from top to bottom. The difference is in the permissions available to be assigned to documents in a folder. Hint: Using the workflow-based approach. editors have read-only permission in the Drafting state. then any parent folder’s workflow and state. Access Control Copyright © 2010 Bentley Systems. The Object Security Hierarchy Folder security is applied at the folder level. workflow security is a dynamic security model.  Exercise: Add folders to the datasource 1 2 Log in to ProjectWise Explorer using the administrative credentials. When workflow#1 is assigned to a folder in ProjectWise Explorer. additional folders are needed. For example. Think of folder security as a static security model.

When a Workflow is assigned to the folder. When the access control list is empty. all users have full access to the folder. The icons differ for the various object types. including sub-directories. Assigning security to a folder To assign security to a folder. This includes the Users. The Select Security Objects dialog lists all users. or items inherited from the Object Security hierarchy. it defaults to Real. The Document Security tab provides access to the security settings for documents in the folder. This list can contain items that are the folder’s own. groups. modify. • The Project\Folder Security tab provides access to a folder’s. and delete folders. it indicates that no security schema has been defined for this folder. In ProjectWise Explorer. right click the Security Project folder and select Properties. That includes security explicitly assigned to the folder or security inherited from a higher folder in the hierarchy. and User Lists who can create. or project’s. the Inherited from field indicates if the security is the folder’s own or if it is inherited from another folder. security settings. In this case. and user lists defined in the datasource. select the Project\Folder Security tab and click Add.The Object Security Hierarchy 3 4 Navigate to the Security Project folder in the class data set and copy the sub-folders to the ProjectWise Explorer folder. Just above the access control list. • The Security Type item on both tabs shows the current security mode. The option defaults to Folder when no Workflow has been assigned to the folder. Jun-10 Copyright © 2010 Bentley Systems. Incorporated 199 Access Control . The Name pane is the access control list for the folder. Groups. • A single head represents an individual user.

The following example shows the same datasource for two different users. Then you can select the individual or group that needs access to the folder. Incorporated 200 Jun-10 . When a user has no access to a folder. It can be seen by everyone. The drafter does not see the \Borders folder. they are automatically a member of the Everyone group. • When you click the Add button. So if the folder to which a user has no access contains text documents. administration of the datasource becomes more cumbersome because you must change security whenever a user’s role changes. Always click OK to add the selections first. Important: When assigning security. any users not included in the access control list are denied access to the folder. and they execute a search for *. and the sub-folders have inherited the permissions. A drafter sees the folders on the right. Hint: If you shift between the display filters. It might be easier to think of this group as the Everyone Else group. they cannot even see the folder in ProjectWise Explorer’s datasource list. you can enable or disable permissions in the right pane. As soon as you add a security object to this dialog. Note that the contents are open to search.The Object Security Hierarchy • • The double head represents a user group.txt. you will lose your selections. Everyone is a special user group created automatically by the system. they will find the documents. This special group doesn’t display in the Administrator console. When you select a name in the access control list. Whenever you create a new user account. The head beside a paper stack represents a user list. When you assign security to individual users. the List items of type option list lets you filter the security objects to display one of these types. The following images show the security schema for the\BSI400 folder. An administrator sees the folders on the left. It is much easier to move users between groups when their roles change. Note the Access Control Copyright © 2010 Bentley Systems. it is best to assign security to Groups or User Lists.

The exception to this rule is the No access permission. With Change Workflow State. users can perform every folder function. users can modify folder properties. Anyone can at least review documents. users whose user setting Document -> Change State is on can change the states of documents. With Read. The administrative user has Full control. • • • • • • • • • With Full control. Hint: Always include the Everyone group when developing a security schema. the user has no access to the folder. With Free. With No access. Adding Everyone with Read privileges insures that all users can at least see all folders. then their cumulative rights are the most permissive. This is good if there is no sensitive material in the folder.The Object Security Hierarchy Read permission for the Everyone user. With Create subfolders. With Change permissions. Incorporated 201 Access Control . The Management user group was given additional Write and Create subfolders. users whose user setting Document -> Free is on can free documents that are checked out or exported by other users. If a user is a member of more than one group. If any one Jun-10 Copyright © 2010 Bentley Systems. With Delete. the folder is visible. users can create sub-folders. users can delete folders. Folder permissions Folder permissions work as follows. permissions. users can change folder permissions. With Write.

Those with security set explicitly for them are left alone. It offers two options. Incorporated 202 Jun-10 . Access Control Copyright © 2010 Bentley Systems. The controls are the same as those on the folder properties dialog’s Project\Folder Security tab. Note: Remember to take the user’s rights. Sub-folders that inherit security from this folder will inherit the new security automatically. Document security Document security functions like to folder security. Sub-folders that already inherit from this folder will inherit the new security automatically. even if they are listed in the access control list as having Delete access for a folder. Explicit security on those sub-folders is removed and replaced with the new schema. Warning: The No access permission takes priority over all others. The difference is in the permissions you can assign to documents in a folder. into account. as defined in their user properties settings. Explicit security is removed from the sub-folders and is replaced by inherited security.The Object Security Hierarchy of the groups to which a user belongs is assigned No Access. that user’s cumulative rights equal No access. a dialog appears. they cannot delete a folder. These are set on the Security tab of the document properties dialog. If you select the second option. If a user does not have Folder-Delete rights. Apply changes to this folder and subfolders: This option applies the new security setting to the currently selected folder and to all of its sub-folders. • Apply changes to this folder only: This option applies the new security setting to the currently selected folder. Document permissions The basic document permissions are the same as folder permissions. Sub-folders that have explicit security of their own are unchanged. Applying security to sub-folders When you apply security to a folder that has sub-folders. • To achieve true inheritance. the new security will be applied to the parent folder and all sub-folders. Both sub-folders with inherited security and sub-folders with explicit security will inherit this security. select the first condition.

They can also open the file read only. Incorporated 203 Access Control . After you set security for the Security Project folder. change permissions. • File Read: Users can open the file associated with the document in Read-only mode. delete. File Write: users can modify the file associated with the document. Typically. they can see the document in ProjectWise Explorer and modify its properties in the properties dialog. it is a good idea to create a security schema using a spreadsheet. In this example. read. assign Folder security to each folder on the Project\Folder security tab of its properties dialog. the Everyone group becomes the baseline group and only groups that need permissions other than those assigned to Everyone are granted. • Note the differences in these permissions. you might opt not to add the design group because its permissions are the same as that of Everyone. You can check out the document. With File Read permission. but not check it out. if you apply the changes to this folder and subfolders you will only have to change some Jun-10 Copyright © 2010 Bentley Systems. With File Write permission. Enter the groups in the top row horizontally and create the directory structure vertically.  Exercise: Assign security to a folder structure 1 Continuing in ProjectWise Explorer. make changes. They can also open it. write and no access. They cannot see the content of the file. according to the following matrix. You can copy out the document. they can see the document in ProjectWise Explorer and see its properties in the properties dialog. Then assign security to each group. Organizing object security Prior to applying security to a folder structure. users can see the document in ProjectWise Explorer and see its properties in the properties dialog. When you actually apply the security in the folder properties dialog. With regular Read permission. With regular Write permission. and modify its content. and check it back in.The Object Security Hierarchy They are full control. you use the spreadsheet as a guide. users can see the document in ProjectWise Explorer and see its properties in the properties dialog. there are two additional permissions. However. They cannot modify the content of the file.

Note: Note that FC indicates Full control. Had the Drafter user not been a member of Design. However. 5 In the previous exercise. Verify the security schema by browsing the folders while logged in as Drafter. Verify the security schema by browsing the folders. Enabling File Read enables the Read permission automatically.  Exercise: Create a new sub-folder 1 In ProjectWise Explorer. so the user is granted permissions accordingly. the Drafter user is a member of the Design group. and comparing the directory structure. 2 On the Document Security tab for each folder. assign permissions according to the following matrix. Incorporated 204 Jun-10 . FR is File Read. and enter the following: Name: Plots Access Control Copyright © 2010 Bentley Systems.The Object Security Hierarchy settings as indicated in the matrix. enable the Apply changes to this folder and subfolders radio button and click OK. W Write. C indicates Create subfolders permission. and FW is File Write. 3 4 Verify the security schema by browsing the folders while logged in as administrator. Groups in the top row horizontally and the directory structure listed vertically For documents. there are extra permissions. while logged in as Project Manager. select New Folder. then they would have been granted permissions because they belong to the Everyone group. when you are done with that folder’s settings. R Read permission. D is Delete. right click the Security Project folder. who is a member of the Management group. the user named Drafter was not explicitly given permissions to access any folders. NA No access. So.

the extraction user only has Everyone permission. the modifications override the inherited security for the folder. 4 When a new sub-folder is created under a folder where a security schema exists. you can click on a name in the access control list in the properties dialog and the Inherited from field will update with name of the folder from which permissions are inherited. Those permissions are not sufficient to run all extraction processes. If you modify the permissions for a folder using inherited security.The Object Security Hierarchy Description: Plot files Environment: Default Environment Storage: Exton Owner: Administrator 2 Open the Properties dialog for the new sub-folder and select the Project\Folder Security tab. into consideration. Close the folder properties dialog. Inherited from changes to none. Inherited folder security When a root level folder has security applied and that security is subsequently applied to any sub-folders. As it currently stands. created specifically for running extraction processes. Note the populated access control list. In this case. 3 Select the Document Security tab. This list was inherited from the parent folder. The folder then has its own explicitly defined security and no longer inherits from the folder higher in the hierarchy. This access control list was also inherited from the parent folder. Jun-10 Copyright © 2010 Bentley Systems. Incorporated 205 Access Control . The folder now has its own permissions Security and Document Processors The security schema you just defined neglected to take an extraction user. it will inherit security from the parent folder.

The Object Security Hierarchy • • • Full Text extraction requires Read permission File Properties extraction requires Read. Each new folder will then inherit a standard security schema. Add the Extraction user to the Documents sub-folder. no change is required. Establishing default security It is often desirable to establish a default security model for creating new folders. Access Control Copyright © 2010 Bentley Systems. setting the same Document permissions. Note that the user must personally have the Document -> Modify permission enabled. Write. and File Write permissions You can create individual users for each of the respective extraction processes. select the extraction user from the list. File Read Write. This standard security model serves as a starting point. This is more efficient than creating the security schema specifically for each new folder. Select the Project\Folder Security tab. open the Properties dialog for the \Security Project\Drawing folder. and click OK. Disable Create. Incorporated 206 Jun-10 . Highlight the extraction user in the access list. and File Write are enabled. It is the documents to which they need access. and Change Workflow State for that user. File Read. Delete. 3 4 5 Select the Document Security tab.  Exercise: Modify the security schema to include the extraction user 1 2 In ProjectWise Explorer. or you can create a single user for all processes. click Add. 6 7 Click OK. File Read and Write permissions Thumbnail extraction requires Read. The user only needs to be able to see what’s in the folder. It also helps you to remember critical users or groups. and you can refine from there. such as the extraction user. Since the extraction user is by default a member of the Everyone group. If you have a single user. Read. be sure to grant that user sufficient folder and document access rights to run all extraction processes.

and File Write. Write. 7 8 9 Select the Document Security tab and click Add. create a new root level folder with the following properties: Jun-10 Copyright © 2010 Bentley Systems. and click OK. 4 5 6 Select the Administrator group and check Full Control. Select the Administrator group and Everyone and click OK. Highlight the Administrator group and check Full Control. In order to establish default security for root level folders.The Object Security Hierarchy Since the root level folder in ProjectWise Explorer has no parent folder. Select the Folder Security tab and click Add. Click Apply From this point forward. This is done in ProjectWise Administrator. Select the Administrator group. all new root level folders will inherit these security settings.  Exercise: Verify the default security schema 1 In ProjectWise Explorer. all new root level folders will inherit these document security settings. Incorporated 207 Access Control . and the Extraction user. right click the class datasource and select Properties. File Read. Everyone.  Exercise: Define default folder and document security for the datasource 1 2 3 In ProjectWise Administrator. 12 Click OK. From this point forward. Read. 10 Highlight the Everyone group and disable all access except Read and File 11 Highlight the Extraction user and disable all access except Read. it is necessary to configure Folder and Document Security for the datasource. security cannot be inherited. Select the Everyone group and disable all access except Read.

In this case. each document would have its own security. Access Control Copyright © 2010 Bentley Systems. The folder access control list includes those items inherited from the default folder security schema. The document access control list includes those items inherited from the default document security schema. In the event that documents in the same folder need different access rights. Select the Project\Folder Security tab. Note that. it is still thought of as folder security because it is defined at the folder level. The Inherited from field updates to reflect that the security schema is inherited from datasource global permissions. Incorporated 208 Jun-10 . This includes folders created before establishing the default security schema. In the previous examples. 5 Select the Document Security tab. security may actually be applied at the document level. Document level security There may be cases where this security model doesn’t provide adequate security. 7 Close the folder Properties dialog.The Object Security Hierarchy Name: Default Folder Security Environment: Default Environment Storage: Exton Owner: administrator 2 3 Open the new folder’s Properties dialog. Note: Default security will affect all folders in the project that do not have their own security. independent of its parent folder or other documents within the folder. 4 Select the Administrator group. yet the schema applied to both folders and documents. even though the schema applied to both folders and documents. 6 Select the Administrator group. The Inherited from field updates to reflect that the security schema is inherited from datasource global permissions. security was applied at the folder level.

You cannot remove members from an access list defined at the datasource level. Write. and then log in as Project Manager. File Read. Note that the Administrator and Everyone groups and the extraction user have permissions to this document. 2  Exercise: Establish document level security 1 Open the Document Properties dialog for Manholes 1 of 5. and are handed down to the document. Give the Management group Delete.pdf and select the Security tab. 2 3 In the access control list. and click OK. and File Write permissions. Change Workflow State. select the Management group. Log out of the datasource. Note that the Remove button at the bottom of the dialog is inactive. 4 5 6 7  Click Add. Click Close. Exercise: Test the schema 1 2 Log in to ProjectWise Explorer as Drafter. You will only see documents 2 and 3 of 5. navigate to \Document Security folder in the class data set. create a new root level folder named Document Security using the Default Environment and setting the Owner to Administrator. Incorporated 209 Access Control . Read.The Object Security Hierarchy  Exercise: Import files to test document level security 1 In ProjectWise Explorer. drag the files from that folder into the new ProjectWise folder. and drop them. they can no longer see the first document. In Windows Explorer. Navigate to the Document Security folder. Since the Drafter user is not a member of the Administrator group or the Management group. Navigate to the Document Security folder. Jun-10 Copyright © 2010 Bentley Systems. and then click Save. select Everyone and change the access permission to No access. These permissions are the datasource global document permissions. 3 4 Log out of the datasource.

Open the Properties dialog for the Manholes 1 of 5. Other documents in the folder continue to inherit permissions from the hierarchy. The Project Manager user has read. The Remove button is now active because their permissions were modified. Select the Security tab. write. New documents in the folder will inherit permissions from the hierarchy. document read. At this point. 5 6 7 8 Log out of the datasource. and it can be modified by anyone with Change permissions. 9 Note: Close the document properties dialog. • • • Workflow Security When designing folder security for workflow.Workflow Security You now see all three documents. Incorporated 210 Jun-10 . However. document write. • In the previous example. and then log in as the administrative user. the document has its own security. select Everyone. Security for these two documents is still inherited from the global datasource permissions.pdf. It can be disconcerting when folders appear and disappear as the documents move through states. and delete privileges to the first document. documents 2 and 3 are read-only since their security was not modified. Access Control Copyright © 2010 Bentley Systems. the Remove button was inactive until at least one change had been made to the document’s security. In the access control list. Document level permissions should only be used in instances where one document in a folder needs a different access control list from the others. Routine use of this technique is discouraged because it can be cumbersome to maintain. keep in mind that the folder’s state will change less dynamically than the documents in the folder.

you should assign security (both folder and document security) to the folder. The folder security is static. Incorporated 211 Access Control . set document security only in the workflow. you should assign only state-based security to documents. You can start assigning permissions now. and is not dependant on workflow states. It makes sense to add all of the Groups. Hint: It is recommended that you set security on Folders only in ProjectWise Explorer. Important: When using Workflow security. When using Folder Security. this combination can get very complex. Implementation The simplest method of working with Real security is to separate it from folder security. but this can cause folders to disappear and reappear based on their state. Then. This is called Real security. Jun-10 Copyright © 2010 Bentley Systems. and should be carefully planned prior to implementation.Workflow Security ProjectWise combines the security applied directly to folders and documents with the security assigned through workflow. These permissions serve as the defaults. Right click on Workflows in the console tree and select New > Workflow to open the New Workflow Properties dialog. This is where you give the workflow a name and an optional description. The document security is dynamic. For an administrator. even before adding any states. Right click a Workflow and select Properties to open its properties dialog. they will inherit from the default security for the workflow. Once states are added. Assigning security at the document level can be cumbersome to maintain and should only be done where necessary. It is possible to assign state-based security to a folder. and is dependent on the current workflow state for each document.

but you cannot set the security type at the top. Incorporated 212 Jun-10 . Right click and select Add State. select the states that you want to use in the Workflow. Adding the states To add states to a workflow. right clicking.Workflow Security Users. You can assign permissions for the other groups. You can optionally assign permissions to the members of the access list. You can refine the security of the state by selecting it. Then modify the permissions as you add States. The ProjectWise Workflows module contains exercises that demonstrate this implementation. as they are initially listed in alphabetical order. Under most circumstances. expand the structure under workflows in the console tree and select the desired workflow. You should do this for the Administrator group. In the Select States to Add dialog. Once again. Order them correctly using the arrows that appear in the upper right corner of the Administrator dialog. and opening its properties dialog. a security matrix should be used to assist with assigning rights. You can use the Shift or Ctrl keys to select multiple states. or User Lists that you will need as users progress through the states. The order in which they are selected doesn’t matter. you will want to assign the security on the Document Security tab. This dialog works like those for folder and document security. This lets you only go through the Add process once. Assign the most restrictive permissions as a baseline from which to start. Access Control Copyright © 2010 Bentley Systems. since their security is not likely to change during the different states. but you will have to modify those to reflect the permissions for the various states.

are defined in ProjectWise Administrator. Jun-10 Copyright © 2010 Bentley Systems.Working with Workflow-Based Security Working with Workflow-Based Security Real When the Real (Workflow & Folder) security type is selected. from its Workflow if defined in ProjectWise Explorer. the Workflow and State option lists are also enabled. the folder is considered to be in that state. The Workflow option list contains all available workflows defined in the datasource. The Real (Workflow & Folder) Security Type provides a read-only view of the combined security settings. which override their workflow permissions. If the inherited settings are modified. A state inherits its security settings from its workflow state permissions or from its workflow if either. as defined in ProjectWise Administrator. they become the workflow state’s own permissions. A folder with its own workflow/workflow state permission settings does not have inherited ones. or both. This lets you manage the workflow security hierarchy. You must switch the Security Type to Folder or Workflow to make modifications. the Workflow and State option lists are enabled on the security tabs of the document and folder properties dialogs. The Add and Remove buttons are hidden and you cannot change permissions. This means that they are valid only when the folder is in the selected state in that workflow. The state option list displays all States in the selected workflow. Workflow When the Workflow security type is selected. Remember that when all documents in a folder are moved to the same state. The modified permission settings are assigned to the folder in the selected workflow and state. The Name list contains the objects that could be inherited from the workflow or from the workflow state. Setting the Security Type to Real (Workflow & Folder) will display what that user’s permissions really are. or. For example. Incorporated 213 Access Control . a user can have environment permissions.

the Workflow and State option lists are disabled and folder security is displayed. Note: In ProjectWise Explorer. The Name list displays the objects that could be inherited from the parent folder. the user is immune to access control and will therefore have access to all files and folders. and it is not possible to modify the security in this mode. General -> Use Access Control This setting. In order to modify security you need to select either the Workflow or Folder types. User properties setting In addition to the folder and document user properties settings. When disabled. it is only possible to set document permissions for a document in a particular state. These rights override those settings at the folder level from the perspective that they may globally restrict the user. not based on the folder being in a particular state. Security Datasource and User Properties Settings Each user has rights relative to folder and document security. Folder When the Folder security type is selected. Once again. Real security is displayed by default. If the <Default> state option is used. the following settings affect security within ProjectWise. Incorporated 214 Jun-10 .Security Datasource and User Properties Settings States within a workflow can have their own permission settings. A folder with its own permission settings does not have inherited ones so you can manage the ProjectWise security hierarchy. Enable “Use access control” for the majority of Access Control Copyright © 2010 Bentley Systems. in the General category on the Settings tab of the user properties dialog. all states within the workflow without their own settings will use the permission settings defined for the default state. controls how folder and document security affects a user.

Incorporated 215 Access Control . the following datasource settings affect security within ProjectWise. they cannot be given back at the folder level. Global Delete Restrictions This setting. Jun-10 Copyright © 2010 Bentley Systems. Log back in to ProjectWise Explorer and you will see the folder again. and only enable “Allow user to change general settings” for users with full administrative access rights. Datasource properties setting In addition to the default security schema. Document Owner restricts document deletion to the owner of the document. Owner: This option has the options Folder Owner and Document Owner. no users other than members of the Administrator group can delete documents. Hint: You may find that a folder has become invisible. let’s measure what you have learned. on the Settings tab of the datasource properties dialog. If you cannot see a folder. open the user properties dialog in ProjectWise Administrator and disable the Use Access Control setting. Admin Only: When selected. • • Module Review Now that you have completed this module. includes the following options: • Default: When selected. Questions 1 2 Explain the reason for stating that security in ProjectWise is exclusive. Folder Owner restricts document deletion to the owner of the folder. True or False: If rights are removed at the user level.Module Review users. this setting has no effect on document delete rights. Users can delete documents based on their document user properties settings and the document access control defined for the folder.

Incorporated 216 Jun-10 .Module Review 3 4 5 What is the object-based approach to access control? When do you use it? What is the workflow-based approach to access control? Access Control Copyright © 2010 Bentley Systems.

This module discusses creating and applying workflows. Incorporated ProjectWise Workflows . Module Prerequisites • • • Knowledge about the ProjectWise Explorer and ProjectWise Administrator interfaces Knowledge about user accounts Knowledge about access control Module Objectives After completing this module.ProjectWise Workflows Module Overview ProjectWise workflows have two primary functions. The other is to allow the security schema for a document to change based upon its life cycle. The first is to track documents’ progress and send notifications. you will be able to: • • • • • Create workflows and states Apply states to workflows Create a message agent Work with workflows and folders in ProjectWise Explorer Work with workflow-based security Jun-10 217 Copyright © 2010 Bentley Systems.

the access control list for a document object is determined by the current state of the document within the workflow. a Revisions phase. they place the document in the next state of the workflow. Then users with access to that next state will have access to the document. In ProjectWise Explorer. Workflows ProjectWise Workflows Copyright © 2010 Bentley Systems. Incorporated 218 Jun-10 . no access control settings are configured. Typically. When a user is finished creating a draft document. The process goes on until the work is complete.Introductory Knowledge Introductory Knowledge Before you begin this module. It is only when some users are explicitly given permissions to certain items that other users are excluded from accessing those items. you might want all of your documents to have a Draft phase. The access control list changes as a document moves through the states in the workflow. therefore all users you create will have access to all folders and documents in the datasource. and a Final phase. Workflows contain states. You create a workflow and then create a state for each phase. You then assign the states to the workflow. let's define what you already know. the workflow is assigned to a folder. only certain users will have access to each state in a workflow. When a datasource is first created. For example. Questions 1 2 What is the workflow-based approach to access control? Explain the reason for stating that security in ProjectWise is exclusive. a First Review phase. Answers 1 With workflow security. All documents at the root of the folder are automatically placed in the first state in the workflow. 2 Workflow Overview Workflows are created in ProjectWise Administrator and are applied to folders and projects in ProjectWise Explorer. which are the phases or milestones you want all of your documents to have or go through.

right click on States in the console tree and select New > State. However. it can be used across multiple workflows in the same datasource. They are labels for functionality used elsewhere in ProjectWise. type the description Preliminary phase. Create States using the following name/description combinations: Design/Design phase Review/Review phase Jun-10 Copyright © 2010 Bentley Systems. Creating and Modifying States Before implementing a workflow.Creating and Modifying States provide an electronic approval process that can be documented through the Audit Trail.  Exercise: Create states 1 2 3 In ProjectWise Administrator. you must create states. At the same time. Workflows and states are created independently from each other. States can be used in more than one workflow. and then click OK. care should be taken not to burden users with overly complicated workflows. Once a state exists. Creating states When creating states. or you can create states and then create the workflow that will contain them. the order isn’t important. You can create an empty workflow to which you will add states later. The goal of workflow design is to provide sufficient states on which to base changes to document access permission or automated notifications. Name the state Preliminary. A state cannot be deleted if it is associated with a workflow. Incorporated 219 ProjectWise Workflows . States are similar to ProjectWise applications or interfaces. Click on the States icon in the ProjectWise Administrator console tree to view previously defined states in the document list. they cannot be used more than once in a single workflow. Order becomes important when adding them to a workflow. you should outline the states you want to include. Before creating a workflow.

To see the new state structure you must detach and then reassign the workflow. you must name the workflow. you should add any security objects to the workflow now so you will not have to add them to each individual state. However.Creating and Modifying Workflows Issued/Issued Modifying a state To change the name or description of a state. Change the name and description on the General tab.  Exercise: Create a workflow 1 2 3 In ProjectWise Administrator. right click on Workflows in the console tree and select New > Workflow. Name the workflow Project Workflow. ProjectWise Workflows Copyright © 2010 Bentley Systems. provided no folders in the datasource use them. and then click OK. Before adding states. such modifications will not be reflected in folders where the workflow is already assigned. it is not mandatory to define security through the workflow mechanism. Workflows can be deleted. You can implement workflows simply to provide notifications to designated users as documents move through their life cycle. You can modify existing workflows by adding or removing states. Creating and Modifying Workflows A Workflow is defined by selecting states in a particular order. Right click on the new Workflow and open the Properties dialog. right click the state and select Properties. type a description. While you can use workflows as part of a security schema. the states in the source workflow do not copy to the target workflow. Incorporated 220 Jun-10 . If you create a workflow by copying an existing workflow from another datasource. If you are going to implement workflow security.

Creating and Modifying Workflows 4 On the Document Security tab. and then apply security according to the following matrix. using the arrows to adjust the order: Preliminary Design Review Issued 7 Right click each state. You can assign permissions for the other groups. Groups are in the top row. Incorporated 221 ProjectWise Workflows . horizontally. FR File Read permission. add Administrator. Administrator group Design group C/D/W/CWS/FW C/D/W/CWS/FW FR/W/CWS FR Everyone R R FR FR Management group R FR C/D/W/CWS/FW FR/CWS FC FC FC FC Preliminary Design Review Issued Jun-10 Copyright © 2010 Bentley Systems. select Add State. select the Document Security tab. select Properties. You can optionally assign permissions to the members of the access list. and the states are listed vertically. since their security is not likely to change during the different states. Note that FC indicates Full control. Administrator group FC Design group R/CWS Everyone FR Management group R/CWS 6 Right click the workflow. but you will have to modify those to reflect the permissions for the various states. R Read permission. 5 Apply security to the workflow. Everyone and Management. and add the following states. according to the following matrix. CWS Change Workflow State. Design. You should do this for the Administrator group.

Messaging Services Messaging Services Messaging services are used to notify users when a particular event occurs for a document. If the message is an e-mail message. the document itself is attached to the message. Other events include: • • • • Document check out or check in When a document is exported When a document changes version When the server copy is updated The message can be sent as a ProjectWise message or as a regular e-mail. Creating a message agent Use the New Messaging Agent Wizard to define messaging agents. If you enable Attach Document on the Defining the messaging agent page. ProjectWise Workflows Copyright © 2010 Bentley Systems. One such event would be when a document changes state within a workflow. Incorporated 222 Jun-10 . the ProjectWise address to the location of the document will also be displayed in the e-mail. you will have a link to the document attached to the message if the message is a ProjectWise message. In the case of e-mail messages. You can choose to attach a document to the message.

On the Attaching Folder to Document Agent page. the Users that have access to the document check box is enabled by default. Click Next in the New Messaging Agent Wizard. To create the message agent. Otherwise. type the message subject and textual content and select the type. to determine which user action generates the message. In most cases. other than Document state change. and then click Finish. or when the server copy of a document is updated is slightly different than that for state changes. Then. Click Add to select those who you want to include as recipients. On the next page. Last. checkouts. the message is sent. Then enable either “Send the message just before the command is executed” or “Send the message when the command execution is finished” to determine when the message is sent. version changes. exports. Click Next to open the Specifying Message Sending Mode page. Incorporated 223 ProjectWise Workflows . every user that has Read or better access rights to the document are included on the message. invoke the New Messaging Agent Wizard and complete the pages up to the Specify Command type and Sending time page. right click the Messaging Services icon in ProjectWise Administrator’s console tree and select New > Messaging Agent. Select a Command type. you will want to disable this option. click Next. Select Document State change to send a message when documents either enter or exit the specified state(s). Enable “Send the message silently” so that the user who triggers the message will not be notified before the message is sent or “Show dialog to send the message” so that the user will receive the message before it is sent out. When the specified action is performed on any document in the folder. Enable Attach Document if desired and click Next. select the folder(s) to be associated with the messaging agent. Workflow related events To create a workflow messaging agent for document state changes. first make sure you have at least one workflow in your datasource.Messaging Services Non-workflow related events The procedure for creating a messaging agent for document check-ins. On the Specifying message recipients page. When you are specifying a State-based action you Jun-10 Copyright © 2010 Bentley Systems.  How to create a messaging agent for non-workflow related events: First.

The next page is where you select the workflow and state to which the messaging agent will apply. and a state in that workflow to associate with the messaging agent. depending on the selection on the previous page.Messaging Services can choose to send the message when the document leaves the current state. right click Messaging Services in the console tree and select New > Messaging Agent. and then click Next: Users that have access to the document on which the command is executed: Disabled Recipients: Add the Management group 5 On the Specifying Message Sending Mode page. set the following. you don’t select a folder because the messaging agent will apply to all folders using the assigned workflow. set the following. In this case. and then click Next: ProjectWise Workflows Copyright © 2010 Bentley Systems. Click Next on the Welcome page. and then click Next: Message Subject: Drawing for review Message Text: See attachment Message Type: ProjectWise message Attach Document: Enabled 4 On the Specifying Message Recipients page. or when it enters the new state.  Exercise: Create a workflow related messaging agent 1 2 3 In ProjectWise Administrator. Incorporated 224 Jun-10 . Clicking Add opens the Select Workflow State dialog where you select a workflow. On the Defining Messaging page. you will create a messaging agent to send a message to the Design group when a document in the Project Workflow enters the Review state. set the following. In the following exercise. A message is sent when a document enters or leaves that state.

Jun-10 Copyright © 2010 Bentley Systems. select the project workflow and add the Review state of the Project workflow Click Next and then click Finish. all documents at the root of the folder or project inherit the assigned workflow and are automatically placed in the first state defined for that workflow. and then click Next: Command Type: Document state change Send the Message when document enters new state: Enabled 7 8 On the Attaching Workflow State to Workflow Agent page. the option list’s text field is empty. you must assign the Workflow to one or more folders in ProjectWise Explorer. If you package 50 documents for review and they all change state. 50 e-mail messages are sent. Workflows in ProjectWise Explorer In order to use a Workflow in ProjectWise. set the following. After a workflow is selected. The folder’s documents display in the first state of the workflow. however new folders or projects you create will automatically be assigned the same workflow as its parent folder or project. When the Workflow & State tab first opens. unless the folder has already been assigned a workflow. The Workflow option list contains all the workflows defined for the datasource. Assigning a workflow to a folder Workflows are assigned to folders on the Workflow & State tab of the Folder Properties dialog. The workflow and its states can be expanded to list the Documents in each State. Note: Messaging is per document. When you assign a workflow to a folder or project. Existing subfolders or subprojects do not inherit the workflow assigned to their parent folder or project.Workflows in ProjectWise Explorer Send the message silently: Enabled 6 On the Specifying Command type and sending time page. Incorporated 225 ProjectWise Workflows . the current folder’s workflow displays in the option list’s text field.

Select the Project\Folder Security tab.  Exercise: Review folder workflow and security 1 2 Continuing in ProjectWise Explorer. Click OK to assign the workflow to the folder. In Windows Explorer.  Exercise: Create folders and documents 1 2 3 Log in to ProjectWise Explorer as the administrative user. Assign the Project workflow and click Apply. 3 4 5 6 7 Click OK to close the dialog. Create a new root level folder named Workflow Project. drag the sub-folders from that folder into the new ProjectWise folder. and then re-open it. Currently the folder is only using Folder security. click OK to move all documents to the first state of the workflow. When prompted.Workflows in ProjectWise Explorer When assigning a workflow to a folder. You are notified that doing so will result in all documents being moved into the first state of the workflow. navigate to the \Workflow Project folder in the class data set. and drop them. Select the Project\Folder Security tab. open the Folder Properties dialog for the Workflow Project folder. Note that the Security type for the folder is now set to Real. an Alert prompts you to confirm that you want to change the folder’s workflow. Click the Workflow & State tab. Remember that the Project workflow did not define security for the folder. Incorporated 226 Jun-10 . 8 Highlight the Administrator group. ProjectWise Workflows Copyright © 2010 Bentley Systems. only for the documents in the folder. Real security is a combination of folder and workflow security.

12 Click OK to close the Folder Properties dialog. 10 Highlight the Design group. Therefore.  Exercise: Review the Workflow and Security for the sub-folders 1 2 In ProjectWise Explorer. sub-folders do not inherit workflow because the sub-folders were created prior to assigning the workflow. 3 Select the Project\Folder Security tab and highlight the Administrator group. open the Folder Properties dialog for the Admin sub-folder. Incorporated 227 ProjectWise Workflows . 9 Click the Document Security tab. The Project workflow includes document security. In this case. Note the permissions for the Design group when the State is set to Preliminary. You will find that changing the state does not affect the folder permissions. Note that the security type is set to Folder and the permissions for the Administrator group are inherited from the datasource global permissions. Jun-10 Copyright © 2010 Bentley Systems.Workflows in ProjectWise Explorer The security for this folder is inherited from the datasource global permissions. 11 Change the State from Preliminary to Issued and highlight the Design group. The security is set to Real. Select the Workflow & State tab. The access control list confirms that the Design group has different access permissions for documents in different states. the security access control list will vary based on the selected state. The workflow for the folder is set to <none>.

overriding the global defaults. or both as columns in the document list view. expand Basic Columns. Incorporated 228 Jun-10 . select View > Choose Columns. One way to access this information is in the preview pane.  Exercise: Add workflow columns to the view 1 2 3 In ProjectWise Explorer. the preview pane will display the workflow and the state. Alternately. When prompted. a user can display workflow. select the Workflow & State tab. the security type is set to Folder and the permissions for the Administrator group are inherited from the datasource global permissions. By default. In the previous examples. Click OK to close the Folder Properties dialog. state. If necessary. all security was inherited from the global datasource permissions. In the left pane. it is often desirable to determine a folder or document’s state without opening the properties dialog. ProjectWise Workflows Copyright © 2010 Bentley Systems. Select your existing view definition so you can add columns. in the Folder Properties dialog for the Admin subfolder.  Exercise: Assign a workflow to the sub-folders 1 2 3 4 5 In ProjectWise Explorer. Repeat the process to assign the Project Workflow to the Dgn and Docs sub-folders. Identifying folder/document workflow and state When ProjectWise workflows are in use.Workflows in ProjectWise Explorer 4 Select the Document Security tab and highlight the Administrator group. Once again. Set the Workflow to Project Workflow. you can assign folder permissions to the individual folders. click OK to move all documents to the first state of the workflow.

dgn. Click OK to dismiss the comments dialog. Incorporated 229 ProjectWise Workflows . Right click the document plotplan. The Change State dialog is where you can move multiple documents forward or backward within the Workflow. Jun-10 Copyright © 2010 Bentley Systems. and select Change State > Change. Right click the document office. it is likely that you will define many workflows. and select Change State > Next. In the left pane. The workflow and state for each document is listed in columns in the view. navigate to the \Workflow Project\Dgn folder.  Exercise: Working with Documents and Workflow States 1 2 3 In ProjectWise Explorer. Navigate to the \Workflow Project\Dgn folder. Log back in using the Drafter credentials.dgn. Move them using the green arrow icons or by dragging a document to a new State and dropping. Double click the Folder Workflow item to add it to the view definition. Displaying the Workflow column provides useful feedback for users. Click OK. but only read permissions for documents in the Review state. Note that the Drafter user has permissions to modify document in the Preliminary and Design states. In a production environment.dgn down and drop it onto the Review State. The State of the document is now set to Design. Changing states Document state can be changes within the workflow from ProjectWise Explorer’s Document menu or right click menu.Workflows in ProjectWise Explorer 4 5 6 7 Double click the State item to add it to the view definition. Close the Change State dialog. 4 5 6 7 8 9 Drag plotplan. clicking OK to dismiss the comments dialog. expand Folder Columns. Log out of ProjectWise Explorer.

Incorporated 230 Jun-10 . View. indicating that there is a document ready for review. ProjectWise Explorer polls the Integration Server every two minutes to check a user’s inbox for new messages. and log back in using the Project Manager credentials. etc. You will see that anyone in the Management group will receive the message based on the state change. By default. Within the ProjectWise Messenger system. Note that you have all document functions available from the attachment. the project manager user will have a message waiting. The dialog initially opens to the user’s Inbox. ProjectWise Workflows Copyright © 2010 Bentley Systems.  Exercise: Verify the Messaging Agent 1 Log out of ProjectWise Explorer.dgn document was moved to the review state. You can use ProjectWise Administrator to review the Messaging Agent definition. each user has an Inbox and a Sent Items folder. select Open Folder. 6 Close the message and then close the ProjectWise Messenger. click Yes. they won’t be prompted immediately.Workflows in ProjectWise Explorer Workflow related messages A messaging agent was defined to send a message to users when documents entered the Review state of the Project workflow. Even though this user has a message waiting. Check Out. 2 When prompted. Right click the message attachment. If they don’t manually check for new messages. they are notified after a maximum of two minutes. The ProjectWise Messenger is a limited e-mail system integrated with ProjectWise. This gives ProjectWise Explorer focus and directs the user to the folder containing the document. This includes Open. to view new messages. Since the plotplan. 5 From the right click menu. 3 4 Double click the new message to view the message contents.

The Name list contains the objects that could be inherited from the workflow or from the workflow state. Setting the Security Type to Real (Workflow & Folder) will display what that user’s permissions really are. The Real (Workflow & Folder) Security Type provides a read-only view of the combined security settings. For example. or from its Workflow if defined in ProjectWise Explorer. they become the workflow state’s own permissions. the folder is considered to be in that state. A folder with its own workflow/workflow state permission settings does not have inherited ones. The Add and Remove buttons are hidden and you cannot change permissions. or from its workflow if either or both are defined in ProjectWise Administrator. Jun-10 Copyright © 2010 Bentley Systems. If the inherited settings are modified. The state option list displays all States in the selected workflow. The Workflow option list contains all available workflows defined in the datasource. the Workflow and State option lists are enabled on the security tabs of the document and folder properties dialogs. Remember that when all documents in a folder are moved to the same state. as defined in ProjectWise Administrator. This means that they are valid only when the folder is in the selected state in that workflow. This lets you manage the workflow security hierarchy.Working with Workflow-Based Security Working with Workflow-Based Security Real When the Real (Workflow & Folder) security type is selected. the Workflow and State option lists are also enabled. Incorporated 231 ProjectWise Workflows . The modified permission settings are assigned to the folder in the selected workflow and state. A state inherits its security settings from its workflow state permissions. You must switch the Security Type to Folder or Workflow to make modifications. a user can have environment permissions that override their workflow permissions. Workflow When the Workflow security type is selected.

In order to modify security you need to select either the Workflow or Folder types. Once again. Click the Project\Folder Security tab. right click on the \Workflow Project\dgn folder and select New Folder. 3 4 5 6 Log out of ProjectWise Explorer. For this exercise. the folder’s security is inherited from the datasource global permissions.  Exercise: Refine the Real security schema 1 2 Still logged in as the Project Manager user in ProjectWise Explorer. A folder with its own permission settings does not have inherited ones so you can manage the ProjectWise security hierarchy. Folder When the Folder security type is selected. and log back in using the administrative credentials. Click OK in the Error Information dialog. the Workflow and State option lists are disabled and folder security is displayed. it is only possible to set document permissions for a document in a particular state. To do this. not based on the folder being in a particular state. Note: In ProjectWise Explorer. you need to provide folder security for the project. overriding the datasource global permissions. Open the Folder Properties dialog for the Workflow Project folder. Create a new folder named Structural. document security is defined by the Workflow. If the <Default> state option is used. Since the Workflow did not define folder security. The default datasource global permissions allow only the administrator group to create sub-folders. Real security is displayed by default. In this case. ProjectWise Workflows Copyright © 2010 Bentley Systems. you want the Management group to create sub-folders. Incorporated 232 Jun-10 . The Name list displays the objects that could be inherited from the parent folder. all states within the workflow without their own settings will use the permission settings defined for the default state.Working with Workflow-Based Security States within a workflow can have their own permission settings. The process fails. and it is not possible to modify the security in this mode.

and Write. FW R R Review the permissions for the Management group in the table. To understand why this error occurred. FR Review FC R. FR. You will see that the Management group has permissions to Create subfolders. Highlight the Management group in the access control List. R. Click Add. Preliminary Design FC C. Jun-10 Copyright © 2010 Bentley Systems. FR. 5 Click OK in the Error Information dialog. you need to review the Document security defined for the Workflow. Remember that the folder will take on the state of the document at the lowest state in the workflow. FR R. The Project Manager user was unable to create a new document because the folder itself is still in the Preliminary state. Delete. FW C. FR R. You receive an error message indicating that you have insufficient privileges to complete the operation. select the Management group. R. 11 When prompted. 10 Accept the default permissions and click Apply. FW R R. W. FW Issued FC R. and then click OK. navigate to the \Document Indexing\MS-V8 folder in the class data set. W.Working with Workflow-Based Security 7 8 9 Change the Security Type from Real to Folder. D. Create a new folder named Structural. FR. In Windows Explorer. Read. enable Apply Change to this folder only. FR Administrative Design Everyone Management FC C. D. 12 Close the Folder Properties dialog. drag the files from that folder into the new ProjectWise folder.  Exercise: Testing the new security schema 1 2 3 4 Log out of ProjectWise Explorer and log back in using the Project Manager credentials. Incorporated 233 ProjectWise Workflows . and drop them. FW R. R. Right click on the \Workflow Project\Dgn folder and select New Folder. Note that the first state in which the Management group has Create permissions is the Review state. W.

Document -> Change State Change State: When enabled. Workflow Datasource and User Properties Settings User properties settings ProjectWise provides the following user properties settings to restrict users’ ability to change Workflow states. if a user has read/write privileges to State 1 and read/write/create privileges to State ProjectWise Workflows Copyright © 2010 Bentley Systems. For example. Datasource settings ProjectWise provides datasource level settings to control document creation permissions in the context of Workflow document security. In order to change the state of a document. Folder -> Change State Change State: When enabled. but the Project Manager user doesn’t obtain create privileges until the folder reaches the Review state. Documents • Creation in workflow Put created document into first Workflow State having create permission: When a user creates a document. They must also have Write permissions to the folder to do this. the document is assigned to the first State in the Workflow where the user has create privileges. In this example. users can change the State of a document. they must have Document Write (not File Write) permissions. Incorporated 234 Jun-10 . or change the Workflow if one is already assigned. provided they have permission to change the document in question. users can assign a workflow to a folder.Workflow Datasource and User Properties Settings When the last document moves to the next state. the folder moves to that state. the folder is still in the Preliminary state.

Click Apply. note the state of the new documents. and then click OK. If this is undesirable. Folder State does not prevent document creation: A user can create a document in a folder.Module Review 2. In the Documents category. enable Creation in Workflow. when they create a document. Log out of ProjectWise Explorer and log back in using the Project Manager credentials. you may want to consider modifying the security schema to include create permissions in the first state of the workflow for all groups. drag the files from that folder into the new ProjectWise folder. navigate to the \Document Indexing\MS-V8 folder in the class data set.  Exercise: Working with datasource workflow settings 1 2 3 4 5 6 7 8 In ProjectWise Administrator. let’s measure what you have learned. Navigate to the \WorkflowProject\Dgn\Structural folder. In Windows Explorer. if a folder is in State 2 and a user has create privileges in State 1 but not State 2. When you are done. the document will still be placed in State 1. and drop them. Enable Put created document into first workflow state having create permission. right click the datasource in the console tree and select Properties. the new documents were created in the Review state. Questions 1 What is a workflow? Jun-10 Copyright © 2010 Bentley Systems. Rather than the Preliminary state. Select the Settings tab. the document will automatically be placed in State 2. even if the folder is in a State for which they do not have create privileges. For example. Module Review Now that you have completed this module. Incorporated 235 ProjectWise Workflows .

all documents at the root of the folder or project inherit the assigned workflow and are automatically placed in the first state defined for that workflow. Where are workflows assigned to folders? True or False: When you assign a workflow to a folder or project. What is Real security? 6 ProjectWise Workflows Copyright © 2010 Bentley Systems. Incorporated 236 Jun-10 .Module Review 2 3 4 5 What is a state? Name the events on which you can base a messaging agent.

these applications often rely on external data. Module Prerequisites • • • • Knowledge about the ProjectWise Explorer and ProjectWise Administrator interfaces Knowledge about MicroStation workspaces Basic MicroStation skills (view controls. Unlike typical desktop applications. In addition. element placement) Knowledge about MicroStation tag elements Module Objectives After completing this module. applications like MicroStation place different demands on a content management system due to features such as reference files. you will be able to: • • • • • Manage multiple MicroStation versions Understand MicroStation reference management Use versioning to manage the design process Configure MicroStation workspaces/AutoCAD workspace profiles Integrate MicroStation/AutoCAD title blocks Jun-10 237 Copyright © 2010 Bentley Systems. Working with these documents using traditional networking techniques often leads to problems due to the complex relationships between files. or data sets.Integrated Applications Module Overview ProjectWise provides an extensive set of tools for using MicroStation in a managed environment. Incorporated Integrated Applications . commonly referred to as workspaces. profiles.

It lets you define your resource locations and project settings. This is important during a transition period when users may be working with files in both old and new formats. let's define what you already know. but also the version of the application was used to create the file. Multiple MicroStation Versions One advantage of using ProjectWise is that is allows you to track not only the file type. or with two versions of an application. Non-graphical attributes that may be attached to elements drawn in designs. one for MicroStation V8 XM Edition and one for MicroStation V8i. • • You can create a ProjectWise Application for multiple product versions. For example. and which were not.Introductory Knowledge • • • Use attribute exchange for Microsoft Office documents Work with MicroStation Link Sets Know about AutoCAD Sheet Set Manager and Session File Manager integration Introductory Knowledge Before you begin this module. A custom MicroStation environment or configuration. Integrated Applications Copyright © 2010 Bentley Systems. ProjectWise tracks more information about files and helps you remember which files were converted to a new version. Questions 1 2 3 What is a reference file or Xref? What is a MicroStation workspace? What is a tag/block Answers 1 2 3 A file attached and displayed with the active file for printing or construction purposes. Incorporated 238 Jun-10 .

to the right of the Program Class Name field. Normally you would add additional Action definitions but they are omitted now for brevity. and then click OK. highlight Bentley MicroStation V7. click the B icon that indicates MicroStation V7 files. click Applications in the console tree. 10 Click the browse button. Name it MicroStation V7. and then click OK. Jun-10 Copyright © 2010 Bentley Systems. click Remove. The new Application is functional. click Set icon. 12 Set the following: Action: Open Program Description: MicroStation V8 using V7 Workmode Command Line Arguments: -wsMS_OPENV7=3 13 Click OK twice. Select the Actions tab. Right click Applications in the console tree and select New > Application. Navigate to the location of the V7 install. Change the name from MicroStation to MicroStation V8.  Exercise: Set up an application for the V7 workmode 1 2 3 4 5 6 7 8 9 In ProjectWise Administrator. double click MicroStation to open the Properties dialog. On the General tab. Incorporated 239 Integrated Applications . 11 Select Bentley MicroStation V8i SELECTseries 1 and click OK. Select the Actions tab and click Create.Multiple MicroStation Versions This technique is equally valid with other applications where multiple file versions are in use. In the list of applications that are already defined.

Due to the default extension mapping. This confirms that ProjectWise has instructed MicroStation to open in V7 Workmode.dgn. Create a new root level folder named Integrated MicroStation. through CB6.dgn are MicroStationV8 files. Files CB4.dgn through CB6. All other users will continue to use the datasource default.dgn.dgn into the new ProjectWise folder. select Tools > Associations > File Extensions. navigate to the \Integrated MicroStation folder in the class data set. Note: Files CB1. Once properly set up in ProjectWise.Multiple MicroStation Versions  Exercise: Create folders and documents 1 2 3 Log in to ProjectWise Explorer using the administrative credentials.dgn. and drop them. When MicroStation launches. the administrative user has established a personal extension mapping for dgn files. Select MicroStationV7 from the options. 3 4 5 Select File > Open. As a result. In Windows Explorer. drag the files CB1. Click Close. checking the previous file in. drag the files CB4. the Application field provides a convenient reminder as to which version of MicroStation should be used to edit each file. double click CB4. and drop them.dgn and CB3. Click Cancel. Integrated Applications Copyright © 2010 Bentley Systems. Open CB1.dgn  Exercise: Working with MicroStation 1 2 In ProjectWise Explorer. when this user imports dgn files into ProjectWise they will automatically be associated with MicroStation V7.dgn are MicroStationV7 files. and navigate to \Integrated MicroStation in the class data set. which is to associate dgn files with MicroStation V8.dgn through CB3. Incorporated 240 Jun-10 . pause the pointer over the B icon in the status bar. 8 In Windows Explorer. 4 5 6 7 In ProjectWise Explorer. CB2. dgn files are automatically associated with the MicroStation V8i application. navigate to the \Integrated MicroStation folder in the class data set. Double click the dgn extension in the list.dgn from that folder into the new ProjectWise folder. From now on.

dgn. accept the default option Upgrade to V8 format. and let users utilize references in a distributed environment.dgn will be converted to the MicroStation V8 format. assume that CB4.  Exercise: Import files and change the associated application 1 In Windows Explorer.MicroStation Reference Management The B icon no longer appears because this is a V8 format file.xml. Incorporated 241 Integrated Applications . When prompted to Upgrade File Format.fileinfo. the changes documented in the XML file are saved to the logical set in the database. Click Save. Each XML file will have the name of the master file prepended to the file name. changes documented in the XML file are discarded and not saved to the database.dgn. drag the files E1. P1. 6 Exit the MicroStation session. master2. ProjectWise has reference manipulation and management tools.fileinfo.dgn. Jun-10 Copyright © 2010 Bentley Systems. For example. checking the file in. the file is converted to V8 format. and then click Close. navigate to the \Integrated MicroStation folder in the class data set. If you free the master document. and drop them. In the following exercise. 6 MicroStation Reference Management For each master MicroStation or AutoCAD document you check out.dgn from that folder into the new ProjectWise folder. Exit MicroStation. Double click CB4. Change the Application from MicroStationV7 to MicroStationV8.dgn and select Properties. This file lists all the master document's references. As MicroStation launches. checking the file in.dgn. When you select Check In or Update Server Copy.  Exercise: Convert a file to MicroStationV7 format 1 2 3 4 5 In ProjectWise Explorer. master1. and records all reference-related changes to the master document. right click CB4. and S1. These tools support both MicroStation and AutoCAD.dwg. an XML file is created in the working directory.xml.

4 When the Modify documents dialog appears. You see the updated icon preceding the documents. In the Attachment Settings dialog. In the ProjectWise Attach Reference dialog.dgn. From MicroStation’s File menu. select References. type the logical name Equipment. select all three files. navigate to the Integrated MicroStation folder. 5 6 Click Add. In the References dialog. make sure the application is set to MicroStationV8. change the application from MicroStationV7 to MicroStationV8. and click OK. Incorporated 242 Jun-10 . This command is used to modify the properties for multiple documents in a single operation. and select E1.MicroStation Reference Management Due to the extension mapping established in the previous exercise. 2 3 In ProjectWise Explorer.dgn. Right click them and select Modify. Creating sets  Exercise: Attach references 1 2 3 4 Continuing in ProjectWise Explorer. and click OK. Integrated Applications Copyright © 2010 Bentley Systems. double click P1. and then click OK. select Tools > Attach. these MicroStationV8 files were incorrectly associated with the MicroStationV7 application.

MicroStation Reference Management This completes the reference attachment.dgn. Enable Show Selective Set Open dialog. 9 10 Click Cancel to keep the file checked out. ProjectWise will copy out the references as the master file is checked out so that MicroStation can find all the members of the set. equipment. you see all files are present. Jun-10 Copyright © 2010 Bentley Systems. press F5. Note that the icon to the left of P1. The Select Reference Documents dialog appears. Incorporated 243 Integrated Applications . In MicroStation. In ProjectWise terminology. ProjectWise will automatically copy out all members of the set when the master file is checked out. the list of references. 7 8  Repeat the process to attach the structural file S1. Expand the User Interface category. Exit MicroStation. the piping. From now on. without opening the file in MicroStation. Exit MicroStation. ProjectWise can determine the other members of the set. Exercise: Working with references in ProjectWise Explorer 1 In ProjectWise Explorer. You will now see equipment elements in the piping file. 4 5 6 7 Select Tools > Options. 3 Close the set contents dialog.dgn. Double click P1. and click OK.dgn indicates that it has references attached. By default.dgn and select Set > Show References. checking the file in. 8 Click OK. with the logical name Structural. 2 Right click P1. and structural files are now members of a set. and click the Settings tab in the Properties dialog.

dgn. Integrated Applications Copyright © 2010 Bentley Systems.MicroStation Reference Management Reference location One of the most common problems with reference file management occurs when moving or deleting files that are referenced by others. 3 Click No to cancel the delete operation. select S1.dgn. In ProjectWise Explorer’s \Integrated MicroStation folder. so the Referenced By tool searches all folders to find other documents that reference a document.dgn in the \Structural folder and select Delete.dgn and select Check In. Click Yes in the verification dialog. Right click P1. and drop it there.dgn references S1. It can be useful to find out which files reference this file so you can decide if it really should be deleted.dgn and select Set > Referenced By.dgn. ProjectWise detects that this file is a member of a set.  Exercise: Moved references 1 2 Continuing in ProjectWise Explorer. drag the file to the \Structural folder. Exercise: Deleted references 1 2 Continuing in ProjectWise Explorer. You know that P1.dgn in the \Structural folder and select Properties. Incorporated 244 Jun-10 . and a warning appears. Double click P1. ProjectWise provides tools to handle these situations. rather than copying it. Holding the Shift key while dragging a file moves it. Under the Windows file system. create a new root level folder named Structural. 3 4 5 6  Click Cancel. There could be many files referencing a file. the move would have resulted in a missing reference. hold the Shift key. 4 Right click S1. All references are located. right click S1. 5  Close the Referenced By dialog. Exercise: Renamed references 1 Right click S1. Note the contents of the Select Reference Documents dialog.

detail views.dgn.dgn is still found. such as a section marker or annotation. change the name to S100. will automatically update the graphics in a reference file. Note that the reference now points to S100.dgn rather than S1.dgn. in the Document section. and elevation views creates types of dynamic views. Click Save. Dynamic View support Dynamic Views is a general name that encompasses different functionality.dgn. Note the Information dialog that informs you of the change to the reference and click OK. 3 4 5 6 Change the file name from S1. Many of the workflows involved with dynamic views involve multi-document sets. checking the file in. even after the name change. Incorporated 245 Integrated Applications . Note that S100. 7 Select Reference from MicroStation’s File menu. Exit MicroStation. Renaming the file did not break the ProjectWise reference file linkage and click OK. In the Properties dialog. where a change to something in a master file. One operation lets users clip models and generate section graphics on the fly. double click P1. Creating section views.dgn to S100. as are detailing symbols with smart fields and links that update automatically as the design evolves.MicroStation Reference Management 2 Click the Advanced button in the File section and select Rename. 8 References without file extensions Reference files that do not have a file extension will not display in MicroStation after being exported from ProjectWise. and then click Close. Jun-10 Copyright © 2010 Bentley Systems. In the \Integrated MicroStation folder.

If the file is already checked out to another user. you must deactivate. but the graphics that are not part of the activated reference are changed to grey so you can see the editable elements. the activating user is presented with a dialog explaining why the reference cannot be activated. In integrated MicroStation. When users activate a reference. the user retains a check out on the file. To use this feature. unlike reference exchange which closes the current file and opens the reference. That process is dependent upon MicroStation configuration variables to discover project content. blocking any other users from modifying that document while they are working on it. A managed workspace is required to support Project Explorer link set harvesting. The master file is not checked in. This check out is maintained until the master file is checked back into ProjectWise. Deactivating the reference does not check the document back in. moving from one to another using activation. activating a reference checks it out from ProjectWise. Incorporated 246 Jun-10 . Right click on an element that is in a reference or right click the file name in the References dialog and select Activate. the position of the graphics on the screen is not changed. on the Reset pop-up menu. on the References dialog’s pop-up menu and the Reset pop-up menu. The user is taken to the exact spot in the reference. without changing the view at all. When edits are complete. dependant reference files are automatically checked out when a dynamic view operation is conducted. If a user is actively working on 3 files. and Release Lock. In place reference activation In place reference activation lets a user make edits to a reference directly from the master file. it is not possible to undo changes. Deactivation Deactivate. but it is editable. are two very different operations. it makes sense to hold the locks until they decide they are ready to release them. • The reason that deactivate does not automatically release the lock is that once the lock is relinquished. It remains checked out. open a master file with references from ProjectWise. Once a reference is activated.MicroStation Reference Management In ProjectWise. they must first open it for write access. Integrated Applications Copyright © 2010 Bentley Systems.

and return to the master file. It may be desirable not to show the dialog. Incorporated 247 Integrated Applications . The only sense in which Deactivate and Release Lock are similar is that Release Lock requires that you first Deactivate the reference you are releasing. the check in dialog shows the master file and all the files that are checked out through the activation and deactivation processes. Use the Release Lock entry on MicroStation’s right click menu. • You can check activated or deactivated files back into ProjectWise from within the MicroStation session. It informs them which reference files are attached and lists their status. Any number of reference files can be activated and deactivated during a session. User Interface -> Show Selective Set Open dialog When this setting is enabled. the view context returns to the master file. the Select Reference Document dialog appears each time a user attempts to check out a document that has reference files. or free the document from within the MicroStation session. automatically checking files in. letting a user check in. This variable controls the visibility of the check in dialog. Reference user properties settings ProjectWise provides several settings related to reference file management and versioning. and the master file is editable again.MicroStation Reference Management When the user deactivates. When the master is checked back in. make necessary edits. the selected element is in a reference. The Release Lock command opens the check in dialog. before checking the master file back into ProjectWise. The Release Lock menu item appears only if the Element Selection tool is selected. Jun-10 Copyright © 2010 Bentley Systems. and that reference was or is currently activated for in-place editing during the current session. Organizations that will use this functionality should consider reviewing the usage of the PW_CHECKINOPT variable. update the server copy. A user can then activate another reference in the set.

In the Select Reference Documents dialog. checking the file in. The downside of this is that it causes reference files to be copied out repeatedly. select Tools > Options.  Exercise: Reference file caching in the working directory 1 2 3 Continuing in ProjectWise Explorer.MicroStation Reference Management Document -> Leave Local Copy and Document ->Use up to date Copy A user’s local working directory is cleaned out automatically when files are checked in. 4 5 6 Double click P1.dgn in the \Integrated MicroStation folder. A copy of all files is left behind to form a cache in it. Enable following if they are disabled. you must open a file with references. The administrator can change this behavior on a per-user basis. Select the Settings tab and expand the Document category. The next time the files are requested. even if they haven’t changed. accepting the default copy out behavior. This speeds operations and reduces network traffic when references are heavily used. 8 Click Cancel. they are compared against the server to see if they are still current before downloading them again. and then click OK: Leave local copy on check in Leave local copy on free Use up to date copy on check out Use up to date copy on copy out To view the results of these changes. The local working directory will not be cleaned out this time. Exit MicroStation. Integrated Applications Copyright © 2010 Bentley Systems. Incorporated 248 Jun-10 .dgn. Click OK to dismiss the Select Reference Documents dialog. indicating that transferring the files from the server is not necessary. note that both the equipment and structural references appear with the status Up-To-Date. 7 Double click P1.

6 Click in the file to release the tank. As a result of the version operation. This is requires special consideration when others are referencing the design in question. the new document appears in the list with the same name. You can add a Version column to the columns in displayed in ProjectWise Explorer so you can see it. Click the color tile in the Attributes toolbar at the top of the application window and change the color to 7 by clicking that tile. two schemes will be created for the equipment file. ProjectWise provides versioning. Note that the original version of the file has been write protected so that changes can only be made to the latest version. The new document does have a different version number. 4 5 When MicroStation launches. although it may not yet be visible. In the following exercise. Jun-10 Copyright © 2010 Bentley Systems.Versioning to Manage the Design Process Versioning to Manage the Design Process Often it is advantageous to return a document to a previous state during the design process. To handle this type of operation. ProjectWise will automatically assign the version number based on rules defined for the datasource. Double click the new version of the file. click the tank on the left so that handles appear around the tank.dgn and select New > Version.  Exercise: Advancing a version 1 In ProjectWise Explorer. Incorporated 249 Integrated Applications . in the \Integrated MicroStation folder. Recall that the piping file has already referenced the equipment file. right click E1. 2 3 Click OK in the New Document Version dialog.

reference linkages always point to the most recent version of a document. Since P1. There are now three versions of the file. checking the file in.dgn now references.dgn and look at the tank color to see that this is true. the original equipment scheme should now be reinstated in the piping file. This shows the version of E1. Click Close to close the New Document Version dialog.Versioning to Manage the Design Process 7 8 9 From MicroStation’s File menu. When prompted whether you want to change this version to become the active document. click Edit.dgn in the history list at the bottom.dgn needs to regress to the previous version. select P1. The original version becomes the most recent version in the document revision history. Versioning datasource and user properties settings Datasource settings Open the Properties dialog for the Datasource in ProjectWise Administrator to access these settings.dgn will always reference the latest version of E1. Within ProjectWise. 10 Exit MicroStation. shown in the bottom pane and click Change. Incorporated 250 Jun-10 .dgn that P1. 2 In the New Document Version dialog.  Exercise: Regressing a version 1 Right click the most recent version of E1. 3 4 5 6 Double click P1. Integrated Applications Copyright © 2010 Bentley Systems. Click OK in the Select Reference Documents dialog.dgn.dgn and select New > Version. Check E1. Now let’s assume E1. click OK. The dialog expands to show all previous versions. Note the color of the large tank.dgn in. Select the previous version. Select the Settings tab in the Properties dialog.

assuming the user has permission to do so. Enabling Document having versions can be moved lets you override this. By default. Document -> Create Version Determines whether a user has the privilege to use the New Version command. • • • • User properties settings The following settings are accessed from Tools > Options in ProjectWise Explorer. Enabling Put created version into first workflow state having create permission lets you specify that the new version will be created into the first state where a user has create permission. Incorporated 251 Integrated Applications . the check box in ProjectWise Explorer will be on by default when a document that has no versions.). documents that have versions cannot be moved to a different folder. whenever a document is added to a flat document set. is added to a flat document set. new documents have their version string set to null. the check box in ProjectWise Explorer will be off by default. When this setting is off. Enabling Use Numeric Version strings lets you specify a numeric versioning sequence. or the active version itself. document versions will increment using alphabetic characters (A. Select the Settings tab in the Properties dialog. Enabling Generate version string for first document version lets you specify a version string for new documents.Versioning to Manage the Design Process Versions • By default. C. Use active version in flat sets controls the default status of the new Always Use Active Version check box that now appears in the Set Contents window in ProjectWise Explorer. B. By default. new document versions are placed into the first state of the workflow. By default. User Interface ->Edit Versions This determines whether a user has the privilege to use the Edit Version button in the New Version dialog. Jun-10 Copyright © 2010 Bentley Systems. When this datasource setting is on. etc.

This workspace profile contains configuration details so ProjectWise can find the workspace. You can right click one of the categories and select New > Configuration Settings Block to create individual configuration settings blocks for each category manually. and standards are met. • Integrated Applications Copyright © 2010 Bentley Systems. Right click the Managed folder and select Import Managed Workspace to import your entire workspace to be completely managed by ProjectWise. all versions of a document display in ProjectWise Explorer. know which components to activate. With this capability. They can be created or imported. There are two types of workspace profile. divided by category. Incorporated 252 Jun-10 . A configuration settings block is a MicroStation configuration variable and its corresponding values. only the most recent version displays. You can create workspace profiles that define the location of MicroStation workspaces or AutoCAD profiles by right clicking the Unmanaged folder and selecting New > Workspace Profile. In order to use a MicroStation workspace within ProjectWise. The Managed folder contains all the configuration settings blocks defined in the datasource. and which users are subject to the workspace. users need not worry about choosing the correct workspace. When disabled. in ProjectWise. which are stored in separate folders under the Workspace Profiles item in the console tree.Configuring MicroStation Workspaces Document List -> Show all versions When enabled. Configuring MicroStation Workspaces ProjectWise can automatically activate MicroStation workspaces by associating them to folders or specific files. • The Unmanaged folder contains all the workspace profiles in the datasource. the administrator must create a workspace profile for the MicroStation workspace.

Configuring MicroStation Workspaces

Note: If both configuration settings blocks and workspace profiles are applied to the

same document, workspace profiles will take precedence.

Unmanaged Workspaces
Unmanaged workspaces, or workspace profiles, define the location of a MicroStation workspace that exists on a local or network drive, outside of ProjectWise. In AutoCAD, profiles are used to store drawing environment settings. This profile is stored in the system registry, and can be exported to a text file with the extension *.arg. Once a workspace profile exists, you or the user can assign the profile to any folder in the datasource in ProjectWise Explorer, through the folder's Properties dialog. Documents inherit their folder's workspace profile, so that when a user opens a MicroStation or AutoCAD document from a folder that has a particular workspace profile assigned to it, MicroStation or AutoCAD opens with the settings defined in the folder's profile.

How to create a MicroStation workspace profile: First, in ProjectWise Administrator, expand the Workspace Profiles icon, right click the Unmanaged icon, and select New > Workspace Profile. On the General tab of the New Workspace Profile Properties dialog, type a unique name. Also, enable the “Allow Users to Override Default Workspace Settings” option. This lets users to change these settings each time they open documents in MicroStation. If this option is disabled, users are forced to use the workspace settings defined here. On the MicroStation Settings tab, set the default MicroStation workspace parameters. These are the location of the workspace root folder and any extra arguments used to open MicroStation. Then define, or navigate to, the appropriate .ucf and .pcf files, and select the appropriate user interface folder.

Jun-10

Copyright © 2010 Bentley Systems, Incorporated

253

Integrated Applications

Configuring MicroStation Workspaces

Customize properties on the MicroStation User Settings tab. You can filter the list of users by selecting a user group. You can select a user from the list and enter the appropriate information for the .ucf and .pcf files, and the appropriate user interface folder. Repeat to configure workspace settings for additional users. When finished, click Apply, and then OK.

Exercise: Create a working folder
1 2

In Windows Explorer, navigate to the \Workspace folder in the class data set. Move this folder to the root of your C: drive. This folder contains a complete MicroStation workspace structure with some custom components.

Exercise: Create the ProjectWise Workspace Profile
1 2 3

In ProjectWise Administrator, expand Workspace Profiles in the console tree and click Unmanaged. Right click on Unmanaged and select New > Workspace Profile. Enter the following: Name: p1200 Description: Project 1200 profile

4 5 6

Click the MicroStation Settings tab. Click the browse button, next to the Root directory field. Select the C:\Workspace folder, and click OK.

7 8 9

Click the browse button, next to the User Configuration File Name field. Select pwise.ucf from the \users sub-folder and click Open. Click the browse button, next to the Project Configuration File Name field.

Integrated Applications

Copyright © 2010 Bentley Systems, Incorporated

254

Jun-10

Configuring MicroStation Workspaces

10 Select GeneralPW.pcf from the \projects sub-folder and click Open.

11 Click OK.

Exercise: Create folders and apply the workspace profile
1 2

In ProjectWise Explorer, create a new root level folder named Workspace Profiles, using no environment. In Windows Explorer, navigate to the \Workspace Profiles folder in the class data set, drag the sub-folders from that folder into the new ProjectWise folder, and drop them. Press F5 to refresh. Expand the Workspace Profiles folder structure in the datasource list. Open the Properties dialog for the WkspExample folder. Click the Workspace tab. Change the Workspace type to Workspace Profile. Change the Workspace Profile to p1200 and note the values that are applied from the workspace profile. Click OK.

3 4 5 6 7 8 9

Exercise: Using workspace profiles
1 2

In ProjectWise Explorer, double click the file \Workspace Profiles\WkspExample\Standards.dgn. In MicroStation, expand the Levels option list at the top left of the application window.

You see a list of levels.
3

Select Element > Dimension Styles.

Jun-10

Copyright © 2010 Bentley Systems, Incorporated

255

Integrated Applications

Configuring MicroStation Workspaces

Dimension styles are present. The p1200 workspace includes DGN Libraries. You can find them in C:\Workspace\projects\GeneralPW\dgnlib.

Levels and Dimension Styles from the DGN Libraries

These files define standard configuration items such as levels, text styles, dimension styles, etc. When this workspace is active, those configuration items are pre-defined so the user doesn't have to worry about them, and standards are met.
4 5 6

Exit MicroStation, checking the file in. Open Standards.dgn’s Properties dialog. Click the Workspace tab. Note that the document’s Workspace Profile is set to p1200. It is possible to assign a workspace profile at the document level if you want. Note the inherited from information in parenthesis next to the profile name (WkspExample). This indicates that the workspace profile is not assigned directly to the file, but is being inherited from the folder Workspace Example.

7

Close the document properties dialog.

Workspace profiles and web parts
If you have ProjectWise Web Parts users attempting to view DGN documents in folders that have workspace profiles associated to them, the ProjectWise Publishing Server must have access to the files pointed to by the workspace profile, whether the it points to a local drive or network drive. ProjectWise Publishing Server needs access to the plot drivers in the workspace pointed to by the workspace profile. When a user selects to view a DGN in ProjectWise web parts, ProjectWise Publishing Server is really plotting the DGN, so it needs access to the plot drivers that it normally finds in its own workspace folder. However, if a workspace profile is assigned to the ProjectWise folder, ProjectWise Publishing Server looks in the location to which the workspace profile points, rather than its own workspace directory.

Integrated Applications

Copyright © 2010 Bentley Systems, Incorporated

256

Jun-10

Configuring MicroStation Workspaces

Note: MicroStation does not deliver the DPR.PLT driver that the ProjectWise

Publishing Server needs to generate the DPR file. ProjectWise Publishing Server does. If users are receiving an error such as “engine failed to generate image/rendition file”, make sure you have a copy of the DPR.PLT in the workspace to which the workspace profile points. For example, copy DPR.PLT from C:\Bentley\Program\BentleyPublisher\Engine\Workspace\System\plotdrv to S:\Workspace\System\plotdrv.

Managed Workspaces
Using the Workspace Import Wizard in ProjectWise Administrator, you can import your entire MicroStation workspace into ProjectWise where it can be fully managed. The process of importing your workspace using the Workspace Import Wizard involves a few steps. 1. Import the variables and their values from your workspace's .cfg and .ucf files into ProjectWise, thus creating configuration settings blocks. 2. Import your workspace files and folders into ProjectWise. Though you can do this using the Workspace Import Wizard in ProjectWise Administrator, you can also do this by dragging the content into ProjectWise Explorer. 3. Import data to ProjectWise that is specific to MicroStation users and projects. 4. Take the new configuration settings blocks and replace the hard-coded local paths with the new ProjectWise paths. The new configuration settings blocks will contain variable information, as it appears in the source configuration files. No attempt to replace hard-coded local paths is made during the initial import process. That is done in another wizard session in which redirection, or remapping, is involved.

1. How to import local MicroStation variables and their values: First, right click the Managed icon under Workspace Profiles in ProjectWise Administrator’s console tree and select Import Managed Workspace. Click Next in the Workspace Import Wizard. Then, on the Choose Desired Action page, enable “Import MicroStation Configuration Files to ProjectWise Configuration Settings Blocks”, and then click Next. On the Choose a MicroStation Installation and Workspace Root page, verify that the MicroStation installation and workspace listed are the ones from which you want to import data. Enable “Create configuration block for

Jun-10

Copyright © 2010 Bentley Systems, Incorporated

257

Integrated Applications

Configuring MicroStation Workspaces

workspace root variable”, and then click Next. On the Workspace Configuration Files page, click “Scan Workspace”. When the scan is done, click Next and the page shows you all the configuration files for import. Click Next. Add or remove any of the files as needed, and then click Next. When processing is done, click Next. On the Configuration Settings Blocks page, review the Settings Blocks that will be created. You can change block names and reassign the ProjectWise level using the option lists, or you can remove blocks you do not want to create. When finished, click Next.

On the Please review configuration file settings page, click Import. When the import is finished, click Next. You should now open the newly created configuration blocks in ProjectWise Administrator to verify the import. When done, click Next. The End of Action page always lets you move on to the next step in the workflow, or you can close the wizard.

2. How to import your workspace files and folders into ProjectWise: First, enable “Import Data to ProjectWise from the File System” on the Workspace Import Wizard’s End of Action or Choose Desired Action page, and then click Continue or Next. On the Import and Validate ProjectWise Folder Structure and Documents page, select the workspace you want to import in

Integrated Applications

Copyright © 2010 Bentley Systems, Incorporated

258

Jun-10

Configuring MicroStation Workspaces

the Local File System list. Then, in the ProjectWise list, select the target folder. Once you select a folder in both lists, click the Map button.

Now click Validate. Select an item in the list on the left to see the status of the item in ProjectWise. If there are problems, you can remove items by unchecking them and then clicking Remove Unchecked Items. Alternatively, click Resolve to upload all missing or mismatched items to ProjectWise. If there is nothing to resolve, just click Finish.

3. How to import data specific to MicroStation users and projects: First, enable “Import data to ProjectWise, specific to MicroStation users and projects” on the Workspace Import Wizard’s Choose Desired Action page, and then click Next. On the Choose a MicroStation Installation and Workspace Root page, verify that the MicroStation installation and workspace displayed are the ones from which you want to import data, and then click Next. When the Find Workspace Data page opens, click the Scan Workspace for Users, Projects and Data button. When scanning is finished, click OK, and then click Next. When the Find Workspace Data page returns, click Next.

Jun-10

Copyright © 2010 Bentley Systems, Incorporated

259

Integrated Applications

Configuring MicroStation Workspaces

On the Import and Validate MicroStation Workspace Data to ProjectWise page, in the Local File System list select the workspace you want to map, select the target folder in the ProjectWise list, and then click the Map button.

Now click Validate. Select an item in the list on the left to see the status of the item in ProjectWise. Here again, you can items folders if needed, or click Resolve to upload all missing or mismatched items to ProjectWise. If there is nothing to resolve, just click Finish.

4. How to replace local paths with ProjectWise paths: First, enable “Update ProjectWise Configuration Settings Blocks to Refer to ProjectWise Data” on the Workspace Import Wizard’s Choose Desired Action page, and then click Next. On the Choose a MicroStation Installation and Workspace Root page, verify that the MicroStation installation and workspace displayed are the ones from which you want to import data, and then click Next. On the Update Configuration Settings Blocks page, click Add to add the existing configuration settings blocks you want to update. Select them from the Select Configuration Blocks dialog and click OK. Click Next when done. After processing, click Next. On the Remap Paths and Variables page, select the CSB variables you want to map on the left, and in the ProjectWise list select the target folder. Then click the Map button. Repeat this step for each variable you want to update, and then click Next. The next page lists all the substitutions that will be made to variables in the configuration settings blocks you have selected. If you would like to change anything, click Back. When ready to remap, click Update.

Integrated Applications

Copyright © 2010 Bentley Systems, Incorporated

260

Jun-10

tmp command line switch to the executable. right click one of the managed workspace categories and select New > Configuration Block.cfg. Support for conditional expressions The following conditional expressions are supported in CSBs: • %include (replaces the “Linked Blocks” UI entry in the XM Edition) • %if • %else • %elif • %endif • %error The following data types can be used in a directive declaration: Jun-10 Copyright © 2010 Bentley Systems. On the General tab of the New Configuration Block Properties dialog. expand the Workspace Profiles icon. Then. type a name and an optional description for the configuration block. where the # sign represents the ID number of the configuration settings block from the database. ProjectWise will export the linked configuration settings blocks to $(PW_WORKDIR)\workspace\ID#. and then expand the Managed icon below it.  How to create a configuration settings block: First. The temporary CFG file that is created will also have the variable PW_MANAGEDWORKSPACE > #. When MicroStation is launched. These blocks are assigned different configuration priority levels. Next.tmp that includes each of the Configuration Settings Blocks linked to the DGN. on the Configuration tab.Configuring MicroStation Workspaces Creating individual configuration settings blocks You can store MicroStation configuration variables and their corresponding values in configuration settings blocks in ProjectWise. add directives or variables to the configuration settings block as needed. It will then launch MicroStation using those configurations by including the master CFG file with a – wc[path][name]. It will then also create a temporary master CFG file $(PW_WORKDIR)\workspace\name. Incorporated 261 Integrated Applications . The procedure follows.

Configuring MicroStation Workspaces • String • CSB • CSB by mask • ProjectWise Document • ProjectWise Folder To use CSB by mask. Test to see if a CSB exists. the directive must be broken up in separate lines to create the conditional statement. and if so. if not include a different CSB. if not assign a different folder to the variable. if so include a specific CSB. if so append the folder to a variable. if not include a different CSB. and if so. Test to see if a variable is defined. if so include a specific CSB. Test the value of a variable. Test to see if specific multiple CSBs are defined. include the CSB in the configuration. Test to see if the value of a variable is defined to a specific ProjectWise folder. The CSB Mask will scan for CSBs in all levels. and include a CSB with the value. the mask is a wild card expression and any CSB that matches that expression will be included. Incorporated 262 Jun-10 . currently there is no way to limit the mask to a certain level. and if so. Test to see if any specific CSBs are defined. include another CSB. • • • • • • Test to see if a variable is defined. define another variable. Some supported workflows are a follows. • Integrated Applications Copyright © 2010 Bentley Systems. Note: When testing for ProjectWise objects.

How to create a new directive and add it to a configuration settings block: First. set the values and click OK.Configuring MicroStation Workspaces • •  Check is a local system variable is set. In the Modify Directive dialog. The Configuration Settings Block Mask will scan for configuration settings blocks in all levels. Note: To use Configuration Settings Block By Mask. the mask is a wild card expression and any configuration settings block that matches that expression will be included. A ProjectWise project must be used. In the Edit Value dialog. currently there is no way to limit the mask to a certain level. and then expand the Managed icon below it. expand one of the managed workspace categories and double click a configuration settings block to open its Properties dialog. add the conditional expression statements and click Add. It will return the moniker of the ProjectWise project. Since this discovery happens when the file is launched. Dynamic project configuration A new variable. Incorporated 263 Integrated Applications . and select Add Directive. This variable is used in conjunction with _DGNDIR in a CSB to get the project moniker of the DGN file being opened. Select the Configuration tab. can be used in a CSB. Test to see if the value is less or greater than a value and sets another variable’s value accordingly. the macro will not return any value and any relative paths that are constructed will only have the additive statements such as /CELL or /DATA in the paths. DMS_PROJECT. Jun-10 Copyright © 2010 Bentley Systems. Then. If a folder is used. expand the Workspace Profiles icon. relative paths can be used with the assurance that the correct definitions will be applied. click the first icon at the upper left (+).

For example. the variables will be unresolved. Therefore. This lets a sub project exist. and using a standard set of project folder names. for example. DMS_PARENTPROJECT will not default to the first project if the parent does not exist. DMS_PROJECT and Integrated Applications Copyright © 2010 Bentley Systems. and then the relative paths are processed. operates the same way that DMS_PROJECT does. MS_CELL = _USTN_PROJECTROOT/CELL. letting any project that has the same structure and uses the same workspace to be imported inherit the same configuration.Configuring MicroStation Workspaces For example. Additionally. with the workspace configuration defined at the top level project. projectroot. Incorporated 264 Jun-10 . Assign the following configuration variable _USTN_PROJECTROOT. DMS_PARENTPROJECT. and enter $(DMS_PROJECT(_DGNDIR)) for a value. configuration can be assigned at the 2008 Projects level. new projects can be added without the need for any additional configuration. such as cell or data. it returns the parent project of the project that contains the dgn file. A similar variable. the project is discovered. assigned as part of the _USTN_PROJECTROOT variable using DMS_PROJEC T. MS_DATA = _USTN_PROJECTROOT/DATA. create a CSB. Create a CSB at a lower priority level. and then be appended with the correct folder name. to define all the project variables.  How to build the configuration: First. When a dgn file is opened. configuration can be created once. they will be populated with the correct project moniker. but instead of returning the project that contains the dgn file. meaning it will be processed after the projectroot CSB. if a datasource has the following structure. Since the _USTN_PROJECTROOT variable is dynamically determined before the MS_CELL and MS_DATA configuration variables.

in ProjectWise Administrator. open the datasource Properties dialog. all folders a user has access to will automatically inherit the assigned configuration settings blocks during that user’s session. and then OK. By default. in the user Properties dialog. to provide a variety of pathing options.  How to assign a CSB at the datasource level or user level: First. Select a settings block and click OK. Select the Workspace tab and set Workspace type to Managed. Variables to Exclude From Copy Out Copying variables can take a lot of time depending on the size of your workspace. Right click a workspace level name and select Add Association. In the New Variable Properties dialog that opens. set the level association. Click Apply. You can remove any of these variables from the list so that ProjectWise will use them. right click a folder in ProjectWise Explorer and select Properties to open its Properties dialog.Configuring MicroStation Workspaces DMS_PARENTPROJECT can be used in conjunction with other macros.  How to add a variable to the list of excluded variables: First. Applying CSBs in ProjectWise Explorer  How to assign a CSB to a folder or project First. in the datasource Properties dialog. type the name of the MicroStation configuration variable you want to add to the exclude list. in the Workspace Profiles. Incorporated 265 Integrated Applications . or a specific user’s Properties dialog and select Managed Workspace tab. Then. In ProjectWise Explorer. such as parentdevdir and build. A dialog opens if there are configuration settings blocks of this type in the datasource. right click Variables to exclude from copy-out and select New > Variable. in ProjectWise Administrator. or you can add to the list of excluded variables. Applying CSBs in ProjectWise Administrator You can apply configuration settings blocks globally at the datasource level. and to specific users. When Level associations is set to Jun-10 Copyright © 2010 Bentley Systems. Managed section of the console tree. Click OK. there are certain configuration variables that ProjectWise will not use when managed workspaces are in use.

 How to create a configuration variable for a personal workspace First. select the Operation type '=' – Assignment' and the Value type ProjectWise Explorer Folder. In the Name field of the New variable dialog. This example will configure _USTN_PROJECTSROOT. If a dialog opens. Configuring a User’s Personal Workspace Personal workspace settings allows user-specific workspace configuration for managed workspaces. To assign a configuration settings block right click the name and select Add Association. This is the configuration block where any changes in the variables made from the MicroStation workspace configuration dialog will be stored. These settings do not have any effect on workspace profiles. Then. in ProjectWise Explorer. so you would type that in the Name field and click Add. it means there are configuration settings blocks of the type in the datasource. as well as any sub-folders. select Tools > Options. Once assigned. the list only shows configuration settings blocks explicitly assigned to this folder. or inherited from a parent folder above. Configuring personal workspace settings in ProjectWise Explorer If this is the only place that contains managed workspace data. to the right of the Integrated Applications Copyright © 2010 Bentley Systems. Click OK to close the Properties dialog. These configuration variables will be applied after variables in all other configuration blocks are processed. in the user Properties dialog. Click the first icon. When set to Object & Inherited. the list shows all configuration settings blocks assigned to this folder whether explicitly assigned. In the Edit Value dialog. Select a settings block and click OK. the configuration settings block is also assigned to any documents in the folder. Click the Browse. select the Personal Workspace tab. Incorporated 266 Jun-10 .Configuring MicroStation Workspaces Object. enter a name for the variable. the managed workspace will be ignored so as not to interfere with workspace profiles settings. You can apply a configuration settings block to individual documents on the Workspace tab of their properties dialog.

ProjectWise workspace profiles support AutoCAD profiles. department. On the General tab of the New Workspace Profile Properties dialog. create a profile in AutoCAD and export the profile to a location on your system.AutoCAD Workspace Profiles Value field. select the target folder. Do not import the profile into ProjectWise. ProjectWise populates the list with available profiles in AutoCAD. enter the name of. type a unique name. right click the Unmanaged icon and select New > Workspace Profile. In ProjectWise Administrator. Click OK to exit the dialogs. AutoCAD Workspace Profiles In AutoCAD.arg file). This allows for the set up and assignment of project. therefore controlling the user's environment. Incorporated 267 Integrated Applications . MicroStation Title Blocks ProjectWise lets you use values from database fields to fill place-holding fields in a MicroStation or AutoCAD design. and then click OK. On the AutoCAD Settings tab. profiles are used to store drawing environment settings. then OK. a profile that matches an existing profile in AutoCAD. By default. This feature is typically used to populate title Jun-10 Copyright © 2010 Bentley Systems. and can be exported to a text file (saved out as an *.  How to create an AutoCAD workspace profile: First. The profile is stored in the system registry. click Apply. or corporate profiles. in the AutoCAD Profile Name or Path field. or browse to. When finished.

and then assign it the p1200 workspace profile. 4. Prior to using this feature you must determine which design fields will be populated. This must match the name of the tag set exactly. it is not possible to use text elements as placeholders. Create the Attribute Class. folder. find it in the class data set Integrated Applications Copyright © 2010 Bentley Systems. so ProjectWise Attribute Exchange uses MicroStation tag elements. These conditions can be changed at any time depending on the action to be performed. These are the names of the tags contained within the tag set with a maximum length of 30 characters in lowercase. 2 Create a new root level folder named Attribute Exchange using the pwclass environment.MicroStation Title Blocks blocks in a design with values entered into the ProjectWise document properties dialog.  Exercise: Create and populate a folder for the exercises 1 In ProjectWise Explorer. Establish the conditions for update. and then establish mapping from their respective ProjectWise properties. 3. Creating MicroStation attribute exchange rules Creating the attribute exchange rules in ProjectWise Administrator requires multiple steps. Incorporated 268 Jun-10 . Then create tags with a maximum length of 30 characters in lowercase that represent the fields you want to display in your title block. The first thing you must do is create a tag set in MicroStation with a name with a maximum length of 6 characters in lowercase. 1. This item is the name of a MicroStation tag set. set the Interface to Default. Bind the attribute to a property type. Create the attributes for the class. Note: If you have not imported this environment. As MicroStation text elements do not have unique IDs. This must match the name of the tag set exactly. You will then likely create a cell from this tag. 2. with a maximum length of 6 characters in lowercase.

enter the following: Jun-10 Copyright © 2010 Bentley Systems.dgn in the Format field and click OK.dgn’s properties dialog.: 1 of 8 Size: A1 4 Select the More Attributes tab. enable “Create a new document” and click OK. set the Department to Engineering and click Save. select Copy. drag the files from that folder into the new ProjectWise folder. enable “Change the name”. and then right click in the document list and select Paste. On the File name tab. 4 5 6 7 8  Exercise: Establish attributes 1 2 3 Open A101.MicroStation Title Blocks 3 In Windows Explorer. On the Create a Document dialog’s Name tab. and drop them. enable “Change the name” and type A101 in the Format field. and then click Save: Approvedby: Engineer Drawnby: Drafter Discipline: Arch Shtno. Incorporated 269 Integrated Applications . enter the following. In the Select an Action dialog.dgn. Click the Attributes tab. Right click no_TB. type A101. Click Yes. On the General tab. navigate to the \Attribute Exchange folder in the class data set.

The cell pwtb contains only a point element that will not print. Zoom In on the title block. Select Utilities > Key-in to open MicroStation’s Key-in browser.MicroStation Title Blocks Type: Plant 5 6 Click Save. In the References dialog. a left mouse click. and then press Enter: ac=pwtb This activates the cell named titleblock for placement. The placeholders are MicroStation tag data attached to the point element. Incorporated 270 Jun-10 .dgn from the Attribute Exchange folder with the logical name border. Select File > References from MicroStation’s main menu bar. to place the cell at this location. Integrated Applications Copyright © 2010 Bentley Systems. Placeholder tags  Exercise: Prepare the placeholders 1 2 3 4 5 6 7 Double click A101.dgn to open the file. type the following. Close the document properties dialog. 8 Move the pointer until it snaps to the lower right corner of the inner border and enter a data point. Close the References dialog. select Tools > Attach. Attach border. This cell was created to hold tags from the pw tag set.

Right click it in the console tree and select New > Attribute. click Next. Click Add. Jun-10 Copyright © 2010 Bentley Systems.MicroStation Title Blocks 9 Select Element > Tags > Define. 11 Exit MicroStation. Expand the MicroStation Title Blocks item to show the new attribute class. 10 Select File > Save Settings. 3 4 5 6 Type the name pw and click OK. 7 8 9 Type the name approvedby and click Next. In the Tag Sets dialog. that the tag set is named pw. When the Welcome page appears. expand Attribute Exchange Rules in the console tree. before synchronization can occur you must create mappings from the ProjectWise environment attributes to the tags in the design. Attribute exchange rules The design is now ready so you can synchronize attribute information with ProjectWise. containing the tags that match the attribute classes you mapped. The attribute name must match one of the MicroStation tags within the pw tag set. Enable the Environment property radio button and set the environment to pwclass. You saw previously in the Tag Sets dialog. checking the document in.  Exercise: Establish the attribute exchange mapping 1 2 In ProjectWise Administrator. Right click MicroStation Title Blocks and select New > Attribute Class. However. Incorporated 271 Integrated Applications . you see a tag set named pw. These hold the data. The attribute class name must match the tag set name within MicroStation and it is case sensitive.

The available options are: • • • • When the document is opened When the document is checked out When the document is copied out When the document is exported You can use any combination of the three options. Attribute name (MicroStation tag) dept description drawnby modified name revision type size pwclass pwclass pwclass Environment Property type Document Property Document Property Environment Property Document property Document property Document property Environment property Environment property ProjectWise Attribute name DocDepartDesc DocDescription drawnby DocFileUpdateDate DocName DocVersion type size Establish update conditions Once attribute mapping is complete. 12 Repeat the process to map the remaining attributes. and then click Next. Integrated Applications Copyright © 2010 Bentley Systems. 11 Click Next. click OK. and then click Finish. Incorporated 272 Jun-10 .MicroStation Title Blocks The attribute list updates to show just those attributes that are part of the pwclass environment. 10 Select the approvedby attribute. You have established the mapping for the approvedby attribute. you must decide when the exchange should take place.  Exercise: Note attribute update conditions 1 In ProjectWise Administrator. right click MicroStation Title Blocks in the console tree and select Properties.

followed by m and the space bar. rather than typing the entire command. Observe the title block area. checking the file in. it is recommended that you enable just the first option.  Exercise: Test the attribute exchange 1 2 In ProjectWise Explorer. This demonstrates the capability to exchange attribute data from ProjectWise to MicroStation. Using the Attribute Exchange Rule command allows you to create.AutoCAD Title Blocks Hint: For best performance. This is activated from the ProjectWise Administrator Attribute Exchange Rules object.dgn. Click Save. and then press Enter: titleblock modify Hint: Enter ti and press the space bar. Click OK in the Select Reference Documents dialog. The ProjectWise document properties dialog appears. ON the Attributes tab. You see the updated field in the title block. You see the placeholder tags are replaced with the actual document properties. You are ready to test the exchange using MicroStation. delete and amend the links between these tags and the attributes. Now you can make any required changes and both ProjectWise and the design will update at the same time. Note that the same techniques apply to AutoCAD and Microsoft Office Applications. The attribute exchange is now completely configured. change approvedby to Manager. It is also possible to change the attributes from within MicroStation. Exit MicroStation. 2 Close the Properties dialog. double click A101. 6 AutoCAD Title Blocks The Attribute Exchange Rules control the way in which the block attributes placed in your drawing files are bound to the attributes in your database. Incorporated 273 Integrated Applications . and then Close. 4 5 On the General tab. change the Description to First floor plan. Jun-10 Copyright © 2010 Bentley Systems. 3 Enter the following into the Key-in browser.

MicroStation Link Sets In ProjectWise Explorer. When defining the block. This block could be a title block or an entire drawing frame. link sets act as a shortcut or pointer to the actual document. In ProjectWise Explorer. They can only be created with ProjectWise Plot Organizer or from within MicroStation V8 XM Edition or later.  How to define and place blocks in AutoCAD The first step is to create a block containing the attribute data that will hold the title block data in an AutoCAD drawing file. You create the attribute classes and attributes in ProjectWise Administrator. In ProjectWise Administrator. binding selected properties or attributes in the ProjectWise database to the attributes contained within the block placed in your DWG file. define the update conditions. Then. define the attribute exchange rules for AutoCAD in ProjectWise Administrator. define the blocks and attributes in AutoCAD. DGN link sets cannot be created in ProjectWise Explorer. and these settings will be reproduced when Attribute Exchange takes place. When you import or create DGN files containing link sets in ProjectWise. Integrated Applications Copyright © 2010 Bentley Systems. place the block in the drawing file or creating a wblock for placement and future use. or a number of tags. Then. remember that the active settings for elements apply to each placed attribute. which is a sub-folder of the Documents root folder. Incorporated 274 Jun-10 . Any link sets that exist in folders that are not in any project are displayed in the main Link Sets tree. using the same steps outlined in the MicroStation Title Blocks section. link sets and their links display in the Link Sets tree under the project in which the link set exists.MicroStation Link Sets  How to Set up an AutoCAD Title Block First. you must scan for references and link sets to make ProjectWise aware of any existing link sets. Next. Note: Blocks can contain one. You can use the file itself as a template within ProjectWise when creating new drawing file. create a block containing the attribute data that can be placed in any drawing file. Note: You cannot store link sets in DWG files.

click Next. This is because the files have been scanned and link sets have been found.dgnlib. but it is not required. Jun-10 Copyright © 2010 Bentley Systems. The file containing the link sets begins to open and you see the Select Reference documents dialog. and then click Next. Enable only the Scan for DGN Link Sets check box. Progress is displayed and then a summery will display. Click Next. highlight the datasource and press F5 to refresh the datasource list. You will not do a Proximity search to scan for documents in other folders. Right click on the first one and select Open. and then click Finished. and click Next. On the Master Folder Settings page. In the Wizard. Expand the MicroStation V8 XM Edition folder. select Tools > Scan References and Link Sets. Click the + next to Documents to expand the tree.MicroStation Link Sets  Exercise: Scan for link sets 1 2 3 4 5 6 In ProjectWise Explorer. you can enter a name and location for a log file. Expand the MicroStation V8 XM Edition folder and then the Building folder. locate the Building folder. Incorporated 275 Integrated Applications . Enable the Enable Priority Search option. On this page. 6 7 Note that the status is Needs Refresh. select MicroStation V8 as the Application Type. then Linksets. and then click OK. 7 8 Click Next. enable the check box for the folder. Click Next. Exercise: Review link sets 1 2 3 4 5 In ProjectWise Explorer. You can review the log file if desired by selecting Yes or you can review it in the location that you saved it in later. and then click Next. enable the check the box next to it to include sub-folders. and then expand Plans. Expand LinkSets. Click OK. select the Building folder. 9  Click No.

The DMSSET variable named SHEETSETMODE is used to control whether AutoCAD Sheet Set functionality is integrated with ProjectWise. the Check In icon in the Link Sets dialog is available. The DGNLIB containing the link sets has an addition to its icon. If you make changes to a link set in the active file. Note that the Check In icon in the Link Sets dialog is gray and is unavailable. checking the file in. Exit MicroStation. When you are using link sets in the active file. 9 Selecting the correct link set source Link sets come from one of three sources: configured DGN libraries. you can use Active File as the source of your link set. it is easiest to use Selected File as the source of your link set. the link is checked out. AutoCAD Sheet Set Manager Integration Sheet Set Manager is integrated with AutoCAD 2007. 2009. which is not being checked in yet. Integrated Applications Copyright © 2010 Bentley Systems. 8 In ProjectWise Explorer. the active file. you cannot check in changes to the link set at this point because the link set resides in the open DGN file. or the selected file. 2008.AutoCAD Sheet Set Manager Integration In ProjectWise Explorer. they cannot be saved until you select File > Update Server Copy or check in the DGN file. The actual document is also checked out in its home folder. This functionality is the same as if you were using only MicroStation to open the link set. Selected File: If you plan to change a link set. Incorporated 276 Jun-10 . it is important that you select the correct source in the Link Sets dialog. After you select a DGN file and check it out in exclusive or shared mode. you will be unable to modify the link set at this point. Active File: If you want to check out a link set but do not need to save any changes to it until you check in the DGN file or update the server copy. navigate to the Building project’s Dgnlib folder. You can check in changes to the link set or update the server copy at any time. When you are using ProjectWise Explorer to check out link sets and DGN files containing link sets. Configured Libraries: If this is the source of your link set.

AutoCAD Session File Manager Users work with the Sheet Set Manager as they normally would. Incorporated 277 Integrated Applications .NET Framework 2. or exported files. and will change from working session to session. AutoCAD Session File Manager This utility provides better access to managed documents that are opened or referenced in the integrated session. open. or inserts. the audit trail. Session file manager requires . Other AutoCAD Integration Features • ProjectWise provides integration with AutoCAD's File > eTransmit feature. Copied Out. which is delivered with AutoCAD 2007 and on. A display filter is provided to temporarily restrict the display to files that meet the display filter criteria. update server copy.0. If you have an AutoCAD 2004 or higher installed but you do not have .NET Framework 2. you will need to install it. It provides some functionality from the Xref Manager dialog and ProjectWise Explorer from within the integrated AutoCAD session. locate the file in the ProjectWise Explorer tree hierarchy. which lets you package the current DWG file and its related dependent files. The reference file hierarchy can also be filtered to include or exclude the display of referenced images. You can display properties. and store it in the datasource. inside a single ZIP file.0. All information presented in this dialog is in the context of the current session. check in and out. The display in the session file manage can be filtered to only show Checked out. any reference hierarchy or a thumbnail preview of selected file. and free. The session file manager is supported in AutoCAD 2004 or higher. The Details section lists the individual to whom the documents are checked out. Documents that are checked out are indicated by a lock symbol added to the file icon. overlays. such as external references and font files. You can turn the integration for this feature on or off through the new DMSSET variable called ETRANSMITMODE Jun-10 Copyright © 2010 Bentley Systems. Users can navigate the content in the Session File Manager. and ProjectWise is in the background.

you see the ProjectWise Save As dialog so you can save back into the datasource.  How to turn on desktop integration: Navigate to and open the \Program Files\Bentley\ Navigator\config\applpw. when you save. ProjectWise Navigator creates an overlay document to contain the markup.CFG file delivered with ProjectWise Navigator. integration with ProjectWise Explorer is turned off by default. Desktop integration When you launch ProjectWise Navigator from the desktop. Integrated ProjectWise Navigator When ProjectWise Navigator is integrated with ProjectWise users can use it to markup DGN and DWG documents stored in a datasource. To turn on desktop integration. When launching integrated ProjectWise Navigator from the desktop or Windows Start menu. do so in the application’s Properties dialog. you use the ProjectWise File Open dialog to open files form the datasource and. you do not need to set up anything further since ProjectWise Navigator and ProjectWise integrate automatically. If you want to use the default settings. Incorporated 278 Jun-10 . Configuration ProjectWise Explorer Integration The ProjectWise Passport you have for ProjectWise Explorer will automatically work for your installation of ProjectWise Navigator.Integrated ProjectWise Navigator • There is a new DMSSET variable called SHOWMISSINGSHAPES. the ProjectWise Log in dialog opens first. If you want to change settings. When they markup a DGN or DWG document.cfg file for both and uncomment the line beginning with #PWDIR: Integrated Applications Copyright © 2010 Bentley Systems. which is used to control what action integrated AutoCAD takes when you open a document that has missing SHX files. Within integrated ProjectWise Navigator. an administrator must modify the PW.

ProjectWise integration is enabled only for launches # from PW Explorer.) Note that when the overlay document first opens in ProjectWise Navigator. the mark up is stored in a new document. To do this.Integrated ProjectWise Navigator # Define "PWDIR=ProjectWise Explorer install path" here to enable desktop # integration. #PWDIR=C:/Program Files/Bentley/ProjectWise/ Becomes: # Define "PWDIR=ProjectWise Explorer install path" here to enable desktop # integration. called the overlay document. Otherwise. The new overlay document is opened in ProjectWise Navigator. Set > Show Markups that works the same as the Set > Show References command. Related document markups You can create multiple overlay documents from the same reviewed document if necessary. To save it to ProjectWise. Otherwise. save the file. you need to select File > Save or File > Save As in ProjectWise Navigator. There is an option on ProjectWise Explorer’s right click menu. you can either select File > Save As again while the overlay document is still open in ProjectWise Navigator. PWDIR=C:/Program Files/Bentley/ProjectWise/ Make sure that the path reflected here is the path to the ProjectWise Explorer install on the system. Then. or if you are back in ProjectWise Jun-10 Copyright © 2010 Bentley Systems. This lets you add comments without altering the original document content. Incorporated 279 Integrated Applications . it only exists in the temporary local folder. Marking up documents with ProjectWise Navigator When users markup a document. it is not yet stored in ProjectWise. the original document is referred to as the reviewed document. and the reviewed document is attached as a reference to the overlay document. (You can verify this by opening the References dialog in ProjectWise Navigator. Once you create an overlay document. ProjectWise integration is enabled only for launches # from PW Explorer.

i-model Composer Integration Configuration ProjectWise Explorer Integration The ProjectWise Passport you have for ProjectWise Explorer will automatically work for your installation of ProjectWise Navigator. A window opens listing all the overlay documents that exist for the selected DGN or DWG document.  How to find a reviewed document: First.” You can also find the reviewed document from which a particular overlay document was created. you can select the reviewed document again and select Document > Markup. you see the reviewed DGN or DWG document.  How to find overlays created from the same document: First. You can search for and find all the overlay documents that were created from a single reviewed document. Incorporated 280 Jun-10 . select a reviewed DGN or DWG document in ProjectWise Explorer. To see details. select View > Details. Below it. If the selected DGN or DWG document does not have any overlay documents. Integrated Applications Copyright © 2010 Bentley Systems.i-model Composer Integration Explorer. a message appears stating “No Documents Found. and select Document > Set > Show Markups. A window opens displaying the selected overlay document. select an overlay document and select Document > Set > Show References.

i. An i-model is a format used for project information exchange. the ProjectWise Log in dialog opens first. The ProjectWise Browser utility in ProjectWise i-model Composer lets users browse and review the documents and component data managed in a ProjectWise repository. An i-model is read-only and is always saved with an . the i-model unifies it in a simple form. Incorporated 281 Integrated Applications . It is not the source content that users create and modify.DGN or .dgn file for each. You can also combine several published i. Desktop integration  How to turn on desktop integration: Navigate to and open the \Program Files\Bentley\ imodelComposer\config\applpw. All design files that can be opened in MicroStation can be published to an i-model. Within integrated i-model Composer.Microsoft Office Integration If you want to use the default settings. resulting in a corresponding i. protected file. Jun-10 Copyright © 2010 Bentley Systems. you do not need to set up anything further since ProjectWise Navigator and ProjectWise integrate automatically. It converts information to a simpler representation. You browse and review from within ProjectWise i-model Composer.dgn files into a single. No matter what format the input data is in. such as when project information needs to be reviewed at a milestone. you use the ProjectWise File Open dialog to open files form the datasource and. you see the ProjectWise Save As dialog so you can save back into the datasource.DWG file into an I. If you want to change settings. Microsoft Office Integration These integrations place a macro inside the Office document. When launching integrated i-model Composer from the desktop or Windows Start menu.DGN file is called publishing. just as shown for ProjectWise Navigator. do so in the application’s Properties dialog. An i-model is a copy meant for information exchange. It publishes the master file and each of its (displayed) references. The process of converting the .dgn extension.cfg file for both and uncomment the line beginning with #PWDIR. when you save. with smaller file size and easy navigation.

find the registry key HKEY_CLASSES_ROOT\PW MS Word\ODMA32\Dialogs\CheckIn. Under that. Under that. and set the value to True. in the users working directory. and set the value to True. and set the value to False. Note: See the on-line Help topic Microsoft Office Integration to find the registry location for each application. Incorporated 282 Jun-10 . Find the registry key HKEY_CLASSES_ROOT\PW MS Word\ODMA32\Dialogs\CheckIn. you can create registry strings for each application. create a string called ShowConfirmation. In the Windows Registry Editor. the standard ProjectWise Check In dialog is replaced with a simple confirmation dialog that prompts the user to “Check in closed document?” They can then click Yes or No. and set the value to True. create a string called SimpleDialog. the document is automatically checked in without any prompting. Automatic check-in When automatic check-in is enabled and you close a checked out document. In the same location. Check-in To enable simple or automatic check-in of documents in integrated Microsoft Office applications. Simple check-in When simple check-in is enabled and you close a checked out document. In the same location. create a string called ShowConfirmation. File > Save behavior The integrated File > Save command in Office applications only saves a changed document locally. Set SimpleDialog to True and set ShowConfirmation to False to enable automatic check-in. Integrated Applications Copyright © 2010 Bentley Systems. create a string called SimpleDialog. Set both SimpleDialog and ShowConfirmation to True to enable simple check-in. They must Check In or Update Server Copy in order to save the changed document to ProjectWise.Microsoft Office Integration Registry strings There are registry strings that can be set to affect Microsoft Office integration and related behavior.

The text fields are linked to ProjectWise so that if the value of the property changes in ProjectWise. This is done using the Custom Properties option in Microsoft Office Word and Excel. and the Attribute Exchange Rules template file idattr. In Office 2007. which is located in the \Program Files\Bentley\ProjectWise\templates directory. Users can also update property values in ProjectWise by modifying the value of the property from the document itself. Disabling integration To disable ProjectWise iDesktop Integration with a specific Microsoft Office application. and then click Add-Ins. It is typically imported into the datasource during datasource creation. Jun-10 Copyright © 2010 Bentley Systems. See the on-line Help topic Microsoft Office Integration to find the registry location for each application. in the application itself. the text field can be updated in the document.Microsoft Office Integration To have File > Save prompt users to Check In or Update Server Copy in one of the integrated applications. click the <application> Options button at the bottom. You can also open the Windows Registry Editor and remove the ODMA32 subkey for each integrated application. Incorporated 283 Integrated Applications . you can modify the ProjectWise Explorer installation through Add \ Remove Programs and turn off integration with the specific application. click the Microsoft Office button.ini. Click Go next to (Manage) Comm Add-ins and turn off the ProjectWise add-in. See the on-line Help topic Microsoft Office Integration to find the registry location for each application. Attribute Exchange for Microsoft Office Documents Attribute Exchange Rules for Microsoft Office lets users insert ProjectWise properties as text fields inside Microsoft Office Word and Excel documents stored in ProjectWise. macros installed as part of iDesktop Integration for Word and Excel. set the value of the Default string to Enable in the appropriate registry key.

On the ProjectWise tab. However. There are BuiltinProperties and CustProperties attribute classes for Microsoft Excel and Word documents. When you click Update Document inside a ProjectWise document. Note: When using attribute exchange in pre-2007 versions of integrated Microsoft Word and Microsoft Excel. then the text field will be blank. you must initialize the document so that the ProjectWise custom properties defined in the delivered Attribute Exchange Rules template are available for insertion. Each class contains a list of ProjectWise attributes that can be inserted into Word and Excel documents that are stored in ProjectWise. Incorporated 284 Jun-10 . Inserting a ProjectWise custom property as a text field will insert the current value of the selected property into a document. if you insert the Folder_Description property and the document's folder has no description yet. You can now insert any of the available custom properties into the document. The setting for Microsoft Office security level is located under Tools > Macro > Security in each application. If there is no current value. since that text field is linked to the Folder_Description property. You can use these. For example. Inserting custom properties If you open the advanced Properties dialog in Word or Excel and click the Custom tab. Initializing documents for attribute exchange Before you can insert a ProjectWise custom property into a document. click Update Document.  How to initialize a Word or Excel document for attribute exchange: Open a Word or Excel document stored in ProjectWise. once a value is defined for that property in ProjectWise.Microsoft Office Integration Importing this file populates the Attribute Exchange Rules > MS Office Attribute Support object in ProjectWise Administrator. the attributes in the delivered CustProperties attribute class populate the Custom tab. or create your own attribute class and add attributes that match the MS Office delivered properties. the Microsoft Office Security level must be set to middle. there is a list of custom properties you can use. then the field will be updated in Integrated Applications Copyright © 2010 Bentley Systems.

On the Insert tab. When the Welcome page appears. select Quick Parts > Field. There are two parts to this process. click Next. Click Next. In the Property list. the other involves creating a custom property of the same name from inside the integrated Word or Excel application. click OK.Microsoft Office Integration the document next time you click Update Document on the Office application’s ProjectWise tab. and then click Next. you can add them. Incorporated 285 Integrated Applications . Click Add. Create another attribute named Drawn By. Enable the Environment property radio button and set the environment to Titleblock. The value of the selected property is inserted into the document. one part involves creating a new attribute under Microsoft Office Attribute Exchange Rules in ProjectWise Administrator. select the ProjectWise document property you want to insert. Select the Engr attribute. using the Titleblock environment and the drawnby attribute. Type the name Reviewed By and click Next. and then click Finish. place the cursor at the point you want to insert a ProjectWise custom property. expand Attribute Exchange Rules in the console tree. select DocProperty. Right click CustProperties and select New > Attribute.  Exercise: Create attributes 1 2 3 4 5 6 7 8 9 In ProjectWise Administrator. Jun-10 Copyright © 2010 Bentley Systems. Folder_Name. For example. Inserting the Folder_Name attribute Adding new custom properties If there are ProjectWise properties that you want to insert into a document that are not in the default list. In the Field dialog. Click OK. Field names list.  How to insert a ProjectWise custom property into a Word document: In an open Word document that has been initialized.

open the properties dialog for Vegetation. 4 5 You must do this for each Word or Excel document so you can insert any available custom properties. and click the Attributes tab. Open the document from ProjectWise Explorer. Integrated Applications Copyright © 2010 Bentley Systems. Click the Microsoft Office Button at the upper left and select Prepare > Properties.Microsoft Office Integration  Exercise: Import files and initialize 1 2 3 In ProjectWise Explorer. leave the Type set to Text. In the Properties panel that opened. 6  Exit Word. click the arrow next to Document Properties and select Advanced Properties. Enter the following: Reviewed By: Engineer Drawn By: Drafter 3 4 5 6 Click Save and then click Close. 7 8 Click the Custom tab. Click the ProjectWise tab at the top of the application window and click Update Document. Create a new root level folder named Office Docs. In the name field type Reviewed By.doc. navigate to the \Office Docs folder in the class data set. make sure the Interface is set to Default. and drop them. and click Add. Exercise: Update the properties 1 2 In ProjectWise Explorer. saving the changes and checking the file in. drag the files from that folder into the new ProjectWise folder. Incorporated 286 Jun-10 . type your name as the value. using the Titleblock environment. In Windows Explorer.doc from ProjectWise Explorer. Open Vegetation.

you must import from the main Attribute Exchange Rules item. make sure you do not click Update Document before you click Update ProjectWise. much like a title block attribute must match a tag set name. manually edit them. 9 In the name field type Drawn By. or you can export individual items. Incorporated 287 Integrated Applications . However. Note: When you are modifying custom property values from inside the document. make sure not to click Update ProjectWise on the ProjectWise tab or the placeholder will populate ProjectWise. If it is just a placeholder. 11 Click the ProjectWise tab at the top of the application window and click Update Document. 10 Click OK to close the dialog. select the Custom tab. leave the Type set to Text. Exporting and importing attribute mappings You can export attribute mappings to an ASCII file format. and click Add. then any changes you made through the Custom tab will be overwritten with the current values from the datasource. and then import them back into ProjectWise.Microsoft Office Integration An attribute name must match the custom property name within an Office document. the Attributes tab would have been populated with the values in this document. Jun-10 Copyright © 2010 Bentley Systems. If you do. and scroll to the custom attributes. If you clicked Update ProjectWise. Values have been updated with those you entered on the Attributes tab of the document’s Properties dialog in ProjectWise Explorer. The value field must have at least a placeholder in it. You can either export the entire Attribute Exchange Rules section. • • Export Mapping includes the bindings for each attribute to an environment Export Mapping as Template excludes the binding and allows either manual editing or import and configuration using ProjectWise Administrator. type any text for the value. 12 Return to the (Advanced) Properties dialog.

Module Review Now that you have completed this module. Incorporated 288 Jun-10 .Module Review  How to export a mapping: First. in ProjectWise Administrator select either the Attribute Exchange Rules object or the individual item. which will take precedence? What are the steps for creating attribute exchange rules? Where do you import attribute mappings? 2 3 4 5 6 7 Integrated Applications Copyright © 2010 Bentley Systems. Then. let’s measure what you have learned. Why would you enable the Show Selective Set Open dialog option for users? Why would you use versioning? What is the difference between an unmanaged workspace profile and a configuration settings block? If both configuration settings blocks and workspace profiles are applied to the same document. select Action > Export Mapping or Action > Export Mapping as. Questions 1 True or False: You can create a ProjectWise Application for multiple product versions. For example. one for MicroStation V8 XM Edition and one for MicroStation V8i. select the required Export location and click Save. In the Save as dialog.

Jun-10 289 Copyright © 2010 Bentley Systems. you will be able to: • • Define projects based on site requirements Backup and restore projects Introductory Knowledge Before you begin this module. Questions 1 2 What is a storage area? True or False: A user can log in to multiple databases simultaneously. Module Prerequisites • Knowledge about the ProjectWise Explorer and ProjectWise Administrator interfaces Module Objectives After completing this module. Incorporated Managing Projects .Managing Projects Module Overview There are best practices that will make ProjectWise administration easier and help your users work most effectively. let's define what you already know.

there may be multiple active projects at each location. a ProjectWise project is created as a folder structure within an existing database. The alternative is a one-to-one project definition where each ProjectWise project is contained in a new database instance.Defining Projects Answers 1 2 The physical folder where all the documents in the datasource exist. with appropriate Environments. or descriptive metadata as well. each project at a particular site would be created as a folder structure within the respective database instance. In this case. Small engineering firms with small to mid-size projects can easily adopt either definition. In many cases. multiple projects are contained within one database instance. security and Workflow. so project structure can be optimized. it may be advantageous to adopt the one-to-one project model. If there is a requirement to turn over the entire ProjectWise database at the end of the project. A likely strategy for an organization of this type would be to implement the one-to-many model. you must decide if you will deliver and receive files only. In this case. Defining Projects When you create a new project you must first determine an organization’s needs and structure the project accordingly. Another factor to consider is contract deliverables. If the contract requires electronic deliverables. In the case of an organization with multiple sites. it would make sense to contain this type it in a database by itself so the entire database can be turned over at the end of the project. Managing Projects Copyright © 2010 Bentley Systems. Projects of this magnitude often include tens or hundreds of thousand documents. Large engineering organizations often work on large projects where project lifecycles are defined in years rather than months. creating a ProjectWise database instance for each site. This is known as a one-to-many project definition. Incorporated 290 Jun-10 . One database instance contains many projects. Then. It is possible to use both project types on one ProjectWise server. yielding hundreds or even thousands of projects company wide. True.

Additional subprojects can be created by placing them under an additional top level project. Files can be easily copied or moved from one datasource to another. multiple database instances. Create necessary security groups. • • • • • Jun-10 Copyright © 2010 Bentley Systems. For performance or security reasons. ProjectWise authentication can be synchronized with a Windows domain server. File extraction processes provide a reason to implement multiple datasources. This project structure will serve as the starting point for each new project. This automates the process of creating new datasources. or ProjectWise servers may be implemented. The one-to-many definition Within an existing database.Defining Projects Project strategy A few factors to consider when establishing a project strategy are as follows. A user can log in to multiple databases simultaneously. but will likely be refined over time. the process of creating a new project involves the following steps. You can create new datasources from a template. Single Sign-On makes it transparent for users to log in to new datasources. • Create a template project folder structure. Incorporated 291 Managing Projects . Copy the template project folder structure to the root folder for the new project. This need be done only once. Add new users as required. Establish storage areas. ProjectWise includes an import/export utility for moving large data structures (projects) from one database to another. database servers. • • • • • • • • • • ProjectWise queries are currently limited to a single database. Apply the security model as required. There is a hard limit of 750 sub-projects per top level project.

All sub-folders created as the template folder structure is copied will inherit their storage area from the new root folder. This would include folder level security as well as document security. the template project can be hidden from most users by applying a restricted group to the root level folder. while separating project files from other projects. this practice provides centralized storage for the new project. access to the template project should be restricted to prevent unauthorized access. • • • • • Establish storage areas It is recommended that each major project be stored in its own storage area. you need to run reference scans on the new folder structure as each new project is created. If necessary. Any documents existing in the template project folder structure are copied to the corresponding folder in the new folder structure. security. the Environment assigned to a sub-folder in the template project will still be assigned to that sub-folder in the new project. and allowing all sub-folders to inherit from the root level. Environments defined in the template project are maintained. Incorporated 292 Jun-10 . ProjectWise storage areas can be created on any node on the network on which the ProjectWise Distribution Service or ProjectWise Integration Server is running. you will designate the master storage area for the new project. Other considerations when creating the template project are as follows: • Storage areas in the template project are ignored. If it is necessary to have reference attachments. they should not have reference attachments. Perfecting the template project will likely take multiple iterations. and Workflows. If not hidden. The template project definition should include the basic folder structure. Environments. As part of that process.Defining Projects Define a template project folder structure A well defined template project is a critical component of the process. In other words. The root folder for each new project is created manually. Managing Projects Copyright © 2010 Bentley Systems. In this case. This way security schema maintenance is minimized. If MicroStation and AutoCAD documents are contained in the template folders. Though not mandatory. Security schemas should be applied to the template project using inheritance at the highest level. the Environment is NOT inherited from the parent folder during the copy process. as it will be continuously improved with feedback from each new project.

Within some organizations. In order to make the new project's root folder visible.Defining Projects Add new users In most cases. At this point. all sub-folders will become visible when the group privileges are applied to the root folder. For this reason. Through inheritance. and that all team members be added to this group. the majority of employees will already have accounts within the ProjectWise database. Jun-10 Copyright © 2010 Bentley Systems. you only need to create the group and add appropriate team members. only the Civil group gets Create and Modify privileges for the Sitework sub-folder. you should wait and apply the security schema after creating the new project folder structure. Incorporated 293 Managing Projects . For instance. the privilege to Read folders) for the group. that the master group for the project should always be applied after creating the sub-folders. Furthermore. it may be advantageous to apply group security to the template project so that this security schema is propagated to each new project. it is conceivable that most of the security schema could be applied to the template project. it is appropriate to establish a security schema for the new project. These will exist from previous projects or from synchronization with the Windows domain controller. Additional groups are required to assign more permissive privileges within the project. Remember though. the security schema associated with the master project group should provide minimal privileges (specifically. Any required new accounts should be created at this time in order to add them to the project master group. and later be applied to the Sitework folder. as you don’t have to assign these groups to the project sub-folders every time a new project is created. a Civil Group is created with those privileges. Only experience will expose the best strategy for a particular organization. Create security groups At this point. it is recommended that a master group be created for the new project. the group is applied to the project AFTER copying the template project. When in doubt however. You would typically start from the security schema for the template folder and note the differences. However each project could include outside contractors who require access to the project. In this case. In some cases. The new project will only be visible to those ProjectWise users who have membership. This saves work.

By implementing inherited security. in which case you (or whomever you are logged in as) will become the owner of the new folders. This is done from ProjectWise Explorer. You may also want to enable Take Ownership. Be sure to log in to the datasource with sufficient privileges to perform the operation. 1. enable Copy Folder Workflow. Incorporated 294 Jun-10 . the number of project participants. This may be quite involved. You also need to assign document privileges per the security guidelines of the project. If you would like to see the hierarchy update during the copy process. Copy Access Control. 2. enable all options. apply the master group to the root folder. follow these steps. This folder will typically be created under the root (Documents) in the datasource console tree. Managing Projects Copyright © 2010 Bentley Systems. On the General tab. enable Update GUI on each operation. allowing all sub-folders to inherit the security defined for this group. Click Copy to start the process. you are ready to assign additional groups and privileges to tune the folder privileges as required for the project. Backup and restore procedures The process for this archive type differs depending on the project definition in use. Applying the security schema The new project structure is created and all that remains is to apply the security schema. This process should be well thought out prior to starting. 6. 3. and Exclude Source Folder. you can minimize the security management burden. depending on the complexity of the project.Defining Projects Copying the template project to the new project You can now copy the template project into the new root folder. Select Copy from the right click menu. At this point. your project is ready for use. at a minimum. Once you have completed the additional security measures. 5. You need to. and remember to use inheritance where possible. Select the template project in the folder hierarchy. 4. Select the root folder for the new project. and the nature of the project. Select Paste from the right click menu and a dialog with options for the copy process appears. On the Advanced tab. Once logged in. the number of folders.

The file will most likely exist. In ProjectWise Administrator. The easiest way to do this is simply to stop the ProjectWise Integration Server service. 4. To restore a single file. Restrict access to the database by stopping the ProjectWise Integration Server service. back up all storage areas used by this project to offline media using operating system tools or off-the-shelf backup tools. 4. Jun-10 Copyright © 2010 Bentley Systems. Log in to the ProjectWise Explorer and view the properties of the document in question. complete the following procedure. From the list compiled in step 1. the back up process is as follows: 1. 2. Full restore To restore the entire project.Defining Projects Full back up one-to-one project definition If the one-to-one project definition is used. including system hostname or IP address. restart the ProjectWise Integration Server service. Restrict access to the database so that the project is in a known and stable condition during the backup. 1. 1. or there is a need to revert to an earlier version. 2. follow the procedure in reverse. restart the ProjectWise Integration Server service. record all storage area definitions used by this project. When complete. Incremental restore In many cases you will need to selectively restore files. Back up the entire database to offline media using tools supplied by the database vendor. and folder name. When complete. Restore the database using tools supplied by the database vendor. but was damaged. Restore all storage areas using operating system tools or off-the-shelf backup tools. Note: These storage areas may all be on the ProjectWise Integration Server or may be distributed on the network to systems running the ProjectWise Distribution Service. rather than the entire database. 5. 3. Incorporated 295 Managing Projects . Note the File Name (as opposed to the Document Name). 2. 3.

You may add other columns as needed. Browse to the temporary folder (where the document was restored) and select the file to attach the restored file to the original document record. If the file you are searching for might exist in multiple folders within the backup. Log in to the ProjectWise Explorer and select View > Choose Columns. Close the View Editor dialog box. In the Properties dialog. This method is sufficient.Defining Projects 3. Restore this file from the backup media to a temporary folder. not the folder name. 8. provided that file names are unique within your project. To restore a single file in a case when the file name isn't sufficient to uniquely identify the document. General tab. It should be a number. Create a new view called Admin. One of the benefits of this approach is that folder names may be changed without adverse effects to the project. and select Import. 8. Folder Name. 5. use the following procedure. 5. 4. Add columns to the new view for Document Name. Click Advanced again. Note the File Name (as opposed to the Document Name). The folder to look in on the archive media is named for the Folder Id in the format dmsXXXXX. and view the properties of the document in question again. you'll need to obtain the Folder Identifier in order to retrieve the correct file from the backup media. and Folder Identifier (Folder Id). Restore this file from the correct folder on the backup media to a temporary folder. 6. Return to the ProjectWise Explorer. Click OK and then save the changes to the document. the folder name would be dms00184. Files are stored in storage areas under folders named per the folder ID. 6. 7. 7. In the example. click Advanced and then select Remove to delete the existing file. File Name. Managing Projects Copyright © 2010 Bentley Systems. You'll only need to do this the first time. Note that it will be five characters long and preceded by leading zeros as needed to maintain the five character requirement. Do not restore the file to the ProjectWise storage area for the folder. Close the properties dialog. 4. such as 184. 3. Incorporated 296 Jun-10 . 1. 9. Browse to the document in question and note the Folder Id column. where the Folder Id will replace XXXXX. 2.

selected projects. Browse to the temporary folder where the document was restored and select the file to attach the restored file to the original document record. 12. or a subset of the database. 10. Incorporated 297 Managing Projects . Return to the ProjectWise Explorer. Using this method the ProjectWise Integration Server service cannot be stopped or the Export Wizard can’t log in. use the ProjectWise Export Wizard for backing up the metadata. all projects. Select Start > Programs > Bentley > ProjectWise V8i > Tools > Export Wizard. 5. including system hostname or IP address. Jun-10 Copyright © 2010 Bentley Systems. and view the properties of the document in question. 6. 3. 4.Defining Projects 9. If selected projects are to be backed up. It is suggested that access to the project be limited by IP address filtering. Full back up one-to-many project definition If the one-to-many project definition is in use you must decide if the entire database. Log in to the datasource as Administrator. Create a temporary folder in which to store the exported files prior to committing to backup media. or select ALL if you're not sure. should be backed up. Do this in ProjectWise Administrator under the general settings for the datasource. and then click Next. the process for performing a full backup on a selected project using the ProjectWise Export Wizard is as follows. Prior to starting the backup process you must prevent users from checking out files by restricting access to the database. Click OK and then save the changes to the document and close the properties dialog. record all storage area definitions used by this project. Once this is done.In the properties dialog. and folder name. 11. 13. Click Advanced and select Import. 2. If the entire database is to be backed up. 1. click Advanced and then select Remove to delete the existing file. refer to the previous procedure for full back up. Select those environments. Choose to export documents From Selected Folders with subfolders and then select the root level folder for the project in question. General tab. You’ll want to select all environments used by the project in question. In ProjectWise Administrator.

etc. This project can then be imported into this or any other datasource. It should be noted that this second procedure could also be used in the one-toone project definition. This allows the process to be automated. Workflow States. Security and Workflow schemas are not captured by this method. Once this has been accomplished. or security schema(s). rather than the administrator having to copy them from each storage area.Defining Projects Note: You can select multiple folders to include all documents for the project. files. Saved Searches. The Export Wizard does not export users and associated group membership. 9. Environment definitions. metadata. Select Export to continue. using the ProjectWise Import Wizard. the exporter provides additional options to include Workflow definitions. Warning: The script file created by the export process is critical as it contains all the metadata mentioned above. When running from the command line. 7. the script file and the actual document files are in the temporary folder specified in the script file. This file will be required should the need arise to restore this project using the Import Wizard. Incorporated 298 Jun-10 . apply the Managing Projects Copyright © 2010 Bentley Systems. you will then need to remove the IP address filter from the database to allow general access again. Once the export Wizard has finished. At this point. Click Finish. • Export command line options As an alternative to running the GUI version of the Export Wizard you can run the export routine from a command line. application definitions. the Export Wizard will export all Folders. Groups. 8. Therefore the user performing the import would own all files and folders. You can now move the contents of the temporary folder to the offline media of your choice. and Departments. using Windows Scheduler for instance. Enter a script file path and name using the temporary folder created earlier. The files are in a sub-folder named files000. however. enable Log to File and enter a log file name. required to restore this data at a future date. It does not. Applications. Only the most recent version of a document is backed up. The advantage of using this method is that all files are copied to the temporary folder automatically. The disadvantages are: • Users. If desired.

Applications. you’ll want to choose Set starting Folder to ROOT unless you have already created a new root folder for the project. 2. Click Import to start the process. Departments. On the first wizard page. see the ProjectWise Explorer on- line Help files. 3. Folders. 1. If necessary. since there is no GUI. or no folders. 9.Defining Projects Workflow to the folders upon import. 7. Select Start > Programs > Bentley > ProjectWise V8i > Tools > Import Wizard and log in to the datasource as the Administrator. When complete. and then close the Import Wizard. You may select an existing folder or choose to set the starting folder to ROOT. Note: You may receive warnings if the project is being imported into a ProjectWise datasource that contains other projects. enable all settings (Environments. These warnings occur when the Jun-10 Copyright © 2010 Bentley Systems. The project can be imported into any ProjectWise datasource. Incorporated 299 Managing Projects . Note: For a complete list of command line options. and Documents). For this reason. In addition. 8. 4. If you are importing the data into a new datasource it should not be necessary to enable these options. Project restoration using the Import Wizard A project that was backed up using the ProjectWise Export Wizard can be restored using the Import Wizard. not just the original. It should not typically be necessary to do this. restrict access to the datasource by establishing IP address filter(s). the process for restoring a project is as follows. 6. The second wizard page pertains to pre-existing folders. close the Message window. 5. On the next page. If necessary. 10. Assuming the ProjectWise datasource already exists. this method is not practical when using the one-to-many database model. select a default storage area and starting folder for the project to be imported. you will not be able to select specific folders. In most cases. you’ll provide the name or browse to the script file restored to the temporary folder. Restore necessary files from backup media to a temporary folder structure. On the third wizard page. The export process will be limited to exporting all folders (and their respective documents). use the ProjectWise Administrator to create any necessary storage areas for the project.

What is a good strategy for handling a situation like this? True or False: It is recommended that each major project be stored in its own storage area. 2 3 Managing Projects Copyright © 2010 Bentley Systems. Questions 1 In the case of an organization with multiple sites. Incorporated 300 Jun-10 . Module Review Now that you have completed this module.Module Review Import Wizard attempts to import an environment or application definition that already exists in the datasource. let’s measure what you have learned. yielding hundreds or even thousands of projects company wide. there may be multiple active projects at each location. True or False: The master group for the project should always be applied after creating the sub-folders.

Spatial Management Module Overview You can set up spatial parameters in ProjectWise Administrator that allow users to relate data on a geographically correct basis. rather than using a hierarchical list. you will be able to: • • • • Work with coordinate systems Defining spatial symbologies Work with background maps Scan for spatial locations Jun-10 301 Copyright © 2010 Bentley Systems. This module shows you how to set up a datasource to use spatial features and how to use spatial features to work with documents based on their geographic location. Module Prerequisites • • Knowledge about the ProjectWise Explorer and ProjectWise Administrator interfaces Knowledge about coordinate systems and background maps Module Objectives After completing this module. Incorporated Spatial Management .

Any ProjectWise document or folder can be associated with a geographical footprint. called a spatial location. Incorporated 302 Jun-10 . or a folder. on a background map displayed in ProjectWise Explorer. let's define what you already know. These let you locate the associated document. The Spatial Management Copyright © 2010 Bentley Systems. Each point on the plane is defined by an x. You could also locate projects or folders and their contents based on their geographic locations. Identifying spatial locations can be helpful for locating facility assets and related information by using locations. 2 Spatial Management Any ProjectWise document or folder can be associated with a geographical location. planar coordinate system in which x measures horizontal distance and y measures vertical distance. Questions 1 2 What is a coordinate system? What is a background map? Answers 1 A two-dimensional. A background map is a backdrop.y coordinate. It shows the contents of a project or folder from a geographical perspective.Introductory Knowledge Introductory Knowledge Before you begin this module. ProjectWise Explorer’s Spatial tab ProjectWise Explorer’s Spatial tab is available when the datasource is configured by and administrator for spatial support. a key map that allows the user to locate a spatial location in a geographical environment. These let you locate the associated document or folder on a background map that is displayed in ProjectWise Explorer.

You select the right background map for your project from the options at the top of ProjectWise Explorer. To assign a spatial location to a document or folder you must assign not only the coordinates. These symbologies show where documents. so it may take few seconds the first time you access a folder associated with a given map. Background maps are added to the datasource by an administrator. The toolbar at the top has display options and map navigation tools. Select View > Show Symbology Legend to add the legend shows the meaning of the different symbologies used in the Spatial view that is currently applied to the background map. the reference coordinate system must be chosen carefully so that all other coordinate systems have a valid transformation path to it. Both objects will be re-projected into the reference coordinate system before comparison. The map displays inside the Spatial Navigator on the tab. Jun-10 Copyright © 2010 Bentley Systems. folders. The reference coordinate system is used to compare objects that are in different coordinate systems. and sub-folders are located on the map. Working with Coordinate Systems Coordinate systems are added using the ProjectWise Administrator. but also a coordinate system that matches the coordinate system assigned to the document or folder. Therefore. The first step in spatial management is adding coordinate systems to the datasource.Working with Coordinate Systems background map that is used is usually published from a server. Incorporated 303 Spatial Management .

right click the Coordinate Systems icon and select Add from Dictionary. When a new coordinate system is created. In the Add Coordinate Systems dialog. Ask means that. The reference coordinate system has an addition to its icon. Incorporated 304 Jun-10 . Custom coordinate systems can be created using Bentley Map and can then be added.NAD27(76) / UTM zone 17N and click Add. Scroll to EPSG:2029 . • The Alias is the name that will be used to represent the coordinate system in the user interface. The icon preceding the row shows which is the reference coordinate system using a yellow datasource symbol. The Key Name is the unique identifier that represents the coordinate system in the re-projection engine. as required. 3 Note: Coordinate systems are listed in numerical order. the Key Name is automatically used as the alias. to the ProjectWise re-projection engine manually. Use means that when this coordinate system is found in a document. 4 Right click the coordinate system and select Set as Reference. The Type column shows where the coordinate system came from. Attributes Once added you will see the following attributes for each coordinate system. scroll to and select Projected defs from ESPG. The Scan Action is the action that is stored for the Spatial Location Scan tool. when this coordinate system is found in a document. area undetermined from the Coordinate Systems Groups options. The tool uses this action to streamline the scanning process. it will automatically be used.Working with Coordinate Systems  Exercise: Add a coordinate system 1 2 In ProjectWise Administrator. • • • Spatial Management Copyright © 2010 Bentley Systems. it will be presented to the user for approval.

Deleting coordinate systems Right click the CS and select Delete. Therefore. Jun-10 Copyright © 2010 Bentley Systems. Note: Note that the automatic use of a coordinate system only happens if there is only one coordinate system that matches for a document. Incorporated 305 Spatial Management . • Replace By is used when the Scan Action is set to Replace. Define symbology in the Default Symbology dialog. Defining Spatial Symbologies The appearance of spatial locations is determined by symbology such as color and weight you can define. they will all be listed so you can choose. It shows the name of the coordinate system that replaces the current one in the Spatial Location Scan tool. select Symbologies in the tree. All objects are re-projected using the reference coordinate system.  How to mark a coordinate system as the reference: Just right click a coordinate system and select Set as reference. If multiple coordinate systems match a document.Defining Spatial Symbologies Replace means that when this coordinate system is found in a document. Setting the reference coordinate system The reference coordinate system is used to compare objects that are in different coordinate systems. Coordinate systems that are used by at least one spatial location cannot be deleted. the reference coordinate system must be chosen carefully so that all other coordinate systems have a valid transformation path to it. it will automatically be replaced by the coordinate system specified in the Replace By column. and then right click on the Default Symbology icon and select Edit. To open it.

Once symbologies are defined. Tooltips and Texts Attributes determine the text that will display in the tooltip. a dialog opens for you to select a Windows icon. or subfolders. a dialog opens for you to select a ProjectWise icon. while a value of 100% is complete transparency in the selected color. and text. highlight color. set the Spatial view in ProjectWise Explorer to the desired view. • • • • Color opens the Color dialog where you select the outline color of the geometry used to represent a spatial location. This option is only available for the default document symbology and it is the same icon that is displayed in the document list. • Show application icon in tooltip displays the icons at the left of the tooltip text. Folders and SubFolders Symbology tabs are where you define the symbology used to display the spatial locations of documents. Fill Color opens the Color dialog where you select the color that fills the geometry used to represent a spatial location. folders. Options on the General Settings tab are used to control the display of tooltips. Hint: Use of some transparency is best so that information behind the areas can be seen. When Windows Icon is selected and you click Select Pins. Spatial Management Copyright © 2010 Bentley Systems. Select View > Symbology Legend to see the legend. 0% means no transparency at all. The Documents.Defining Spatial Symbologies The View Name field is where you type the name of the View that will display in the Symbology Legend in ProjectWise Explorer. Weight specifies the outline weight of the geometry used to represent a spatial location. • Points determines whether Windows or ProjectWise icons display.  Exercise: Set symbology transparency 1 Click Symbologies in the console tree and then right click Default Symbology and select Edit. Fill Color Transparency may vary from 0% to 100%. When ProjectWise Icon is selected and you click Select Pins. Incorporated 306 Jun-10 .

It should therefore be general enough to be used to represent all spatial locations stored in the datasource. Set Scale Range and Extent values properly so that only the necessary information displays when required. 3 4 Working with Background Maps Background maps are the backdrops that are displayed on the Spatial Pane in ProjectWise Explorer. Background maps should be simple enough that spatial locations are easily visible. It is also displayed in the search dialogs.Working with Background Maps 2 Use the scroll bar to access tabs for Document. Use this when the same background map is used all the time. Click OK when you are done. You should also avoid using many different layers with raster attachments as it decreases overall performance. Folder. This ensures that only necessary tiles of information are sent to the client. They are used as maps over which the document and folder spatial locations are drawn. and SubFolder symbology. The reference background map is displayed by default when no specific map is assigned to a folder. All users accessing this background map from ProjectWise Explorer or Spatial Web Part will be using pre-generated DPR file. saving the changes. Jun-10 Copyright © 2010 Bentley Systems. You can also select an icon to represent the symbology type. Static CAD Layers When creating Static CAD Layer. MicroStation is used to generate a DPR file during background map layer creation. Incorporated 307 Spatial Management . Select colors by clicking the tiles and make sure the Fill color transparency is set to a high value. Creation Proper creation of background maps results in better overall performance. Many background maps can be defined. but only one will be the reference background map.

Note: Avoid attaching a raster from Imaging Server with Raster Manager and then using the DGN file to create a background map as this results in poor performance. select Properties. and then select the Spatial tab to specify the address. It might take some time to download the DPR file. Dynamic layers tend to be slower that static layers. There is no DPR file pre-generated. This can be an existing DPR (Digital Print Spatial Management Copyright © 2010 Bentley Systems. To use dynamic CAD layers in background maps the Publishing Engine has to be installed and its address configured in the datasource spatial settings tab. right click on the datasource. the Choose a document for the layer dialog opens and you can navigate to its location. created using InterPlot. Incorporated 308 Jun-10 . as a source for a background map. and drop them. or after actual file. When you choose Add DPR Layer in the Edit Map Layer Settings dialog. drag the files and folders from the class data set \Spatial folder into it. To modify the Background Map Publishing Engine address. DPR Layers You can also choose an existing .Working with Background Maps When you choose Add Static CAD Layer in the Edit map layer settings dialog.dpr (Digital Print Room) file. When using the background map for spatial navigation the background map layer DPR file is downloaded to client system. Dynamic CAD layers are not downloaded to the client system. On first access. there is a DPR file generated and cached.  Exercise: Create a background map 1 In ProjectWise Explorer. The first step is to import the file containing the data or image you will be using as the background map. Use this when the background map may change. depending on the size. the Choose a document for a layer dialog opens and you can navigate to the location of the document you want to use. Dynamic CAD layers Use this option to select any file format that can be published by ProjectWise Publishing Server. but streamed instead. used as a source for the layer is modified. create a folder named Spatial.

A progress dialog indicates that a DPR layer is being created. You can modify this file in any text editor as necessary. In the Background Map Settings dialog. if you want to change how your maps are generated. Incorporated 309 Spatial Management . 5 Navigate to \Spatial\Peterborough. name the map Peterborough. a DGN file which MicroStation will publish to a DPR file. For this option to be enabled. MicroStation must be installed on the ProjectWise Administrator computer. In the Background Map Settings dialog.dgn. Use this option to select a design file from which a DPR file will be created and then published. all spatial locations drawn over it will automatically be reprojected into this coordinate system. you specify the coordinate system for the map. Jun-10 Copyright © 2010 Bentley Systems. select the coordinate system you added. and then click Save. select the folder where the map definition file will be stored in ProjectWise. Click OK.dgn. 2 3 4 In ProjectWise Administrator. 7 8 9 Continuing in the Background Map Settings dialog. Click Browse next to the Folder field and save the file to the \Spatial\dgn folder. The PLT file used in the generation of background maps is mapplot. 6 Click OK when done. located in the \Program Files\Bentley\ProjectWise\bin\v89 folder. the file is Peterborough. Click the arrow next to the URL field and select Add static CAD layer. When the background map is displayed in the Spatial Navigator. select it and click Open. Next. and then click Add Layer. Right click on the background map and select Set as Reference. All layers of the map must be projected in this system. In this case. The map set as the reference map has an addition to its icon. Note: It is strongly suggested that you use the reference coordinate system for the reference background map.Working with Background Maps Room) file. It is important that the coordinate system be set correctly. right click the Background Maps icon and select Create Background Map. or a file that ProjectWise Publishing Server will publish to a DPR file.plt.

in the DGN. GeoGraphics coordinate system information. Set both fields 0 if the layer should always be displayed. the bounding box will automatically be extracted from the file if possible. and can optionally obtain a coordinate system if there is a type 66 element. Layers are displayed in the order they are listed. It uses the DGN's total extent as spatial location. Layers can be modified using the Add. Note: The first layer must always be displayed and must be large enough to accommodate all the other layers. Spatial Management Copyright © 2010 Bentley Systems. Use the arrow buttons to change the order of the layers. Incorporated 310 Jun-10 . Scanning for Spatial Locations Metadata scanners are the engines that extract spatial information from documents. in the background map coordinate system. Use 0 to specify an unlimited range in one direction. The Scale range is used to determine the zoom ranges at which the layer should be displayed.Scanning for Spatial Locations Layers are all the documents that compose the map background and are displayed in the Spatial Navigator. They can extract spatial locations and coordinate systems. ProjectWise applications must be associated with the scanners so they know which files to scan. Remove and Edit buttons. When a new document is selected. The bounding box is used to determine when a layer is part of the current view in the Spatial Navigator. The MicroStation scanner uses MicroStation to scan DGN documents. The bounding box is the total extent of the layer in the background map’s coordinate system. The numbers represent a view width. Leave all fields set to 0 if you always want the layer to be displayed.

you can scan CAD files without problems. you must first remove it from the current scanner. Associating applications to metadata scanners ProjectWise applications must be associated with the scanners so they know which documents to scan. and can extract the coordinate system if there is one. For example. To change an application's association from one scanner to another. The ESRI scanner uses ESRI ArcObjects to scan ESRI file formats. The ESRI Scanner requires that ArcMap 8. It uses the file extent as spatial location. Note that AutoCAD is listed so that the MicroStation engine can process those files. Then. It uses the raster's clip shape as spatial location if there is one.Scanning for Spatial Locations The Raster scanner can open most raster file formats. A ProjectWise application can only be associated with one scanner. By default. Jun-10 Copyright © 2010 Bentley Systems. No validation is made as to which application is added to which scanner. right click the MicroStation scanner and select Properties.  How to associate an application with a scanner: First. it will not display in the Applications list. All software listed is not required in order for the tool to work correctly. those that do not have ESRI ArcMap installed will not be able to scan ESRI files. A coordinate system can be obtained if the raster contains GeoKeys like a geoTiff.  Exercise: Note the MicroStation scanners 1 Click Spatial Metadata Scanners in the console tree. The Scanner Properties dialog contains a list of currently associated applications. Each scanner requires that some software be installed in order for them to run. click Spatial Metadata Scanners. but if you have MicroStation installed. If an application is already associated with the scanner. for example. otherwise it will use the raster extent. making sure that the selected ProjectWise applications are associated with files that the scanner can process. right click a scanner and select Properties. Incorporated 311 Spatial Management . You can also add other applications. • • The MicroStation Scanner requires that MicroStation V8i be installed.x be installed if users wish to extract extent and coordinate system information from ESRI files. some applications that will be processed by the scanner are listed. click Add and select one or more applications to associate with the selected scanner. Please choose the applications carefully.

and then store this spatial information in the datasource and assign the information to the processed document. select Tools > Scan Spatial Locations. Select Tools > Scan Spatial Locations.Scanning for Spatial Locations 2 Click Cancel. • Extract Location Only only extracts the minimum bounding rectangle of the scanned file and use it. Spatial locations can also be batch assigned based on attribute values. Extract Location and Coordinate System extracts both the minimum bounding rectangle and the coordinate system from the scanned file. you must have Write and File Read privileges to the document in question. The Spatial Location Scanning dialog opens to guide you through the scanning process. the log file information clearly underlines the access and status constraints. Next. 2 Spatial Management Copyright © 2010 Bentley Systems. This registers the coordinate system and background map you added. select the folders you wish to scan and whether you want to scan sub-folders. Scanning using ProjectWise Explorer The Spatial Location Scanning tool is used to extract spatial information from the files associated to documents within a ProjectWise datasource. To launch the Spatial Location Import tool. Use Attribute Lookup Tables assigns a spatial location through the document's environment lookup table and attribute values. along with the coordinate system to create the scanned file's spatial location. Then. the status of the document must be checked in for the scanning process to work. • • Then. and then click Next. select the coordinate system that will be assigned to each file. select Tools > Scan Spatial Locations in ProjectWise Explorer. it will not be specified in the log file.  Exercise: Scan spatial locations 1 Exit ProjectWise Explorer and then re-launch it and log back in. Also. Incorporated 312 Jun-10 . identify a log file and start the scan. However. The Welcome Page briefly describes the tool.  How to scan for spatial locations in ProjectWise Explorer: First. In order to scan a file with the Spatial Location Scanning tool. If a document is ignored by the scanning process.

select your coordinate system. Click Next. turn ProjectWise Folders on. and then click Next. Click Next and check the check box preceding the folder you just added. to extract the geometries from a DGN file and store them in the SLF file. enable the Extract Location Only radio button. or by selecting the application in the (Utilities > MDL Applications) MDL dialog. If the geometries in the index file represent documents. the Spatial Location File Creation dialog opens. They are stored as in a spatial location file (SLF). Load the SLF Creation tool. 7 8 Click Start Scan. if they represent ProjectWise folders.  How to create an SLF file: Launch MicroStation and open the index DGN file that contains the geometries to capture. There are the Documents and ProjectWise Folders options in the Spatial Location File Creation dialog. which is an XML document. If the geometries contained in the index file represent documents. project locations. Enter a log file name and click Next. or zones of interest into a ProjectWise datasource. by typing MDL LOAD SLFCAPTURE in the Key-in browser.Scanning for Spatial Locations 3 4 5 6 Click the Add folders icon. Incorporated 313 Spatial Management . and then click OK. turn Documents on. Click OK in the Summary dialog and then click Exit. launched within MicroStation. Jun-10 Copyright © 2010 Bentley Systems. Once the SLF Creation tool is loaded. the Documents Search Options have to be set correctly. Browse if you want to place the file somewhere other than the root \Program Files\MicroStation folder. and select the MicroStation V8 application. The Spatial Location File Creation tool is an MDL application. Creating spatial location files The Spatial Location File Creation tool lets you import administrative boundaries. navigate to and select the \Spatial\dgn folder.

When launched. You can replace all spatial locations for all objects found. it will look in the target folder for an immediate child folder with the same name. the import tool will look in the target folder for a corresponding object. If the Spatial Location File object is a document. which will automatically assign spatial locations to corresponding ProjectWise documents or folders. Set logging options on the next page and then launch the process. the file names in the index file must exist in the directory specified in the ‘Search in’ field.  How to load spatial locations in ProjectWise Explorer: First. The Import Options page is used to specify the import mode. If the Spatial Location File object is a folder. the import tool will look for a document with the same name in the target folder. You can assign the spatial location to an object found in the target folder only if the object does not already have a spatial location. it only lists geometries. It will only look in the target folder. When reading the Spatial Location File and processing each of the Spatial Location File objects in the file. Incorporated 314 Jun-10 . Loading spatial location files Once the SLF is created in MicroStation. all valid geometries extracted from the index file are added to the SLF as ProjectWise folder geometries without further validation. whether these objects initially had a spatial location or not. The Spatial Location File does not provide any information about the coordinate system of the CAD file from which the Spatial Location File was generated. The Choose Spatial Location File page is used to select the Spatial Location File whose geometries will be created in ProjectWise. select the Target Folder. If the geometries contained in the index file represent folders. no options have to be set.Scanning for Spatial Locations To add these geometries. in ProjectWise Explorer. Spatial Management Copyright © 2010 Bentley Systems. Next. select Tools > Load SLF. which is the ProjectWise folder where the documents/folders whose geometries are listed in the Spatial Location File can be found. It will only consider direct child folders and ignore all other folders in the datasource. The Select the Coordinate System page is used to choose the coordinate system that will be assigned to all documents or folders contained in the selected Spatial Location File. Default file extensions can be specified in case the file names in the index file do not include file extensions. the geometries it contains can be loaded in ProjectWise using the Load SLF tool.

Next. Backon the List tab. set the Source to Custom. in the Geometry section.dgn and return to the Spatial tab. and a coordinate system. click BSI200-R01-Environmental. You can right click a previously defined spatial location in the Spatial Navigator and select Properties. 3 4 5 Drawing spatial locations Each spatial location is a pair composed of geometry. In the Editing toolbar. The outline of the map is highlighted in the symbology you selected.  How to draw a spatial location: First. The information in the preview pane updates to show information about the file. right click on the desired document or folder and select Properties.Using the Spatial Tab Using the Spatial Tab  Exercise: View the background map 1 2 In ProjectWise Explorer. navigate to the\Spatial\dgn folder and click on the Peterborough background map. Pop-up information shows the name of the file. You see the contents of the background. Click the Spatial tab. such as a polygon. Then. Click in the view window to start the polygon. click Edit. on the List tab. Click on a boundary. The coordinate system ensures data integrity and is used by the system to re-project a spatial location on a map that does not have the same coordinate system. select a geometry drawing tool. Move the pointer over one of the boundaries. and then click again to Jun-10 Copyright © 2010 Bentley Systems. click the Spatial tab in the properties dialog. In the Spatial Location section. Incorporated 315 Spatial Management .

In the Geometry section of the dialog click Edit. until the polygon is complete. reset. return to the List tab. Finally. right click BSI200-R01-Environmental. and then click Close. You see the location projected on the background map. and then click OK. Document Properties dialog spatial tab on the left ProjectWise Explorer spatial tab on the right  Exercise: Draw a spatial location 1 2 3 4 5 6 Continuing in ProjectWise Explorer. Spatial Management Copyright © 2010 Bentley Systems. Select the Spatial tab in the Properties dialog. Click Save. Incorporated 316 Jun-10 . and so on.dgn and select Properties. Select the Spatial tab. Click Save and then Close.Using the Spatial Tab define the next vertex. Use the tools to draw a location and click OK.

and the background map would represent the area of the entire project. the spatial location can be drawn using the Edit button. Set Source to Custom. or calculated (using the Calculate button). This regenerates the geometry based on the sum of the sub-folders and documents geometries (MBR) of this folder. Rectangles identify the DGN files against a background map  Exercise: Folder location 1 2 3 4 5 Continuing in ProjectWise Explorer. right click the \dgn folder and select Properties. files would most likely represent portions of an overall project. Select The Spatial tab. • Using Custom. This tab is the same as the Spatial tab in the document properties dialog. Note the coordinates at the bottom of the Geometry section. You can define the source that you want to search.Spatial Searches Realistically. Jun-10 Copyright © 2010 Bentley Systems. Click Calculate. You can select the background map you want to search. Incorporated 317 Spatial Management . It can also be extracted from a spatial location file (using the Load SLF button). and then use the tools to draw an area to find documents in that area. Spatial Searches You can search by spatial location using the Search by Form’s Spatial tab.

If a fence is defined and the toggle is still disabled. If there is no fence defined. click the Add Criteria button. click the Search icon in the ProjectWise File Open. enable Use MicroStation Fence to use the fence’s extent as the search area criterion. in the Define Search dialog. click the browse button (. Using source Linked. Note: If the Use MicroStation Fence option is always disabled when defining spatial search criteria. Incorporated 318 Jun-10 . or Open dialogs. Using source Use Parent Folder.. it is because either the active MicroStation document does not have a spatial location in ProjectWise. use the available editing tools to define the area to be used as the search criterion. adding a fence in MicroStation should fix the problem. How to search for documents using spatial criteria from inside MicroStation: First. select Spatial in the Criterion Type list and Spatial Location in the Property/Environment list. the spatial location uses the geometry and the coordinate system of the parent folder.. the spatial location is inherited from a source document or folder. If the active file is a ProjectWise document with a spatial location and a fence is defined. Once the area is defined. and click OK to launch the search operation.Spatial Searches If you set the source to Custom. Select Document.). Finally. click OK. or there is no fence defined in MicroStation. If no fence is defined. Next. Then. Searching by defining the area to search drawing on the selected map • • •  Using source None means no spatial location is associated to the document(s). a spatial location should be assigned to the document in ProjectWise to enable this feature. Spatial Management Copyright © 2010 Bentley Systems. you can search by coordinate system.

let’s measure what you have learned. Incorporated 319 Spatial Management . Questions 1 2 3 4 5 6 What is a spatial location? How can you add a coordinate system to the Add Coordinate Systems dialog? When does automatic use of a coordinate system happen? Why do you establish a reference coordinate system? Why is it important to set the coordinate system correctly in the Background Map Settings dialog? What document privileges must you have to scan a file with the Spatial Location Scanning tool? Jun-10 Copyright © 2010 Bentley Systems.Module Review Module Review Now that you have completed this module.

Module Review Spatial Management Copyright © 2010 Bentley Systems. Incorporated 320 Jun-10 .

ProjectWise Web Server Module Overview SharePoint is a platform for collaboration and the development of Web-based business applications with Windows SharePoint Services.0 on a Windows 2003 Server Install ProjectWise Web Server Deploy ProjectWise Web Server Configure web parts in SharePoint and non-SharePoint Sites Integrate with ProjectWise Publishing Server Configure Users’ Systems Use Design Compare Jun-10 321 Copyright © 2010 Bentley Systems. Module Prerequisites • • • • Knowledge about Windows Explorer Some knowledge about Windows Server Knowledge about MSDE or Microsoft SQL Server Knowledge about Windows SharePoint Services Module Objectives After completing this module. Incorporated ProjectWise Web Server . you will be able to: • • • • • • • Install Windows SharePoint Services 3. This module discusses implementing web parts and installing and deploying ProjectWise Web Server.

Note: Selecting the Basic Installation option will automatically install MSDE to your web server and install SharePoint. SharePoint Implementation When installing Windows SharePoint Services on a web server.Introductory Knowledge Introductory Knowledge Before you begin this module. ProjectWise Web Server Copyright © 2010 Bentley Systems.0? Answers 1 2 False. install the latest Windows updates. It is also recommended that you back up your web server before doing so. Users who want to use their existing Microsoft SQL Server installations should select the Advanced option. Questions 1 2 True or False: SharePoint can be used with an Oracle database? 2. Incorporated 322 Jun-10 . True. After accepting the license agreement. click Continue.Net and any Service Packs. let's define what you already know. Installing SharePoint services  Exercise: Install Windows SharePoint Services 1 2 1.exe executable provided by Microsoft to install Windows SharePoint Services (WSS) and click Run. Double click the SharePoint. specifically . True or False: SharePoint must be installed on Internet Information Services (ISS) 6.

0 on the server. 5 6 Click the Install Now button. The Windows SharePoint Services 3. Upon completion you will be prompted to run the SharePoint Products and Technologies Configuration Wizard. The SharePoint Products and Technologies Configuration wizard appears. 7 Leave this option checked and click Close.0 installer will load the setups file to your disk drive. 4 Click the Server Type tab and enable the Web Front End option. Incorporated 323 ProjectWise Web Server .SharePoint Implementation 3 Select the Advanced option. Jun-10 Copyright © 2010 Bentley Systems. Configuring SharePoint services  Exercise: The SharePoint Products and Technologies Configuration wizard 1 Click Next in the wizard to install Windows SharePoint Services 3.

To access the SQL database. 2 3 4 5 6 Click Yes to restart these services. Enter WSSDatabase as the name of the SQL database. 7 Accept the defaults by clicking Next. and click Next.0 wizard will implement SharePoint. SharePoint Administration Service. I want to create a new server farm” on the server farm page. and the SharePoint Timer Service. The next dialog lets you review the configuration settings of your Windows SharePoint Services installation. Enable “No. use the user name administrator and the password adminnt. ProjectWise Web Server Copyright © 2010 Bentley Systems. Using NTLM or Kerberos is also acceptable for the use of ProjectWise Web Parts or StartPoint. pwstartpoint. 8 Click Next. Incorporated 324 Jun-10 . and click Next. Name the SQL database server. Note: Administrators are responsible for choosing the proper security settings for their SharePoint installation.SharePoint Implementation You will be prompted to restart Internet Information Services. The Windows SharePoint Services 3. On this page you can specify the port number and the type of security.

Creating a web application  Exercise: Using the Central Administration page to create a web application 1 2 3 4 In the upper left corner. click the Application Management tab. Once you click Finish. Incorporated 325 ProjectWise Web Server . Enable “Create a new Web application”.0. Enable “Create new application pool”. type the following and click OK: iisreset Jun-10 Copyright © 2010 Bentley Systems.SharePoint Implementation 9 Click Finish once the configuration wizard has successfully installed Windows SharePoint Services 3. In the “Select a security account” section. In the SharePoint Web Application Management section. Enable “Use an existing IIS web site”. select Run. 5 6 Now you must manually reset IIS on this server. enable Predefined and select the Network Service option. select the “Create or extend Web application” option. 7 Click the Windows Start menu. Internet Explorer will publish the Central Administration page. type http://SQL/ into the address bar. If there are issues with this option.

click http://pwstartpoint/ sites/projectx and bookmark this page in your favorites. 8 Once IIS is restarted. select the Application Management tab and. in the 11 Use administrator for both User names to identify the Site Collection Administrators. 10 In the URL section. Also.0 Central Administration page found in Administrative Tools. Simple Mail Transfer Protocol must be installed on the server. click the Create Site Collection link. Incorporated 326 Jun-10 . ProjectWise Web Server Copyright © 2010 Bentley Systems. and then click OK. 12 Once the new top level site has been created. input field type projectx. expand the option list and select /sites/. then.  Exercise: Add users 1 Click Site Actions at the upper right of the team site and select the Site Settings option. Hint: If you accidentally dismissed Internet Explorer simply go to the 9 Enter the title Project X Team Site. in the SharePoint Site Management section. SharePoint 3. The SharePoint server must be on an active Domain in order to accomplish this. Then. Adding users Now that the new team site has been created you add Domain Users to the team site.SharePoint Implementation Note: If this server is a member of the server farm you must use iisreset / noforce. return to Internet Explorer and click “Create Site Collection” in the center of the page.

Incorporated 327 ProjectWise Web Server . Each web part provides a piece of ProjectWise functionality to the user. and they are connected to the datasource. which is the interface for ProjectWise Web Server and Web View Server. where using ProjectWise Explorer is not a practical option. you can type Bentley\Domain Users and click the Check Name icon. 3 4 Enable “Give users permissions directly” and the Contribute permission check box. You can also add specific Domain accounts to the team site.Installing ProjectWise Web Server 2 In the Users and Permissions column. possibly low-bandwidth locations. you can deploy either ProjectWise Web Server. the server you have deployed Jun-10 Copyright © 2010 Bentley Systems. or ProjectWise Web View Server. For example. and can be placed anywhere on the site. You can add a domain group. which allows normal access to the datasource. all a user needs to do is point their Internet Explorer browser to the website. select the People and Groups option. As the user works in ProjectWise Web Parts. Click the Home tab to return to the start page. you set up a website containing ProjectWise Web Parts. click New and Add Users. and is intended for casual users who may be in remote. which provides readonly access to the datasource. This will add the domain group Domain Users to your SharePoint site. ProjectWise Web Server and Web View Server is a single installation. Once you arrange the web parts and connect them to the datasource. Once deployed. and then click OK. Once installed. Installing ProjectWise Web Server ProjectWise Web Server and Web View Server is used to provide users with web access to ProjectWise.

What changes is the availability of some of the functionality in them. Note: If you intend to use ProjectWise Publishing Server with ProjectWise Web Server and Web View Server. Regardless of which server you deploy. no ProjectWise Passport usage is reported in SELECTserver for the Web Parts users who connect to that site. if you deploy ProjectWise Web Server. or create anything new in the datasource. for better performance consider installing ProjectWise ProjectWise Web Server Copyright © 2010 Bentley Systems. If you deploy ProjectWise Web View Server. however Note: You can deploy ProjectWise Web Server or ProjectWise Web View Server to any this is not supported by ProjectWise Web Server and Web View Server. Also.Installing ProjectWise Web Server (ProjectWise Web Server or ProjectWise Web View Server) handles the communication between the user and the ProjectWise Integration Server. Note: SharePoint lets you extend a web application to another IIS website. Incorporated 328 Jun-10 . when you deploy Web View Server and set up Web Parts. is turned off. ProjectWise Web Server and Web View Server supports: • • • • • • • • Installation on Windows Server 2003 (32-bit and 64-bit) Installation on Windows Server 2008 (64-bit only) Deployment to 32-bit SharePoint on 32-bit Windows Server 2003 Deployment to 64-bit SharePoint on 64-bit Windows Server 2003 and 2008 Deployment to 32-bit websites (non-SharePoint) on 32-bit Windows Server 2003 Deployment to 32. then the users who connect to that site will get basic ProjectWise functionality such as document check out / check in and document / folder create. For example. the ability to check out a document.and 64-bit websites (non-SharePoint) on 64-bit Windows Server 2003 and 2008 Parallel deployments to both SharePoint and non-SharePoint virtual servers on the same computer Parallel deployments of both ProjectWise Web Server and ProjectWise Web View Server to different virtual servers on the same computer available virtual server on the computer (SharePoint or non-SharePoint) as long as neither ProjectWise Web Server nor ProjectWise Web View Server is already deployed to it. the web parts that get delivered are the same.

Make sure Windows Installer 4. You can either install .5 SP1 installer for you. if necessary). make sure Internet Information Server (IIS) 6.0. If using Windows Server 2003. Note: If you need to install a ProjectWise language pack.50727 is installed.) • For Windows Server 2008 make sure the following Roles are installed: Windows Authentication.Installing ProjectWise Web Server Web Server and Web View Server on a different computer than ProjectWise Publishing Server. Before installing • • • Be an administrator of the computer.5 SP1 is installed (available from ProjectWise Server Setups.50727’s status is set to Allowed. or if an earlier version is installed. it is recommended that you do so after installation of ProjectWise Web Server and Web View Server.5 SP1 yourself prior to installing ProjectWise Web Server and Web View Server.0 or Microsoft Office SharePoint Server 2007 installed. Incorporated 329 ProjectWise Web Server . or a 64-bit Windows Server 2008 is installed.NET is not installed.NET Framework 3. or you can let the ProjectWise Web Server and Web View Server installer launch the .NET v2. Make sure . • If you plan to deploy ProjectWiseWeb Server orWeb View Server to a SharePoint virtual server. but before deployment of ProjectWise Web Server or ProjectWise Web View Server. under Web Service Extensions in IIS Manager. then the ProjectWise Web Server and Web View Server installer will prompt you to install .0 is installed. make sure Internet Information Server (IIS) 7.NET v2. Default Document.NET Framework 3. and Default IIS. After the Deployment Wizard is finished. or If using Windows Server 2008.NET.NET Framework 3.5 is installed (available from ProjectWise Server Setups. If the required version of ASP. the ProjectWise Web Server Deployment Wizard or ProjectWise Web View Server Deployment Wizard will install it for you. and that its status is set to Allowed. Or. ASP. a 64-bit Windows Server 2003.NET Framework 3. if necessary). make sure you have either Windows SharePoint Services 3.5 SP1.0.0 is installed. for Windows Server 2003 computers) Make sure that ASP. Make sure a 32-bit Windows Server 2003.NET Framework is installed. open IIS Manager and make sure ASP. (If no version of . • • Jun-10 Copyright © 2010 Bentley Systems.

From the ProjectWise Server Setups. 4. When installing on 64-bit Windows Server 2003 or 2008. and you are working on a computer from which SharePoint has been uninstalled.Installing ProjectWise Web Server • If you plan to deploy ProjectWiseWeb Server or ProjectWiseWeb View Server to a non-SharePoint virtual server. which in turn ensures that the licensing information you enter through the Product Activation Wizard gets registered to the correct location in the Windows Registry. When installing on 32-bit Windows Server 2003. accept the agreement and clickNext. ProjectWise Web Server Copyright © 2010 Bentley Systems. • •  3. When the installer opens. the default installation location is “C:\Program Files (x86)\Bentley\ProjectWise”. accept the default installation location and click Next. 2. you must launch the ProjectWise Web Server and Web View Server installer using the Run as Administrator option.microsoft. depending on the version of RDC you are using. click Next. as uninstalling SharePoint will affect your IIS permissions. Incorporated 330 Jun-10 . When the Destination Folder page opens. or click the Change button to change the installation location. This ensures that the Produc‘t Activation Wizard is also run as an administrator. make sure that correct IIS permissions are set as described in http://support. If you plan to use the Remote Desktop Connection (RDC) client to install ProjectWise Web Server and Web View Server on a remote Windows Server 2003 computer. select ProjectWise Web Server and Web View Server and click Install. (Windows Server 2008 computers only) If you plan to run the Product Activation Wizard at the end of your installation. the default installation location is “C:\Program Files\Bentley\ProjectWise”. then click Next. How to install ProjectWise Web Server and Web View Server: 1.com/kb/812614/en-us. make sure you start the RDC client (mstsc.exe) with the / console or /admin switch. When the License Agreement page opens.

If the Deployment Wizard you want to run is not already open. 4. 3. select Deploy ProjectWise Web Server and click Next. go to the Windows Start menu and select Programs > Bentley > ProjectWise V8i (SELECTseries 1) > Web Server and Web View Server > ProjectWise Web Server Deployment Wizard or ProjectWise Web View Server Deployment Wizard. and whether or not ProjectWise Web Server or ProjectWise Web View Server is currently deployed to any of them. select Deploy ProjectWise Web View Server and click Next. then click Finish. 6. The Product Activation Wizard opens for you to configure licensing for this module. displaying the virtual servers currently available in IIS. When the Ready to Install page opens. At the same time. On the Virtual Server Selection page.Installing ProjectWise Web Server 5. or If you launched the ProjectWise Web View Server Deployment Wizard. When the Deployment Wizard opens. either the ProjectWise Web Server or ProjectWise Web ViewServer Deployment Wizard opens. 2. Select the virtual servers you want to upgrade. select one or more virtual servers to deploy ProjectWise Web Server or ProjectWise Web View Server to. When installation is complete. select which Deployment Wizard you want to run after that.) Jun-10 Copyright © 2010 Bentley Systems. click Install.  How to To deploy ProjectWise Web Server or ProjectWise Web View Server: 1. Incorporated 331 ProjectWise Web Server . 5. If the Site Update Required page opens. then click Next. (ProjectWise Web Server or ProjectWise Web View Server will not be deployed to any virtual servers listed that you do not select. If you launched the ProjectWise Web Server Deployment Wizard. then click Next. click Next. The Deployment Type page opens. depending on your selection. this means that one or more of the virtual servers you selected to deploy to does not meet the minimum requirements of ProjectWise Web Server or ProjectWise Web View Server.

I will do it manually. If during deployment you selected to update one or more of the virtual servers to use ASP. a text file opens when you click Finish. click Finish. This text file contains the custom trust policy information you need to add to your existing trust policy. click Start. Incorporated 332 Jun-10 . then click Next.0. see your SharePoint documentation. under Web Server Extensions. When the Custom Trust Policy page opens.Installing ProjectWise Web Server 6. This text file contains the custom trust policy information for you to manually add to your existing trust policy.50727’s status is set to Allowed. 10.0. then click Next. a text file opens when you click Finish in the Deployment Wizard. For more information. If in step 6 you selected to manually configure the trust policy. 7.NET v2. When finished. When the Select working directory page opens. you need to specify a temporary working directory for each virtual server to which you are deploying ProjectWise Web Server or ProjectWise Web View Server. Hint: If you ever need to rerun one of the deployment wizards go to the Windows Start menu and select Programs > Bentley > ProjectWise V8i (SELECTseries 1) > Web Server and Web View Server > ProjectWise Web Server Deployment Wizard or ProjectWise Web View Server Deployment Wizard. 9. ProjectWise Web Server Copyright © 2010 Bentley Systems. If you select this option. When deployment is complete. select Automatically configure trust level (recommended).50727. 8. then you should now open IIS Manager and make sure ASP.NET v2. or Select Do no configure trust policy .

however. which lets the administrator preset the user’s working directory when using ProjectWise Web Parts. or ProjectWise Web View Server.) Working directory . the user will be able to log in to ProjectWise whether using ProjectWise Explorer. then you should turn on the user setting (in ProjectWise Administrator) called General . The default Web Parts working directory for every user is set to: %LocalAppData%\Bentley\ProjectWise Web Parts\Working Directories\%Datasource%\%User% To change the default Web Parts working directory for any user. changing the location of the working directory from Web Parts does not change the value set for this user setting.Configuring User Settings for Web Parts Users Configuring User Settings for Web Parts Users General .When accessing ProjectWise over the web There is a user setting in ProjectWise Administrator called Working directory -> When accessing ProjectWise over the web. If it cannot be created (because no value is defined in the setting here. then the user will be prompted to select their working directory. (When this user setting is off. using Web Parts. The user can always change the location of their working directory by selecting Tools > Working Directory from the Content web part. The benefit of using ProjectWise Web View Server is that ProjectWise Passport usage is not reported in SELECT Server when a user logs in to ProjectWise. Incorporated 333 ProjectWise Web Server . the working directory on the new computer will be created based on the value set for the user setting in ProjectWise Administrator. if you have deployed ProjectWise Web View Server. Therefore. or maybe the path is invalid path. Jun-10 Copyright © 2010 Bentley Systems. and you have users who will only be using ProjectWise Web View Server. The working directory will be created automatically on a ProjectWise Web Parts user’s computer on their first log in to the datasource through ProjectWise Web Parts.User can only log in through Web View Server.Users can only log in through Web View Server ProjectWise Web View Server is intended for casual Web Parts users who only need read-only access to ProjectWise. ProjectWise Web Server. or for some other reason). select the default location displayed. If the users uses Web Parts from another computer. through a ProjectWise Web View Server. expand the ProjectWise Web Parts working directory setting. then select it again and wait for it to become editable.

a new window will open to display the search results. all users have to do is point their Internet Explorer browser to the SharePoint team site and they will be automatically logged in to the datasource using whichever log in method you have specified all web parts users to use. ProjectWise Search New searches are configured and run from the Search web part. After you add the web parts.Configuring Web Parts in a SharePoint Site Configuring Web Parts in a SharePoint Site Once ProjectWise Web Server or Web View Server has been deployed to a SharePoint virtual server. custom folders. Once connected. Note: After adding the Content web part and connecting it to the datasource. you will be prompted to install the ProjectWise Web File Transfer ActiveX Control. the contents display in the Content web part. It shows documents at the root of the folder or project selected in the Navigation web part. or documents selected from the Content web part. projects. ProjectWise Content The ProjectWise Content web part is where users access ProjectWise documents. Incorporated 334 Jun-10 . you need to connect them to a ProjectWise datasource. you will not be prompted about this again. you can add ProjectWise web parts to the SharePoint team site. which is required for file-based operations. and the results of the search are displayed in the Content web part. ProjectWise Web Server Copyright © 2010 Bentley Systems. ProjectWise Properties Users use the ProjectWise Properties web part to view or modify the properties of folders. projects. Once installed. The following ProjectWise web parts are available: ProjectWise Navigation This web part lets users browse folders. as well as search results. If the Content web part is not present. The Navigation web part is typically used in conjunction with the Content web part because when you navigate to and select things in the Navigation web part. and saved searches.

you can add it to the page and use it independently without adding any other ProjectWise web parts. they are not yet connected to a datasource.  How to add ProjectWise web parts to the SharePoint site: Go to the SharePoint team site. Modify the user setting from either ProjectWise Explorer or ProjectWise Administrator. If you only need to use the Content web part. When you add the web parts. and then click Add. select Site Actions > Edit Page. If you only need to use the Search web part. ProjectWise Publishing and Markup This web part lets users view and redline DGN and DWG documents accessed from the Content web part. Incorporated 335 ProjectWise Web Server . If you are doing this. This lets you see projects and folders in the Content web part without requiring the Navigation web part on the page. Add parts to the other zone if desired. Jun-10 Copyright © 2010 Bentley Systems.Configuring Web Parts in a SharePoint Site Existing saved searches created and saved in ProjectWise Explorer are run from the Navigation web part. Select the ProjectWise web parts you want to add to the selected zone. ProjectWise Spatial Content This web part is used to display ProjectWise documents and folders against a background map. and require the Content web part to display the results. you can add it and use it independently also. The next step is to connect them. you can add it to the page and use it independently without adding any other ProjectWise web parts to the page. and then click Add a Web Part in the Left or Right zone. make sure the user setting Document list-> Show subfolders is on before adding the Content web part and connecting to a datasource. Standalone web parts If you only need to use the Navigation web part.

In the Select web parts to connect section. check all the ProjectWise web parts listed. if there are any. they are not yet connected to a datasource. check out. Usability enhancements for users Web parts have been enhanced to let users do the following.  How to connect web parts to a datasource on a SharePoint site using one account: Add the web parts you want to the site. and open documents Open documents as readonly Move and delete documents export and free documents View thumbnail images of documents Display set contents Compare the graphical differences of two DGN documents Create various types of links to documents Purge local copies of documents from the working directory Create. The next step is to connect them. show component properties.Configuring Web Parts in a SharePoint Site Whenever you run a search and the Content web part is not present. In any web part. • • • • • • • • • • • • Create. Incorporated 336 Jun-10 . From the Location ProjectWise Web Server Copyright © 2010 Bentley Systems. select Edit > Modify Shared Web Part. a new window opens to display the results of the search. modify. Connecting web parts to a datasource using one account This method uses one ProjectWise account for all connecting users. A settings window for that web part opens on the right side of the screen. and delete folders View the component tree. and zoom in to components View spatial data in the new Spatial web part Connecting web parts to a datasource When you add the web parts.

on the ProjectWise Integration Server system. you must add the ProjectWise Web Server's IP address to the [Trusted Servers] section in the Integration Server's dmskrnl. disable the Use Windows Credentials (SSO) check box. which is required for file-based operations. You. the administrator. you will be prompted to install the ProjectWise Web File Transfer ActiveX Control. When another user points their browser to this SharePoint site.\ProjectWise\bin folder.cfg file from the . then save and close the file. you will not be prompted about this again. add a line that includes the IP address of the system on which ProjectWise Web Server is installed. Note: After adding the Content web part and connecting it to the datasource..cfg file. select the ProjectWise datasource to which you want to connect.Configuring Web Parts in a SharePoint Site list. are now logged in to the datasource with the selected account. enter a ProjectWise user name and password and click OK. Connecting web parts to a datasource using single sign on Using this method. Once installed. open the dmskrnl. Finally. Incorporated 337 ProjectWise Web Server . Then. The account you use here can be a logical account or a Windows domain account. In SharePoint.. you do not add the web parts first. For example: Jun-10 Copyright © 2010 Bentley Systems. below [Trusted Servers]. click Exit Edit Mode. To connect web parts to a datasource using single sign on on a SharePoint site.  How to connect web parts to a datasource on a SharePoint site using single sign on: First. they will be automatically logged in to the datasource with that same account.

In SharePoint. Finally. check all the ProjectWise web parts listed.Configuring Web Parts in a SharePoint Site [Trusted Servers] ProjectWise Web Server = 44. Incorporated 338 Jun-10 . After that. A settings window for that web part opens on the right side of the screen. log in to the SharePoint site with a Windows domain account that has administrative rights to that site. Now add the web parts to the page. click Save Settings. on the Web Server system. in ProjectWise Administrator. enable Use Windows Credentials (SSO) and click OK. From the Location list. go to Start > Programs > Bentley > ProjectWise V8i > Web Server and Web View Server > ProjectWise Web Server Single SignOn Settings.66. add your Windows domain users. Make sure this domain account exists in the ProjectWise datasource to which you plan to connect the web parts.77 Hint: If you have installed ProjectWise Web Server on more than one system.cfg file to include a range of IP addresses on this line. make sure the Windows domain users you added to ProjectWise Administrator are added to the SharePoint site. they will be automatically logged in to the ProjectWise Web Server Copyright © 2010 Bentley Systems.55. enter the user name and password for the delegate user account. When another user points their browser to this SharePoint site. in any ProjectWise web part. you can use subnet masking as described in the dmskrnl. Then. In the Select web parts to connect section. Still on the Web Server system. and then click Close. Select your datasource. select Edit > Modify Shared Web Part. Next. You are now logged in to the datasource with the same Windows domain account you used to log in to SharePoint. and then create a logical user account enabling their user setting Administrative-> Enable as delegate user. select the ProjectWise datasource to which you want to connect.

In the Security Settings dialog.aspx to set up a web page to test your configuration. If you want users to have the ability to add web parts.Configuring Web Parts in a Non-SharePoint Site datasource with their Windows domain account. and then OK. scroll to the Security section and enable “Enabled Integrated Windows Authentication (requires restart)”. click Custom Level. you can add ProjectWise web parts to a web page. and then add your Windows domain groups or Windows domain users. You should set most users’ permissions to Team Site Visitors [Read]. This permission does not mean that the contents of the ProjectWise web parts are read-only. click Apply. scroll to the User Authentication section and enable “Automatic logon with current username and password”. click New > Add Users. In SharePoint. When you are finished. default. In the Internet Options dialog’s (Tools > Internet Options) Security tab.  How to add Windows domain users to a SharePoint site: First. but they cannot change anything on the site. Incorporated 339 ProjectWise Web Server . Once connected. You do need to make sure the users who plan to access web parts have the following Internet Options configured in their Internet Explorer browser. Configuring Web Parts in a Non-SharePoint Site Once ProjectWise Web Server or Web View Server has been deployed to a nonSharePoint virtual server. You can use the delivered default ASP page. On the Advanced tab. click Exit Edit Mode. Team Site Members can also log in to the datasource as a different user. you can set their permissions to Team Site Members [Contribute]. all users do is point their Internet Explorer browser to this web site and they will be automatically logged in to the datasource using their own Jun-10 Copyright © 2010 Bentley Systems. It means that users can access the SharePoint site. in SharePoint go to Site Actions > Site Settings > Users and Permissions > People and groups. Internet Explorer options This completes single sign on configuration for web parts.

and paste it in \Inetpub\wwwroot\ if you are using the IIS Manager Default Web Site. on the ProjectWise Integration Server system. add a line that includes the IP address of the system on which ProjectWise Web Server is installed. On the Directory Security tab.  How to connect web parts to a datasource on a non-SharePoint site using one account: Launch Internet Explorer and connect to the ProjectWise Web Server.. When the sample page opens. Incorporated 340 Jun-10 .Configuring Web Parts in a Non-SharePoint Site Windows domain account if you have connected web parts using single sign on. Finally.  How to set up the default web site: After installing and deploying ProjectWise Web Server or Web View Server to a non-SharePoint virtual server. For example: ProjectWise Web Server Copyright © 2010 Bentley Systems.aspx. where webserver is the name of the system on which ProjectWise Web Server is installed. and then select the ProjectWise datasource to which you want to connect. by typing http://webserver:portnumber/default.cfg file from the .\ProjectWise\bin folder. open the dmskrnl. you can type http://localhost/default. This account can be a logical account or a Windows domain account. If you are testing this from the same system on which ProjectWise Web Server is installed. then save and close the file. Select all ProjectWise web parts to connect to this datasource. Then. click the Login/Logout link in the upper right corner of the page.aspx. Connecting web parts to a datasource using single sign on  How to connect web parts to a datasource on a non-SharePoint site using single sign on: First. In the Authentication Methods dialog. Right click Default Web Site and select Properties.. Then. navigate to the \Program Files\Bentley\ProjectWise\Web\Samples directory. disable “Enable anonymous access” and enable “Integrated Windows authentication”. or using the ProjectWise account you have specified all web parts users to use. Click OK to exit. and portnumber is the port that the default web site is using. update your default site security settings by selecting Start > Administrative Tools > Internet Information Services (IIS) Manager > Web Sites. click Edit in the Authentication and access control section.aspx. copy default. below [Trusted Servers]. enter a ProjectWise user name and password and click OK. disable Use Windows Credentials (SSO).

Configuring Web Parts in a Non-SharePoint Site

[Trusted Servers] ProjectWise Web Server = 44.55.66.77
Hint: If you have installed ProjectWise Web Server on more than one system,

you can use subnet masking as described in the dmskrnl.cfg file to include a range of IP addresses on this line. Next, in ProjectWise Administrator, add your Windows domain users, and then create a logical user account enabling their user setting Administrative-> Enable as delegate user. Then, on the Web Server system, go to Start > Programs > Bentley > ProjectWise V8i > Web Server and Web View Server > ProjectWise Web Server Single SignOn Settings. Select your datasource, enter the user name and password for the delegate user account, click Save Settings, and then click Close. Still on the Web Server system, make sure you are logged in to the system with a Windows domain account. Make sure this domain account also exists in the ProjectWise datasource to which you plan to connect the web parts. Launch Internet Explorer and connect to the ProjectWise Web Server by typing http://webserver:portnumber/default.aspx where webserver is the name of the system on which ProjectWise Web Server is installed, and portnumber is the port that the default web site is using. If you are testing this from the same system on which ProjectWise Web Server is installed, you can type http://localhost/default.aspx. When the sample page opens, click the Login/Logout link in the upper right corner of the page. Select all ProjectWise web parts to connect to this datasource, and then select the ProjectWise datasource to which you want to connect. Finally, enable Use Windows Credentials (SSO) and click OK. You are now logged in to the datasource with the same Windows domain account you used to log in to the system. When a user points their browser to this web site, they will be automatically logged in to the datasource with their Windows domain account.

Internet Explorer options
You need to make sure the users who plan to access web parts have the following Internet Options configured in their Internet Explorer browser. On the Internet Options dialog’s (Tools > Internet Options) Security tab, click Custom Level. In the Security Settings dialog, scroll to the User Authentication section and enable “Automatic logon with current username and password”. On the Advanced tab, scroll to the Security section and enable “Enabled Integrated

Jun-10

Copyright © 2010 Bentley Systems, Incorporated

341

ProjectWise Web Server

Integrating with ProjectWise Publishing Server

Windows Authentication (requires restart)”. When you are finished, click Apply, and then OK.

Integrating with ProjectWise Publishing Server
To view and redline DGN and DWG documents in the Publishing and Redlining web part, you must integrate your ProjectWise Web Server with ProjectWise Publishing Server.

Performance and port configuration
ProjectWise Publishing Gateway Service and ProjectWise Publishing Server must be installed on the same system. For better performance, consider installing them on a different system than SharePoint and ProjectWise Web Server. If for testing purposes you have installed ProjectWise Publishing Server on the same system as SharePoint, ProjectWise Publishing Server will not be able to use port 8081 as it will already be occupied. If this is the case, change the ProjectWise Publishing Server request port from 8081 to 8087 on the General Settings page of the Administration Server (Programs > Bentley > ProjectWise Publishing Server > ProjectWise Publishing Server Administration). Make sure you also specify the server and request port accordingly in the datasource settings in ProjectWise Administrator. After changing the port, on the ProjectWise Publishing Server open a command prompt and type iisreset. ProjectWise Publishing Server always runs on IIS's Default Web Site, whose default port is 80. If the Default Web Site port has been changed, then when specifying the location of your ProjectWise Publishing Server, you will also need to specify the port after the server name, for example, http:// publishingserver:88.

Procedure
Following are the steps for integrating ProjectWise Publishing Server. 1. Install ProjectWise Publishing Server.

ProjectWise Web Server

Copyright © 2010 Bentley Systems, Incorporated

342

Jun-10

Integrating with ProjectWise Publishing Server

2. Perform the steps in the ProjectWise Publishing Server readme regarding additional Windows 2003 Server configuration necessary for ProjectWise Publishing Server. You can also find these steps in ProjectWise Administrator’s online Help file under ProjectWise Implementation > Web Server and Web View Server Configuration > Integrating with ProjectWise Publishing Server.

3. Configure integrated ProjectWise Publishing Server to run in secure or regular mode.

How to configure integrated ProjectWise Publishing Server to run in secure or regular mode: Go to Start Programs > Bentley > ProjectWise Publishing Server > ProjectWise Publishing Server Administration. On the left side of the ProjectWise Publishing Server Administration window, click General Settings. On the right, turn “Run as Web Server Extension” on to run in secure mode or off to run in regular mode. At the bottom of the page, click Submit. On the left side of the window, click Server Control and enable “Automatically configure Microsoft IIS when pressing START or RESTART”. Click Restart. In ProjectWise Administrator, right click your datasource and select Properties. On the Settings tab, expand Web Components > Default ProjectWise Publishing Server and double click the icon below it. - For secure mode, in the Specify server address dialog, enable “Server uses secure protocol”, then enter the name of your ProjectWise Publishing Server system exactly as it appears in your certificate. To find this name, open Internet Information Services, go to Web Sites > Default Web Site > Properties > Directory Security tab > View Certificate > Issued to. -For regular mode, in the Specify server address dialog, enter the name of the system on which ProjectWise Publishing Server is installed.

4. Make ProjectWise Publishing Server as the web viewer for all the applications in the datasource associated with DWG and DGN documents.

Jun-10

Copyright © 2010 Bentley Systems, Incorporated

343

ProjectWise Web Server

Configuring Users' Systems

How to make ProjectWise Publishing Server the web viewer for DGN and DWG documents: In ProjectWise Administrator, click the Applications icon, select an application you have associated to DGN or DWG documents and select Properties. On the Web viewing tab, set the Associated web viewer to ProjectWise Publishing Server, click Apply and then click OK. Do this for all other applications that are associated to DGN or DWG documents.

5. Install ProjectWise Publishing Gateway Service on the same system as the ProjectWise Publishing Server.

How to install ProjectWise Publishing Gateway Service: First, make sure ProjectWise Publishing Server is installed, and that the ProjectWise Publishing Server service is running. Then, from the ProjectWise Server Setups, select ProjectWise Publishing Gateway Service and click Install.

Click Next in the installer, accept the license agreement, click Next and then click Install. Click Finish when the installer is done.

Configuring Users' Systems
If any of your web parts users do not have administrator permissions on their system, they will not be able to install the necessary ActiveX controls as prompted the first time they visit the web parts site.

ProjectWise Web Server

Copyright © 2010 Bentley Systems, Incorporated

344

Jun-10

Configuring Users' Systems

You will need to copy the RegisterDLLs.bat file and all the .cab files from the \Program Files\Bentley\ProjectWise\Web\Resources\Installs directory on the system on which ProjectWise Web Server is installed to those user’s systems. Once copied, launch the RegisterDLLs.bat file remotely. This will copy and register the ActiveX DLL’s, allowing the users to use the web parts. Also, their Internet Explorer browsers should be configured accordingly. This means they need to do the following: • Add the web parts web site address and the about:blank web site to their browser's Trusted sites list on the Security tab of the Internet Options dialog.

Turn off the popup blocker, since web parts sometimes needs to open items in a new window. For example, if a user right clicks a folder and select Properties when the Properties web part is not present, the properties of the selected folder display in a new window.

Configure Internet Explorer security settings.

Active X
For ActiveX controls to work properly in Internet Explorer, on the Internet Options dialog’s Security tab, select Trusted sites, click Custom Level, and then make sure the following are set in the Security Settings dialog:

Jun-10

Copyright © 2010 Bentley Systems, Incorporated

345

ProjectWise Web Server

Design Compare

ActiveX controls and plug-ins: Download signed ActiveX controls = Prompt Download unsigned ActiveX controls = Disable Initialize and script ActiveX controls not marked as safe for scripting = Disable Run ActiveX controls and plug-ins = Enable Script ActiveX controls marked safe for scripting = Enable Scripting: Active Scripting = Enable Allow paste operations via script = Enable Scripting of Java applets = Enable

Windows 2003 Server
For downloading to work properly when using Internet Explorer on Windows 2003 Server, and then make sure the following are set in the Security Settings dialog. Downloads: Automatic prompting for file downloads = Enable

Windows Vista
For copy outs to function properly when using Internet Explorer on Windows Vista, on the Internet Options dialog’s Security tab, disable “Enable Protected Mode”.

Design Compare
This utility lets users select two documents produced from MicroStation sources in the Content web part and see changed, unchanged, added, or deleted graphics that are different between them in the Publishing and Redlining web part. Design compare detects changes in an element. A user must modify the element by moving it, adding vertices, scaling or rotating it, or changing its color, weight, style, or fill. The feature is not designed to detect changes in appearance that are

ProjectWise Web Server

Copyright © 2010 Bentley Systems, Incorporated

346

Jun-10

Module Review

caused by level symbology overrides, view attribute changes, or shifts in color tables. To run it, you must install and set up the ProjectWise Design Compare Utility that is delivered with ProjectWise InterPlot Server. You can use the utility on a SharePoint site on non-SharePoint site. Find directions for set up in the online Help file under ProjectWise Implementation > Web Server and Web View Server Configuration > Configuring Design Compare.

Module Review
Now that you have completed this module, let’s measure what you have learned.

Questions
1 2 3 4 5

What operating system is required for Web Parts deployment? True or False: Windows SharePoint Services works with Oracle. What option must you select to install Windows SharePoint Services 3.0 on an existing SQL Server implementation? True or False: ProjectWise Web Server and ProjectWise Web View Server can both be deployed on the same system. True or False: You can use the Navigation, Content, and Search web part, you can add it to the page and use it independently without adding any other ProjectWise web parts independently.

Jun-10

Copyright © 2010 Bentley Systems, Incorporated

347

ProjectWise Web Server

Module Review

ProjectWise Web Server

Copyright © 2010 Bentley Systems, Incorporated

348

Jun-10

Module Prerequisites • Knowledge about the ProjectWise Explorer and ProjectWise Administrator interfaces Module Objectives After completing this module. you will be able to: • • Use the DFT benchmark tool Handle ProjectWise Explorer related issues ProjectWise Administrator Specific Datasource names Datasource names only support characters that are valid for Windows directory names.ProjectWise Maintenance Module Overview There are best practices that will make ProjectWise administration easier and help your users work most effectively. Incorporated ProjectWise Maintenance . Jun-10 349 Copyright © 2010 Bentley Systems.

The application can be run in two modes. click the Settings tab. medium. and large) in your workstation's temporary directory. If you are running this test against an existing. make a predefined set of changes to the file data. you must first activate the Delta File Transfer datasource setting. This is so that you can gauge the performance of the DFT technology based on set of changes over which you have personal control.  How to activate the Delta File Transfer datasource setting: First. in ProjectWise Administrator. A Windows wizard-style window will display. check them out. log in to the datasource you will be using for the benchmark. termed Delta File Transfer (DFT). a benchmark tool has been provided with the ProjectWise Administrator installer that will allow the end-user to perform various file transfer tests to determine how much of a benefit DFT will provide. upgraded datasource. Incorporated 350 Jun-10 . and check the modified files back in.. and will guide you through the process of running the application. The application will then report the efficiency of the DFT operation. The application will import these documents into a test folder in your datasource. and will use those files to gauge the performance of the DFT technology. This technology.\Program Files\Bentley\ProjectWise\bin" directory Then. DFT is on by default.ProjectWise Administrator Specific DFT benchmark tool ProjectWise V8i has file transfer technology that can significantly reduce the amount of time required to check out and check in ProjectWise documents. Right click the datasource and select Properties.. The before and after copies of the file or files should be • ProjectWise Maintenance Copyright © 2010 Bentley Systems. optimizes file transfers by only transferring those parts of a file that have been modified. Because the performance of this feature is greatly dependent on an organization's network infrastructure. scripted changes. based on the predefined. Two copies of each file must be provided: a baseline copy of the file. run the DFTBMWIZ.  How to run the Delta File Transfer Benchmark tool: First. in Windows Explorer or in a command window. auto or manual. The manual test requires that you provide a set of files for the test. Expand the Network category and make sure the Enable Delta File Transfer option is on. and a copy that contains a known set of changes. navigate to the ". In the Datasource Properties dialog. If you are running this test against a new datasource created using the ProjectWise V8i Administrator.EXE application. • The auto test will generate 3 files (small.

This is a known shortcoming of any kind of differential file transfer algorithm. Incorporated 351 ProjectWise Maintenance . There is also an option to submit your results to Bentley for analysis. To ensure that text is correctly imported. various reports can be viewed to show the file transfer performance increase.1 ProjectWise datasource to ProjectWise V8i. Note: DFT technology is designed to provide better file transfer performance over low-bandwidth/high-latency network links. Note: No personally identifiable information. ProjectWise Explorer Specific Importing export files from earlier versions The Import Wizard in ProjectWise V8i can import export files from earlier versions of ProjectWise. After the test completes. After the test completes you have the option of saving the results for later review. Scan for References after converting a pre-8. or information about your organization's internal infrastructure is transmitted to Bentley. You will be given a change to review the full and complete text of the e-mail before it is submitted to Bentley. other than your e-mail address. Jun-10 Copyright © 2010 Bentley Systems.ProjectWise Explorer Specific placed in separate directories. and you will be given an opportunity to decline to send the e-mail. This is to allow for the population of additional data into the ProjectWise database about reference file relationships for both MicroStation and AutoCAD and ensures the correct operation of reference data.1 datasource Scan for References must be run after converting a pre-8. make sure that the default code page (character set/locale) on the import system matches the default code page on the export system. It is possible that negative performance results may occur when using DFT over high-speed LAN links.

ProjectWise Explorer Specific Vista users disable protected mode in IE For ProjectWise links to function correctly when using Windows Vista. ProjectWise Maintenance Copyright © 2010 Bentley Systems. in Internet Explorer select Tools > Internet Options. select the Security tab and turn off the setting Enable Protected Mode. Incorporated 352 Jun-10 .

Answers 1 2 3 A document that has no file associated to it. When the Extraction enabled option is off. 4 5 Jun-10 353 Copyright © 2010 Bentley Systems. no scheduled extractions will occur. and no manual extractions can start. Document ID’s are said to be globally unique. no scheduled extractions will occur. Every document is assigned an identification number within ProjectWise. True. and no manual extractions can start. These tabs are the user’s means of accessing extended document metadata. Why? What is a GUID? What are the Attributes and More Attributes tabs in the document properties dialog? True or False: When the Extraction enabled option is off in the File Property Extraction Properties dialog. Incorporated Module Review Answers . and are thus often referred to as GUID’s. Any existing metadata would be lost.Module Review Answers Document Architecture Questions 1 2 3 4 5 What is an abstract document? It is not a good idea to delete an existing abstract document and import a new one.

Module Review Answers Copyright © 2010 Bentley Systems. True. what is an action association? 2 3 4 5 6 Answers 1 2 3 4 5 6 The request is on port 5799. Action associations determine what program launches when a user tries to open. what do users see when they log in to ProjectWise Explorer? True or False: If two servers use the same display name. or print a document associated to an application. view. What is the purpose of the ProjectWise V8i Network Configuration Settings dialog? True or False: If two users are sharing a client system. True. It is used to configure the networking aspects of the ProjectWise Explorer client application. The datasource list is returned to the client in the format ServerName:DatasourceName. they should not share working directories. users see the name twice in their datasource list and won’t be able to tell them apart. it attempts to discover any ProjectWise Servers on the network by sending out a broadcast on the network.ProjectWise Explorer Best Practices ProjectWise Explorer Best Practices Questions 1 When ProjectWise Explorer launches. What port is used? If you fail to specify a display name when creating a datasource. Incorporated 354 Jun-10 . When defining ProjectWise applications. Each user should have a unique working directory. redline.

but the structure containing them will not be available. What is the difference between a logical account and a Windows account? With a Windows account. When you create a new user. SID. Incorporated 355 Module Review Answers . in the password field. the password is not stored in the ProjectWise datasource. Windows accounts are those whose user name and password are not stored in the ProjectWise database. ProjectWise needs to store the ID from the Windows user database corresponding to the user. the password field in the database is not empty. What is stored there? Why is it important to define a default user? What can you do if a folder becomes invisible to you while you are configuring security? True or False: Moving documents is a copy/delete command combination. they inherit settings from the default user. ProjectWise stores the user’s domain security ID. and password.User Accounts User Accounts Questions 1 2 3 Define a ProjectWise user. 3 4 Jun-10 Copyright © 2010 Bentley Systems. Rather than have another column in the table for this purpose. What can you do to minimize the effort spent administering ProjectWise security? 4 5 6 7 8 Answers 1 2 A ProjectWise user is a person with an account in the datasource. however. but are created using the user name and password credentials of an existing Windows domain account. name. description. Logical accounts are those whose user name and password are stored in the ProjectWise database. Create this user first with the most appropriate settings for most users. along with their ID. Which user properties setting is useful to hide the folder structure from users? Queries will still retrieve the documents to which users have access.

Log back in to ProjectWise Explorer and you can see the folder again. 2. 2 3 An environment defines a list of attributes. Name the four main steps used to create an environment. You can create all of the attributes as part of the environment creation process. Incorporated 356 Jun-10 . Create the environment. An interface arranges the presentation of those attributes to the user. users in ProjectWise Explorer can see the Module Review Answers Copyright © 2010 Bentley Systems. Add attributes to. When an interface has been set up for an environment. Each column in the row is an attribute. 6 7 8 Environments Questions 1 2 3 4 5 6 Define an environment. 3. Hide folder hierarchy in user interface. or metadata. The fields in an environment table are called attributes. Assign security to groups instead of individuals. disable the Use Access Control setting. New interfaces are automatically added to each existing environment.Environments 5 In the user Properties dialog in ProjectWise Administrator. and arrange them in. why would you use required fields sparingly? What are attribute sheets? What is a document code? Answers 1 The environment can also be called a table or schema. or you can create some during creation and create the rest later. True. 1. What is an interface? When creating an interface. Add attributes. 4. the interface. explaining the relationship to a database. Create an interface. Think of an environment as a table with a row in it for each document that uses the environment.

you may want to determine which of the recently imported files reference other MicroStation or AutoCAD files. What does it do? What are the results when you import documents using no wizard? After importing any MicroStation or AutoCAD files. By default. They are additional sheets that you create so users can enter multiple values for the same attribute. Jun-10 Copyright © 2010 Bentley Systems. False. Incorporated 357 Module Review Answers . 4 5 6 Because entering data in required fields is time consuming for users. you should not designate an environment for the files you are importing into it.Importing Legacy Documents attributes in that interface on the Attributes and More Attributes tabs of the Document Properties dialog. the user that is logged in to ProjectWise Explorer is the owner of new files and folders. How do you do this? 6 7 Answers 1 2 3 When you want to import a large number of documents without interaction at the desktop. Where do you change that? True or False: When you import files into an existing folder. the key option on the Create a Document page is Apply selected options to succeeding documents. When using the Advanced Wizard. Using the Manager option in the Process Bulkload File portion of the tool. Document codes uniquely identify documents within an environment. and create a relationship in the ProjectWise datasource accordingly. It can be processed immediately or saved and processed when needed. Importing Legacy Documents Questions 1 2 3 4 5 When should you use the Bulkload tool? True or False: You must run a bulkload data file right after you create it.

If you select a parent folder. This means that selecting Document > New > Document in ProjectWise Explorer will open the Create Document dialog.Document Indexing 4 True. it is not necessary. File properties. In this case. only the master file is processed. it will already have an environment assigned to it. which user properties setting should be disabled? When you extract full text. to designate an environment. 5 6 7 Document Indexing Questions 1 2 3 4 5 What must be installed to install any of the document processors? When you create a user account for the extraction user. or recommended. Incorporated 358 Jun-10 . Full text. Using the Scan References and Link Sets wizard in ProjectWise Explorer. Changing an assigned environment is not recommended. Module Review Answers Copyright © 2010 Bentley Systems. 6 7 8 Answers 1 The ProjectWise Orchestration Framework Service. What must you do to force documents to be processed again? Which of the following can you extract from AutoCAD files with no additional configuration? Thumbnails. It lets ProjectWise apply the information that you entered in the wizard pages to the remaining documents that you dropped into the folder. and that copying or moving documents in ProjectWise Explorer using drag and drop will automatically perform the copy or move. where is the actual text index stored? Where does the Indexing Service run? True or False: When processing DGN and/or DWG files. Documents having reference files will only be indexed against the text in the master file. Name two ways to monitor extraction processes. that clicking OK in the Create Multiple dialog will automatically create the specified number of documents with no files attached.

False. you must first create the table in the database. Frequently viewing a folder Audit Trail with many transactions can have an adverse effect on performance. users can’t use the Free command. True or False: If Require Comment is enabled. Why might you want to limit the number of users who can view a folder’s Audit Trail? True or False: If you elect to move audit trail records to a secondary table. The actual text index is stored in the Microsoft catalog. False. Incorporated 359 Module Review Answers . rather than in the ProjectWise database. The user doesn’t have to enter comments because the Free command is not eligible for comments. 3 4 Jun-10 Copyright © 2010 Bentley Systems. expand the General category and disable Use access control. An event is logged whether users enter comments or not.Audit Trail 2 3 4 5 6 7 8 On the Settings tab. On the ProjectWise Integration Server. Answers 1 2 False. True. even though the event is tracked in the Audit Trail. It will be created by ProjectWise when it is needed. and then back in or mark the entire folder for reprocessing. Audit Trail Questions 1 2 3 4 True or False: Users must enter comments for Audit Trail events to be logged. Thumbnails The Windows Task Manager and the ProjectWise provides the Automation Service Administrator. Check the files out.

sub-folders and documents in ProjectWise Explorer will inherit these permissions. This permission set can then be edited and will become the object’s own permission set. Any folders. it automatically inherits the permission set from the previous level. For example. Incorporated 360 Jun-10 . new permissions can be set which the lower levels inherit. True or False: If rights are removed at the user level. you set workflow#1 so it is only accessible to certain users in the datasource. they cannot be given back at the folder level. at any level in ProjectWise Explorer. In ProjectWise Administrator. stateB. True.Access Control Access Control Questions 1 2 3 4 5 Explain the reason for stating that security in ProjectWise is exclusive. As each new level is created. folder and document permissions can be set for the entire datasource in ProjectWise Administrator. stateC. 4 5 If your datasource is not workflow driven. and stateD. Then you can decide which of those users have access to each state in the workflow. Module Review Answers Copyright © 2010 Bentley Systems. In this approach. If rights are removed at the user level. and what permissions each user has for folders or documents in that state. say that workflow#1 has stateA. they cannot be given back at the folder level. Then. What is the object-based approach to access control? When do you use it? What is the workflow-based approach to access control? Answers 1 2 3 It is only applied when some users are explicitly given permissions to certain items that other users are excluded from accessing those items. A workflow security hierarchy.

What is Real security? 6 Answers 1 2 3 An ordered group of milestones through which a document passes on its way to completion. When a document changes state. 4 5 6 In the Properties dialog. Incorporated 361 Module Review Answers . all documents at the root of the folder or project inherit the assigned workflow and are automatically placed in the first state defined for that workflow. Document check out or check in. True. When a document changes version. When the server copy is updated. Jun-10 Copyright © 2010 Bentley Systems.ProjectWise Workflows ProjectWise Workflows Questions 1 2 3 4 5 What is a workflow? What is a state? Name the events on which you can base a messaging agent. The Real (Workflow & Folder) Security Type provides a read-only view of the combined security settings. When a document is exported. Where are workflows assigned to folders? True or False: When you assign a workflow to a folder or project. A milestone within a workflow.

Unmanaged workspace profiles define the location of MicroStation workspaces or AutoCAD profiles. Workspace profiles will take precedence. A configuration settings block is a MicroStation configuration variable and its corresponding values. Change properties in an application’s Properties dialog or create new applications. Bind the attribute to a property type. Create an Attribute Class. which will take precedence? What are the steps for creating attribute exchange rules? Where do you import attribute mappings? 2 3 4 5 6 7 Answers 1 True. Do this using the Applications item in ProjectWise Administrator. 2 3 4 5 6 Module Review Answers Copyright © 2010 Bentley Systems. Incorporated 362 Jun-10 . Often it is advantageous to return a document to a previous state during the design process. Establish the conditions for update. For example.Integrated Applications Integrated Applications Questions 1 True or False: You can create a ProjectWise Application for multiple product versions. Create the attributes for the class. in ProjectWise. Why would you enable the Show Selective Set Open dialog option for users? Why would you use versioning? What is the difference between an unmanaged workspace profile and a configuration settings block? If both configuration settings blocks and workspace profiles are applied to the same document. one for MicroStation V8 XM Edition and one for MicroStation V8i. Users can choose whether to copy or check out references. So the Select Reference Documents dialog appears.

What is a good strategy for handling a situation like this? True or False: It is recommended that each major project be stored in its own storage area. 2 3 Spatial Management Questions 1 2 3 What is a spatial location? How can you add a coordinate system to the Add Coordinate Systems dialog? When does automatic use of a coordinate system happen? Jun-10 Copyright © 2010 Bentley Systems. yielding hundreds or even thousands of projects company wide.Managing Projects 7 From the main Attribute Exchange Rules item in ProjectWise Administrator. there may be multiple active projects at each location. Incorporated 363 Module Review Answers . each project at a particular site would be created as a folder structure within the respective database instance. True or False: The master group for the project should always be applied after creating the sub-folders. True. creating a ProjectWise database instance for each site. 2 3 Answers 1 A likely strategy for an organization of this type would be to implement the one-to-many model. True. Managing Projects Questions 1 In the case of an organization with multiple sites. Then.

all spatial locations drawn over it will automatically be reprojected into this coordinate system. Any ProjectWise document or folder can be associated with a spatial location. on a background map displayed in ProjectWise Explorer. Use the Geospatial Extension or Bentley Map to edit the Coordinate Systems Dictionary.ProjectWise Web Server 4 5 6 Why do you establish a reference coordinate system? Why is it important to set the coordinate system correctly in the Background Map Settings dialog? What document privileges must you have to scan a file with the Spatial Location Scanning tool? Answers 1 A geographical footprint. 2 3 4 5 6 ProjectWise Web Server Questions 1 2 3 4 What operating system is required for Web Parts deployment? True or False: Windows SharePoint Services works with Oracle. Write and File Read privileges. When the background map is displayed in the Spatial Navigator. they will all be presented to the user.0 on an existing SQL Server implementation? True or False: ProjectWise Web Server and ProjectWise Web View Server can both be deployed on the same system. What option must you select to install Windows SharePoint Services 3. These let you locate the associated document. The reference coordinate system is used to compare objects that are in different coordinate systems. If there is only one coordinate system that matches a document. Module Review Answers Copyright © 2010 Bentley Systems. or a folder. Incorporated 364 Jun-10 . If multiple coordinate systems match a document.

Click Advanced and select the Web Front End option. Jun-10 Copyright © 2010 Bentley Systems. Content. you can add it to the page and use it independently without adding any other ProjectWise web parts independently. True. as long as they are deployed to different virtual servers. Answers 1 2 3 4 5 Windows 2003 Server. Incorporated 365 Module Review Answers .ProjectWise Web Server 5 True or False: You can use the Navigation. and Search web part. True. False.

Incorporated 366 Jun-10 .ProjectWise Web Server Module Review Answers Copyright © 2010 Bentley Systems.

Active datasource The datasource you have logged in to and are currently working in. ProjectWise Explorer users on the receiving end of such e-mails can then copy the addresses and paste them into their own Address bar in ProjectWise Explorer. and so on. Action association The relationship between a program and the ProjectWise Explorer commands to open. ProjectWise Explorer users can copy an address in the Address bar and paste it into an e-mail. and the application is associated to documents in ProjectWise Explorer.Glossary A BC D E F G HI JK L M NOPQR S TUVWXYZ A Access control The method for controlling which users have access to documents and folders. When a ProjectWise application has these action associations defined for it. viewing. or print documents associated to a particular application. groups and other access lists who need the same access rights to folders. documents. Address bar The Address bar lets you know where you are in the datasource by displaying the full folder path to and including the selected folder or document. Jun-10 367 Copyright © 2010 Bentley Systems. Incorporated Glossary . redline. view. then the program defined will launch (assuming it is installed) when a user selects a document for opening. Access list An access list is a type of user list that is used when you want to group together users. or printing. redlining.

In ProjectWise Explorer. For specific definitions see Action Association. Extension Associations. The items tracked by an audit trail are specified in ProjectWise Administrator. When you select a document to open. you can open a document's properties and add values for these custom properties on the Attributes and More Attributes tab pages. Attribute sheets Additional layers of attribute values applied to documents. the path to and including the document displays in the Address bar. Incorporated 368 Jun-10 . Attribute exchange Attribute exchange is the process by which tagged elements inside your files. Audit trail The mechanism for recording document and folder activity in the datasource. Associations General term for the relationships between icons and applications. get automatically updated with ProjectWise environment attribute values. Application An item defined in ProjectWise Administrator. When an environment and an interface is applied to a folder. which lets you quickly access documents you work on frequently. Icon Associations. The Address bar also contains a list of documents most recently opened from ProjectWise (referred to as the most recently used (MRU) list). documents are associated to ProjectWise applications so that they always open in the correct physical application. Glossary Copyright © 2010 Bentley Systems. the audit trail itself is viewed in ProjectWise Explorer. used to represent a physical application that users have installed on their computers.The ProjectWise Address bar also exists on document selection dialogs in integrated applications. file types (extensions). such as MicroStation title blocks. Attribute A custom property defined in an environment. or Program Associations. ProjectWise applications generally consist of a name and the file extensions typically associated with the physical application.

Any ProjectWise Integration Server or ProjectWise Gateway Service in the network that receives the broadcast request responds to the request accordingly. Incorporated 369 Glossary . ProjectWise Integration Servers and ProjectWise Gateway Services receive broadcast information through port 5799. Auto-login Auto-login lets a user log in to a datasource without having to enter their user name and password. Check in To upload your modified document. -------------------------------------------------------------------------------- B Background map A background map is a backdrop. a key map that allows the user to locate a spatial location in a geographical environment.Authentication The act of verifying that the user name and password entered during log in matches a user account in the datasource. Broadcast The term used to describe how ProjectWise Explorer and Web Server clients send datasource list requests to the network. By default. Jun-10 Copyright © 2010 Bentley Systems. -------------------------------------------------------------------------------- C Caching See file caching.

components are mapped to tables in the database for persistent storage. Using ProjectWise Class Editor. Component link A class created in ProjectWise Class Editor. but without locking the document. might consider components to be equipment or process lines. Check outs Documents that are currently checked out. used to represent relationships between components. components are extracted from DGN documents in the datasource. and optionally. Component A component is an asset or item that is important to your business (a business object). <. so that other users can also check out or export the document as shared. Comparison operators Expressions (such as >. <=) which allow you to compare values when defining document search criteria. Users in the plant industry. for example. Component indexing Component indexing involves the identification and classification of components within documents. the creation of an index that specifies the location of those components in their respective documents. and windows. Incorporated 370 Jun-10 . Check out as shared To check out a document and download a copy of it to your working directory.Check out To lock a document and download a copy of it to your working directory. doors. the extraction and importation of component data. Using ProjectWise Automation Service. >=. Users in the building industry might consider components to be walls. so that no other user can check out and edit the document until you check it back in. Glossary Copyright © 2010 Bentley Systems.

Incorporated 371 Glossary . and other administrative items. Console A container for hosting administrative tools. Custom folder Custom folders can be thought of as “favorites” where you keep the documents you are working on most often.y coordinate. once they are imported to or created in ProjectWise. or if you are an administrator. without checking out the document. you can create global custom folders that all users to see and use. Copy out To download a copy of a document into your working directory. planar coordinate system in which x measures horizontal distance and y measures vertical distance. Created by The user who created the document. Copy To make a copy of a document to be pasted into another folder. Each point on the plane is defined by an x. Copies Documents that are currently copied out. You can create your own personal custom folders.Configuration settings block MicroStation configuration variables and their corresponding values. Coordinate system A two-dimensional. -------------------------------------------------------------------------------- Jun-10 Copyright © 2010 Bentley Systems. These folders serve as an alternative to the standard folder hierarchy. folders or other containers. enabling one to quickly locate frequently used documents. World Wide Web pages.

Delta file transfer Delta file transfer is the ProjectWise technology that improves performance when sending large files over networks with high latency / low bandwidth connections. Distributed DGNs The collective term for the functionality delivered in both ProjectWise V8 Athens and integrated MicroStation V8 Athens that allows multiple users to export and/ or check out the same DGN document as shared. Datasource The collective term referring to the container of folders and documents. the items defined for that container in ProjectWise Administrator. rather than the entire file. Datasource list In ProjectWise Explorer. documents can be associated to these departments on the General tab page of the Document Properties dialog. The data is then decompressed when it reaches its destination. work on the document simultaneously. use delta file transfer along with existing ProjectWise local file caching functionality. the left side of the application window. Glossary Copyright © 2010 Bentley Systems. The datasource list is displayed in the Navigation web part. in which datasources are listed.D Data compression Data compression is the ProjectWise technology that improves performance over networks with high latency / low bandwidth connections by compressing the data sent to or retrieved from the ProjectWise database. For optimal performance. Performance improvements will be most noticeable with large amounts of data. In ProjectWise Explorer. and merge changes upon import / check in. by only sending the changes needed to update the file. Department An item defined in ProjectWise Administrator. Incorporated 372 Jun-10 . used to group documents by departments in an organization. and the supporting database.

Document An item in a ProjectWise folder. or Reserve. Document list In ProjectWise Explorer. under which projects and folders can be created. Document set A group of documents. -------------------------------------------------------------------------------- E Jun-10 Copyright © 2010 Bentley Systems.DNS See Domain Name System. or a placeholder for an electronic or hard copy file not stored in ProjectWise. Forbid. the right side of the application window. Document code restriction Restricts users to a range of document code when creating documents. Three types of restrictions can be created: Allow. Incorporated 373 Glossary . A Forbid restriction sets a range of document code which users do not have access to. in which the selected folder's documents are displayed. which is either an electronic file. An Allow restriction sets a range of document code which users have access to. A Reserve restriction sets aside a range of document code for future use. Documents root The top level folder in any datasource. Document code A combination of custom attributes which uniquely identify documents within an environment.

Incorporated 374 Jun-10 . Once applied to a folder or project. When an application is created in ProjectWise Administrator. so that it can be sent out to be edited by non-ProjectWise users. -------------------------------------------------------------------------------- F Glossary Copyright © 2010 Bentley Systems. attribute layout (interface). or free it. but without locking the document. An environment can contain attributes. Exporting a document locks the document so that no other user can check out or export and edit the document until you import it.Environment An environment is a collection of supplemental. when files having those extensions are first brought into ProjectWise. Environments are optional in the datasource. organization specific. Extension association The relationship between a file extension and a ProjectWise application. and document code restrictions. the documents therein inherit the attributes of that environment. so that other users can also check out or export the document as shared. those new documents automatically become associated to the ProjectWise applications having those file extensions. and then apply to folders and projects in ProjectWise Explorer or ProjectWise Web Parts. External file A file that exists outside of ProjectWise. and can be seen by opening the Document Properties dialog and going to the Attributes and More Attributes tab. Export To check out a document and download it to a folder outside of your working directory (therefore outside of ProjectWise). document attributes that you establish in the datasource in ProjectWise Administrator. file extensions can be associated to it. and are not required for your folders and projects. Then. Export as shared To check out and download a document to a folder outside of your working directory.

or Gateway Service running in Caching Server mode can be configured to store copies of another ProjectWise server's files. -------------------------------------------------------------------------------- G Jun-10 Copyright © 2010 Bentley Systems. Flat set Documents that are grouped together with no logical structure or dependencies. Folder A container for documents and other folders in the datasource. File name The name of the electronic file attached to a ProjectWise document. Incorporated 375 Glossary . Freeing a document undoes the check out or export. for the purpose of providing fast. local access to documents whose files are stored on a remote server. Caching Server. Any ProjectWise Integration Server. Free To remove a lock on a document.File caching The copying and storing of files from one server's storage area into another server's cache. Footprint See Geometry. Final status The state in which a file can no longer be modified.

when launched from the desktop or by opening a document from ProjectWise Explorer. or to another gateway server.cfg file. only polygons are supported. For example. Incorporated 376 Jun-10 . contains ProjectWise functionality. Glossary Copyright © 2010 Bentley Systems. displays next to the document ProjectWise Explorer. Interface A group of attributes in an environment. -------------------------------------------------------------------------------- I Icon association The relationship between an icon and a ProjectWise application. By configuring the [Gateway] section of a server's dmskrnl. specially arranged by the administrator. Import To check in an exported document.Gateway service The server computer through which a request is routed on its way to its destination. Geometry Any spatial object will have an associated footprint displayed in the Spatial tab in ProjectWise Explorer. Inherit To obtain properties from a container object. a document inherits environment attributes from the folder it is in. to another server instead. In the present version. You can configure this gateway server to forward request directly to their destination. you can instruct clients to send their requests. Integrated application Any application on the ProjectWise Explorer computer which. if one is defined. that application's icon. for display on the Document Properties dialog. When documents are associated to an application. bound for one server. The server now receiving these requests is referred to as the gateway server.

Local Document Organizer The dialog accessible from ProjectWise Explorer that is used to manage documents that you currently have checked out. you can change the locale. or export. models. and which the current version of ProjectWise would otherwise not know about. In MicroStation. if you still have documents checked out or exported from that datasource. When DGN files containing link sets are stored in ProjectWise. Jun-10 Copyright © 2010 Bentley Systems.-------------------------------------------------------------------------------- L Legacy integration Integration support for applications (typically custom applications) whose integration remains based on methods used in previous versions of ProjectWise. Locale The language that words display in. You can also configure Local Document Organizer to open when you log out of datasources. Local copy A copy of a document that has been downloaded from the server. whether by check out. Incorporated 377 Glossary . Any link sets that exist in folders that are not in any project are displayed in the main Link Sets tree. copied out. Link set A link set is basically a group of one or more links to other files. or exported. in ProjectWise windows and dialogs. The default locale is English. and/or saved views that can be stored in a DGN file or a DGN library. which is a subfolder of the Documents root folder. but if you have a ProjectWise language pack installed. references. link sets and their links display in ProjectWise Explorer in the Link Sets tree under the project in which the link set exists. copy out. the Link Set dialog is used to create and manage link sets. whether in ProjectWise Explorer or an integrated application. and the Project Explorer dialog is used to create the actual links.

The opposite of a logical user account is a Windows domain user account. The user name and password are stored in the datasource's database. Glossary Copyright © 2010 Bentley Systems. and other mailing lists. Logical set A DGN or DWG document that has other documents referenced into it. A document that is checked out or exported by another user is said to be locked. so users with e-mail addresses can send and receive messages using Messaging Services in ProjectWise Explorer. Incorporated 378 Jun-10 . Mailing lists are also referred to as Global Address Books. Master document A document that references other documents. groups. Managed workspace A collection of configuration settings blocks that can be assigned to various priority levels in ProjectWise Explorer.Lock To check out or export a document exclusively is to lock the document. -------------------------------------------------------------------------------- M Mailing list A mailing list is a type of user list that is used when you want to group together users with e-mail addresses. Logical user account A ProjectWise user account that is created for the purpose of logging in to a ProjectWise datasource. or freed. imported (for exports). only valid in ProjectWise. so that no other user can make changes to it until the document is checked in.

Messenger See ProjectWise Messenger. but hosts tools that do. not just those opened in the application you are working in. This is referred to as the most recently used (MRU) list. Move To remove a document from one folder and paste it in another. Messaging Services The feature which allows messages to be sent and received in ProjectWise. When MicroStation is integrated with ProjectWise. MMC does not perform administrative functions. so that you can quickly access a DGN document recently opened from ProjectWise. Most recently used (MRU) list At the bottom of most applications' File menu is a list of files that were recently opened in that application. Integration with the File menu MRU list in other integrated applications is not yet supported. The Address bar's MRU list displays all documents recently opened from ProjectWise. Minimum bounding rectangle (MBR) Represents the smallest rectangle completely enclosing a spatial location. Incorporated 379 Glossary . -------------------------------------------------------------------------------- O Jun-10 Copyright © 2010 Bentley Systems. Microsoft Management Console (MMC) Used to create. ProjectWise Administrator runs inside the MMC.Messaging agent A group of settings defined in ProjectWise Administrator for sending a message to users when a triggering action occurs in the datasource. save. the File menu MRU list is also integrated with ProjectWise. and open collections of administrative tools. The address bar in the Open dialog that appears in integrated applications also contains an MRU list.

on either the Search Form or Search Builder dialog. Glossary Copyright © 2010 Bentley Systems. OR group An additional page of search criteria. Permissions The items that set what a user can and cannot do.Open datasource A datasource which you are currently logged in to. Parent document See master document. Incorporated 380 Jun-10 . when access control is used. a password is used to authenticate the user when attempting to log in to a datasource. Organizer See Local Document Organizer. Placeholder document A ProjectWise document that does not have an electronic file attached to it. displays properties of the selected folder or document. below the document list. -------------------------------------------------------------------------------- P Pane A section of the application window. An OR group is used when you want to search on multiple values for the same attribute. Password In combination with a user name. usually separated by a border. Preview pane In ProjectWise Explorer.

the search path of the new saved search is updated to reflect the project it was copied to. documents. Project Projects are a kind of super-folder that provide a single place to manage and organize documents. When you copy a projectaware saved search to another project.Priority search This type of search for references will only search selected folders. Privileges General term for the settings that determine what you are allowed to do with documents and folders and projects. links to other sources of data. Once a project type is created in ProjectWise Administrator and assigned to a project in ProjectWise Explorer. data and resources related to a given real-world project. Incorporated 381 Glossary . Jun-10 Copyright © 2010 Bentley Systems. except that project types can only be assigned to projects. users can open the Project Properties dialog and enter values for those custom project properties on the Properties tab. where the starting point of the search is the project in which the search itself is saved. and contain custom project properties. and they will be searched in the order they are listed in the Scan for References wizard. Project type Project types are similar to environments. Program associations The programs linked to and defined for use with the specified ProjectWise applications. Project types are created in ProjectWise Administrator. and so on. folders. Projects can contain or reference saved searches. ProjectWise Administrator The ProjectWise module that lets you create and manage datasources. components. subprojects. Project-aware saved search A search that is defined to search for documents.

or if you have the proper connectors. Glossary Copyright © 2010 Bentley Systems. modify.ProjectWise Automation Service The portion of ProjectWise that lets you extract components from ProjectWise documents. Incorporated 382 Jun-10 . from which users can check out. When integrated. or you can choose to skip the rendering and simply use ProjectWise Distribution Service as a way to copy documents from one place to another. and then send the rendered documents to another folder. open. You can choose to send copies of the original documents along with the rendered copies to the target location. Bentley Navigator. and otherwise manage their ProjectWise documents. and then manage those components within ProjectWise. open. ProjectWise Explorer The main client interface for ProjectWise. The ProjectWise Caching Server cannot be installed on computers on which ProjectWise Integration Server or ProjectWise Gateway Service is already installed. ProjectWise Distribution Service The portion of ProjectWise that lets you identify a group of documents. ProjectWise Caching Server The ProjectWise server module to install when you want to set up a storage area on a computer other than the Integration Server computer. ProjectWise iDesktop Integration An option of the ProjectWise Explorer installer that integrates supported desktop applications (such as MicroStation. AutoCAD. another datasource. have them rendered using ProjectWise InterPlot Server. The ProjectWise Gateway Service cannot be installed on computers on which ProjectWise Integration Server or ProjectWise Caching Server is already installed. to another document management system. Microsoft Office) with ProjectWise Explorer. and check in ProjectWise documents directly from the integrated application. ProjectWise Gateway Service The ProjectWise server module to install for datasource list publishing. users can check out.

and is the server on which your datasources are created. or another server. ProjectWise Messenger The mechanism optionally available on each ProjectWise Explorer computer for sending and receiving messages between other ProjectWise users. and for receiving messages generated by messaging agents in ProjectWise Administrator. ProjectWise Automation Service. Once these ProjectWise user accounts are created. is said to be a client of the ProjectWise Integration Server. Incorporated 383 Glossary . ProjectWise Orchestration Framework Service ProjectWise Orchestration Framework Service is a required supporting feature of ProjectWise Distribution Service. and the automated document processors that can be installed with ProjectWise Integration Server. accepts text extraction updates to the catalog. Every other ProjectWise module. ProjectWise Integration Server The primary server of ProjectWise. Jun-10 Copyright © 2010 Bentley Systems. whether it is a user client. and executes full text searches as configured and run from ProjectWise Explorer and Web Parts. you can use ProjectWise User Synchronization Service to keep those accounts synchronized with any changes made to their domain or Active Directory counterpart. ProjectWise Indexing Service cannot be installed on a computer on which ProjectWise Integration Server is already installed. or you can install a devoted ProjectWise Indexing Service on another computer to off-load work from the main Integration Server. You can use the ProjectWise Integration Server's Indexing Service. ProjectWise User Synchronization Service The ProjectWise module that leverages Windows domain or Active Directory accounts in order to create ProjectWise user accounts.ProjectWise Indexing Service When the Full Text Indexing feature of ProjectWise Integration Server is installed. ProjectWise Integration Server contains its own Indexing Service which maintains the full text index catalog. an administrative client.

-------------------------------------------------------------------------------- Glossary Copyright © 2010 Bentley Systems. -------------------------------------------------------------------------------- Q Quick view To open and view a document as read-only using either ProjectWise QuickView or the designated viewing application for the selected document's file type. Proximity search This type of search for references will start the search with the top folder selected. ProjectWise Web Parts can be set up in a Microsoft SharePoint portal. Once you install and deploy ProjectWise Web Parts. or project. that document is converted to a format that is able to be displayed by your browser. Properties The general term for all of the general and custom attributes which can define a document. possibly lowbandwidth locations. Web browser-based access to ProjectWise is intended for casual users who are in remote. folder. and is said to be published. Purge To remove local copies of documents from the working directory. there are five web parts that you can add to your portal or web page. or they can be configured on a computer without SharePoint.ProjectWise Web Parts ProjectWise Web Server Components for Web Parts is used to provide a web browser interface for ProjectWise users. then will work its way down until all subfolders are searched. Publish When you select a document for viewing from Web Parts. DGN and DWG documents are published using ProjectWise Publishing Server. Incorporated 384 Jun-10 .

when that request is routed through another server. Redline document A document that contains redlining mark up. the comments are saved in a new redline document. or the permission itself. and the original document becomes a reference of the new redline document. -------------------------------------------------------------------------------- S Jun-10 Copyright © 2010 Bentley Systems. Routed server The destination of any client request. References Documents that are referenced by a master document. Refresh local copy To replace the local copy of a document with the latest copy of the document from the server. Redline To mark up a document with comments or suggested changes. When a document is redlined. Redlined document The original document selected for marking up. Incorporated 385 Glossary .R Read-only Refers to a document which can be viewed but not edited. Register To add a server to a list of available datasources in ProjectWise Administrator.

Glossary Copyright © 2010 Bentley Systems. Incorporated 386 Jun-10 . Also referred to as the ProjectWise Server server copy The master copy of a document that is stored in the datasource's storage area. Server The short form used to refer to the ProjectWise Integration Server. Set See document set. and the results are displayed in the search results window. the search is run simply by clicking on the saved search. and also the criteria used to find documents and/or folders and projects. When you create a saved search. Seed file A file used to create another file. which no other users can see or use.Saved global search A search that an administrative user has saved for other users to see and use. Saved personal search A search that you have saved for personal use. it becomes a saved search. Security See access control. Saved searches are designed to be reused and can be modified as needed. Search Can refer to both the act of finding documents and/or folders and projects. Saved search When you save your search criteria.

Accepted geometry types are point. Single sign on (SSO) Single sign on lets ProjectWise users automatically log in to datasources using the same account with which they are logged in to the computer. polygon. which is a common coordinate system among a group of spatial locations. that user must already have a Windows domain account in datasource they are trying to log in to. A master geometry will also be defined relative to a master coordinate system. The original geometry is stored in the local coordinate system for the file. ProjectWise User Synchronization Service is an example of a snap-in. Shared files The overall term referring to the ProjectWise capabilities that allow users to check out or export documents as shared. and extruded rectangle. Shared check out See check out as shared. Jun-10 Copyright © 2010 Bentley Systems. line. the user will be automatically logged in to the selected datasource. and the integrated MicroStation capabilities that allow users simultaneously edit documents that are checked out as shared. Incorporated 387 Glossary . in ProjectWise Administrator.Shareable document A MicroStation V8 DGN document that has been marked in ProjectWise Explorer so that it can be checked out or exported as shared and simultaneously edited by multiple users at the same time. Snap-in A tool that you can add to a console. For a user to use single sign on. and they must already be logged in to the computer as that user. A spatial location is a geometry and its projection. Then by choosing Datasource > Log in in ProjectWise Explorer. Spatial location A row in the spatial_locations table that stores two geometry representations and a spatial index for business objects in the ProjectWise database.

a document's status might be 'Checked Out'. The Spatial pane contains the Spatial Navigator. Spatial pane The Spatial pane allows to view the selected document's spatial perspective. Glossary Copyright © 2010 Bentley Systems. For example. documents) that intersect with a search area (most likely a minimum bounding rectangle (MBR) defined by the user). Spatial view Used to specify how spatial locations will be drawn according to the attributes of their associated documents. the Spatial Navigator toolbar and the Symbology Legend. folders and documents. the Spatial Navigator displays documents and folders spatial locations over a background map. Incorporated 388 Jun-10 . A more extensive search would then reduce the result set further by checking the geometries of the documents within the search area. Status The condition a document is in. Spatial object Any ProjectWise object that may be associated with a spatial location. Spatial search Finds all spatial objects (for example. for example.Spatial Navigator Located in the Spatial pane. A fast search would check the search area against the MBR of all documents. Storage area The physical folder where all the documents in the datasource exist. State (also called workflow state) A milestone within a workflow.

including Distribution Service / Automation Service Administrator. and also by ProjectWise Web Server for Web Parts when single-sign on is used. the only IP address you need to add to this list is that of the computer on which ProjectWise Web Server for Web Parts is installed.cfg file on the Integration Server computer. a subnet may represent all the computers at one geographic location. but it can also be used to connect to local servers. in one building. Multiple Master Jun-10 Copyright © 2010 Bentley Systems. For ProjectWise Web Server for Web Parts.Subfolder A folder inside a folder. Incorporated 389 Glossary . The trusted servers list is configured in the dmskrnl. Subnet An identifiably separate part of an organization's network. used by ProjectWise when a client computer is connected to a ProjectWise server. -------------------------------------------------------------------------------- T Transmission Control Protocol (TCP) A connection-oriented protocol. Typically. or on the same local area network (LAN). For Distribution Service and Automation Service. to improve client-side performance. TCP is necessary when you want to connect clients to remote servers. the list of trusted servers must be configured to include the IP addresses of all computers running Distribution Service / Automation Service software. Trusted servers A list of IP addresses allowed by ProjectWise Distribution Service and ProjectWise Automation Service. -------------------------------------------------------------------------------- U Universal coordinate system (UCS) A self-describing coordinate system used to relate geometries from other coordinate systems to a common framework for spatial queries.

and so on. Up-to-date When the local copy of a document matches the server copy of a document. Access lists are used when you want to group together users. groups and other access lists who need the same access rights to folders. groups. Glossary Copyright © 2010 Bentley Systems. By default. there is only one UCS and it is defined for the entire datasource. Incorporated 390 Jun-10 . User group A group of ProjectWise users. In the Spatial world. so users with e-mail addresses can send and receive messages using Messaging Services in ProjectWise Explorer. the local copy is said to be up-to-date. Mailing lists (also referred to as Global Address Books) are used when you want to group together users with e-mail addresses. User Datagram Protocol (UDP) A connectionless protocol that runs on top of IP networks. Unmanaged workspace A workspace profile. Update server copy To replace the server copy of a document with your modified local copy of the document.SRCs may be defined within a ProjectWise datasource. User A person who has an account in the datasource. ProjectWise clients request ProjectWise DNS information using the UDP protocol from ProjectWise Gateway Services and ProjectWise Integration Servers that are situated within the same subnet. and other mailing lists. without changing the document's checked out status on the server. documents. User list There are two types of user lists you can create in ProjectWise Administrator — access lists and mailing lists. ProjectWise internal DNS (Domain Name System) information can be retrieved from any server within a subnet using the UDP protocol.

Unlike a logical user account. View To open a document for viewing only. User settings The settings for each user in the datasource. that control what a user can and cannot do in ProjectWise. The ProjectWise Server checks the user's operating system to verify that the user name and password entered are valid in the domain. Windows domain user account A ProjectWise user account which leverages its log in credentials from an existing. a Windows domain account's password is not stored in the datasource. Incorporated 391 Glossary . One document can have many versions. valid Windows account.User name The name under which the user logs in to the datasource. the older versions of documents are always read-only documents. and to some extent the behavior of the user's ProjectWise session. The newest version of a document is always the active version. Jun-10 Copyright © 2010 Bentley Systems. -------------------------------------------------------------------------------- V Version control (versioning) ProjectWise's ability to store and manage multiple versions of documents. -------------------------------------------------------------------------------- W Web Parts See ProjectWise Web Parts.

Workspace profile Defines the location of a MicroStation workspace that exists on a local or network drive. outside of ProjectWise. so that when documents are opened. Workflow state A milestone within a workflow. Once defined in ProjectWise Administrator. Workspace A collection of MicroStation configuration variables and user settings. Incorporated 392 Jun-10 . Working directory The file system folder on a user's computer into which documents from the datasource are downloaded when performing a check out or copy out. workspace profiles are applied to folders and documents in ProjectWise Explorer. Glossary Copyright © 2010 Bentley Systems.Workflow An ordered group of milestones through which a document passes on its way to completion. they open in the workspace defined in the associated workspace profile.

Sign up to vote on this title
UsefulNot useful