Skip to main content

href in long feature description to ProjectWise

Comments

3 comments

  • Tom Neer
    Latitude limits the protocols used in the Feature Descriptions pretty tightly. To get around this, create a Workflow with an input parameter that opens a web page, call the Workflow, pass in the url/uri. This will get around this. We use it for file:// and ftp:// also.
    0
  • Permanently deleted user
    Hi @Tom Neer

     

    Thanks for your comments

     

    I tried to create a workflow and used run command to open a web page. It worked fine for me both in feature long description or even as a separated button for normal Http or Https URI but when I changed the input to the ProjectWise URL or even local drive URI I got the below error.

     

    https://drive.google.com/file/d/1Tks9unKJmPNB-EjvHqKSWQw4MVmNJ1Fz/view?usp=sharing

     

    Can you please take a look at WF5 and let me know where is the issue.

     

    WF5 can find in below:

     

    https://drive.google.com/file/d/1w20vAHO75E56lrLUdBugllAVzIt9abPW/view?usp=sharing

     

     
    0
  • Tom Neer
    Well Bentley never makes things easy. So because ProjectWise is using a proprietary ProjectWise protocol (PW://server:datasource). I would suspect that the ability to launch into ProjectWise Explorer.is dependant on having the correct software installed to be able to handle the custom URI.

     

     

    In this case you are using a Web Browser which requires a protocol handler for ProjectWise to be registered. I would have to defer to Bentley on this one. Essentially, the browser doesn't know what to do with the pw protocol.

     

     

    You can, if you are so inclined, get around this by registering an application to a URI Scheme. This would probably need to be setup as a GPO policy for your organization for full rollout.
    0

Please sign in to leave a comment.