ProjectWise Navigator lets you register your markups to provide a structured approach to creating and preserving comments and status. All markup information is stored in the overlay file and no changes are made to the original file. Upon closing the file you can choose to save the overlay file (.overlay.dgn), which references the original file.
Markups are listed in Markup dialog (By default Markups Dialog button is hidden in MicroStation you have to right click on Primary Tools bar select Markups Dialog).
Created by, Date Created fields are filled automatically, but the Priority, Status, Assigned To and Approved by field values can be entered manually. Priority to and Status value list can be changed. Value lists are configured in MarkupConfig.xml which is stored in \WorkSpace\System\Data\.
By default, only markups saved within an existing overlay file will appear in the Markups dialog list. You can look for the other markups related to the design by filtering them out. Three options of filtering are given: Active Markups, Related Markups, All Markups.
Markup Search Path defines the location where to look for the overlay files. By default markups are picked up from the folder where the overlay file is opened or folder where the referenced original file exist. By setting the MS_MARKUPPATH variable, you can specify the location. For example, you may look for overlays within the Project and its subfolders of the opened file if you set MS_MARKUPPATH to $(DMS_PROJECT(_DGNDIR)). You could also make it look in all datasource by setting the PW:\\SERVER:DATASOURCE\Documents\ value to the variable, but keep in mind it will have to scan through all folder looking for the overlays so it may take a while each time you open Markups dialog.
Access security control affects the Markup appearance in markup dialog also. Folder Read and File Read Access needed for the overlay file to display Markups from to the user.
You can prevent Markups from being discovered in Markups dialog by denying access rights to the overlay file where they are stored.
For example, related markup will not be discovered by anyone but you in Markup dialog if....
Only 3. and 4. overlays will be shown in the list if you go Document > Set > Show Markups for that design file.
Same configuration applies to the MicroStation Markup Dialog.
Consider scenario where you would like to have control over which Markups to display or not to a group of users. One option to achieve this is by setting the correct access security for Designers and Reviewer teams to Project folders "Published Markups" and "Unpublished Markups". Moving the overlay file between those two folders would give just that control. Gaining Document Read access for the document will let Designers discover those Markups in MicroStation application.
The second option is to introduce workflow based security for the overlay files. Create two states (published/unpublished) with correct right for the documents. Setting access security for Markups folder would let Reviewers promote/demote their markups by changing the state. Designers will have markups appear in their MicroStation Markup Dialog when document gets published sate.
Moving the Design file will break link to the design file in overlay. To fix this you will need to scan for References or open each overlay file with ProjectWise Navigator to fix it manually.
JP
Hi Jo
Is there a projectwise variable which points to the projectwise folder that the document is in, if so could i use it to define a markup folder off the main folder ? ie a dynamic MS_MARKUPPATH , i am using managed workspace. There is a PW system variable $VAULT.FULLNAME$ could this be used ?
Thanks