Special Characters such as <> are found as invalid when creating document codes in PW 365. PW Explorer automatically changes these special characters to dashes which are supported. We would like PW 365 to behave the same way as Explorer.
Allow Users to Upload personal markups in place of PDF whilst in Doc Review Cycle.. Either a button to 'launch pdf from desktop' button during review, or a simple option to be able to drag and drop a file over the old one
Trigger attribute value based on a group membership
Under an attribute we can set a trigger to update the value Request is to allow group or list membership to be a trigger. Example if member of a group, set attribute to Yes
ProjectWise Explorer integration to Adobe Professional and Adobe Reader
Is it possible to add to our PW Explorer roadmap, integration to Adobe Professional and Adobe Reader ?
Integration in this case means :
File Open/Save command in Adobe opens PW dialog screen with files.
Batch operations in Adobe Professional e...
User Interface: Allowing mouse buttons for "Page Forward" and "Page Back" to navigate folders
The page forward and back buttons on a mouse should navigate folders within projectwise. These mouse buttons are typically found on the side of a mouse for the thumb to control, but sometimes they're integrated into the mouse wheel so tilting the ...
The interface form is fix in terms of dimension, which limit us in terms of attributes we can place. To help us gain more space, we would like the option to display attributes label within the attribute.
We face a situation where we cannot have the PDF and the DWG store inside the same folder because the unique identifier is based on the document name ( which do not have the extension when using the Rules Engine) For ProjectWise to have a unique i...
0
Needs review