same implementation of escalate to program risk
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Hi @MuhmmadU ,
What you’re seeing is expected behavior. Your button works in the classic UI because it’s a standard UI Action, but Project Workspace doesn’t use classic UI Actions at all.
Workspaces (including Project Workspace) are built on the Now Experience UI, which means:
Classic Form/List UI Actions are ignored
Workspace has its own action framework
There’s no switch or checkbox that will make an existing UI Action show up in Workspace
So even though the script is correct, Workspace simply doesn’t know it exists.
How to implement the same button in Project Workspace
To get the same behavior in Workspace, you need to recreate the button as a Workspace Action.
The safest and cleanest way to do this is:
Move the server-side logic out of the UI Action
Put your escalation logic into a Script Include
This makes it reusable from both Classic UI and Workspace
Create a Workspace Action
Go to Now Experience Framework → Actions
Create a new button for the risk table
Decide where it should appear (header or overflow menu)
Call the Script Include from the Workspace Action
Workspace actions run client-side
They call server logic via a Script Include or Data Broker
Handle success/error messages using Workspace notifications instead of gs.addErrorMessage()
Add visibility logic
Use Workspace visibility rules instead of the UI Action condition field
For example, hide the button if the risk is already escalated
Why this extra work is required
Workspace is not just a new skin on top of Classic UI.
It’s a completely different framework, so classic constructs like:
current
UI Action conditions
gs.addErrorMessage()
If this helps you then mark it as helpful and accept it as solution.
