UI Action - Form Link - SOW Workspace

[swathi55]

Hello,

I created a UI Action (Form Link) on a custom table/form and need it to be available in the Service Operations Workspace (SOW). I created a corresponding Workspace Client Script, and the link is displayed correctly in the workspace.

However, the URL is not a standard HTTP/HTTPS URL. It is a custom protocol/application link intended to launch a locally installed application on the user's machine.

While the link is visible in the workspace, clicking it does not trigger any action. Has anyone implemented a similar use case in Workspace? Is there a supported way to launch a locally installed application or invoke a custom protocol from a UI Action/Form Link in SOW Workspace?

Thanks

[Sachin_Nasa]

Hi @swathi55 ,
Could you please share the script which you used and some screenshots to resolve please.

[swathi55]

Below is the script i am using 

function onClick(g_form) {

var url = "pw://dpewrt-pw.babcdey.com:dpewrt-pw/Docs";

window.location.href = url;

}

As its not a http link. nothing is happening when i click on the link.

[swathi55]

@Sachin_Nasa  -  Any suggestions on this?

[Sachin_Nasa]

Hi @swathi55 ,

From the script, it looks like the main difference is pw:// is a custom URI scheme rather than a standard HTTP/HTTPS URL.

In SOW, the Workspace Client Script can execute browser-side JavaScript, but whether a custom protocol can launch a locally installed application is also dependent on the browser/OS handling and whether the pw:// protocol is properly registered on the user's machine.

As a first test, could you try opening the same pw://... URI directly in the browser address bar? If it doesn't launch there either, the issue is likely with the local protocol registration rather than the ServiceNow UI Action.

If it works directly in the browser but not from SOW, then it would be worth checking whether the Workspace/browser is blocking or restricting the custom scheme. A normal https:// URL can be tested from the same UI Action to confirm that the Workspace Client Script itself is executing correctly.