Resolve Declarative Action, shows a different pop up for admin's

[saint]

Hi Experts,

I recently created a variant for a page in Service Operations Workspace for Admins by using Audiences and a custom View, and then applied that view to the variant.

After this setup:

• Fulfillers can see the data relevant to them
• Admins see admin-specific fields and data
• A custom role sees only the fields and data intended for that role

So far, everything is working as expected except for one issue on the Incident form for admins.

Issue for Admins only;

When clicking the Resolve button:

Instead of showing only the Resolution Code and Resolution Notes fields in the popup,
The popup displays all fields from the Incident form again.

This behavior was not present before applying the variant and view.
I’m not sure why this is happening or what configuration is causing the Resolve dialog to ignore the intended field set.

I would really appreciate any insights or guidance on:

Why the Resolve popup is showing all fields
How to restrict it to only Resolution fields when using variants and views in Workspace

Thanks in advance for your help—urgent assistance would be greatly appreciated.

[jcmings]

Weird. Have you traced the event on that button component in UIB? I'd start there to see if it somehow got to modified to display a different view. Also check out the UI action to see what workspace client script is running onclick.

[saint]

Hi   ,

Thanks for your response. I've done some research on the UI action based on your 2nd point. And I don't see any changes to either the UI action or declarative UI action, I've attached the screenshots of both here, the version has no change and the client script as you mentioned seems to be running onclick too.

I think I can eliminate the idea of something going wrong here. 

I have verified that the fields shown on the popup when Resolve is clicked has the SOW view (which is same as applied for the form) I don't know if this matters, just an observation.

I'm currently looking into how to trace the event as you mentioned in the 1st point and trying to find the issue.