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

[Ankur Bawiskar]

@swathi55 

you didn't share the script etc and screenshots

[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.

[Tanushree Maiti]

Hi @swathi55 

Please share the script so others can review it and help you troubleshoot the issue.

[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.

[wordsofwond]

This sounds like a browser security restriction rather than an issue with the UI Action itself. Since the Form Link is displayed correctly in Service Operations Workspace, the Workspace Client Script is most likely working as expected.

Custom protocols that launch locally installed applications are often blocked or restricted by the browser and workspace framework. Even if the link uses something like myapp://..., the browser may prevent the navigation unless the protocol is registered correctly and explicitly allowed by the client environment.

I would verify the custom protocol directly in the browser first, outside ServiceNow. If it works there but not in SOW, check whether the Workspace UI framework allows custom-protocol navigation from that particular component. You may need to use a supported client-side integration, browser extension, or locally installed helper application instead of directly invoking the protocol from the UI Action.

Also test the behavior in the exact browser and managed-device environment used by your users, since enterprise browser policies can prevent external protocol handlers from launching.

[Message edited by mod - kindly avoid all types of self-promotion on the forum]