href in long feature description to ProjectWise
Hi Guys
I'm trying to create a hyperlink to a ProjectWise folder in long feature description.
I tried some of below methods but none of them works
<a href="pw://ABC-au-pw.bentley.com:ABC-AU-PW-11/Documents/">PW</a>
<a href="file:///pw://ABC-au-pw.bentley.com:ABC-AU-PW-11/Documents/">PW</a>
<a href="RunCommand=OpenWebpage?pw://ABC-au-pw.bentley.com:ABC-AU-PW-11/Documents/">PW</a>
but the original link works in the browser. I also tried to put the link in a field but it was not recognised as an external link
if you have a look the Bently community they suggested the same ways and it worked for me in a simple HTML page.
Could you please let me know what is going wrong in GC Viewer,
Cheers
0
-
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 -
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=sharing0 -
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.
Comments
3 comments