Hello,We've created a custom protocol in-house that will launch legacy appli

Hello,We've created a custom protocol in-house that will launch legacy applications from a web page, but I'm having some issues implementing this on an appian form. When I use the following URL as the destination of a link control:runapp://snlentry/westx/DocumentsForm/Environment=2/Flags=-1/KeyObject=103/Key=13585359/ The link works as expected, in that it launches our legacy application.However, having static URLs is not a long-term use case for launching legacy apps, so I created an expression rule whereby various pvs and constants can be passed into the rule to generate the URL dynamically.The expression rule I created looks like this:="<a href='runapp://snlentry/westx/"&'pv!formName_txt'&"/Environment="&'cons!WestXDev'&"/Flags=-1/KeyObject="&'pv!keyObject_int'&"/Key="&'pv!OID_int'&"/'>Launch Me</a>" However, I'm having issues in using this expression rule in a form. I've seen the following behavior:

OriginalPostID-23534

OriginalPostID-23534

  Discussion posts and replies are publicly visible

  • 1) Calling the expression rule from a link component takes me to tempo, since it seems that expression rules can't be set as a link location.2) Calling the expression rule in a message form control renders the text "Launch Me," as a link, but nothing happens when the link is clicked on the form.3) Calling the expression rule as the default value in a text form control generates what appears to be valid html, including inserting the values of the constant and the process variables in the expression rule:<a href='runapp://snlentry/westx/DocumentsForm/Environment=2/Flags=-1/KeyObject=103/Key=13585359/'>Launch Me</a>but this is not rendered as a hyperlink, but only as the text above.Any assistance with this would be greatly appreciated. Again, the end goal would be to have an expression rule (or similar) that would allow links like these to be generated dynamically based on the values of process variables.
  • This is due to the security of the application. Antisamy rules applied to the properties of the <a> tag prevent any URI schemas other than sftp, http/s, ftp/s and mailto. For more information re: this setting with Appian Cloud sites, please open a support case.