Workspace view rule is getting unexpectedly applied to a popup that shows on button click

[Kirthika D]

We applied a workspace view rule to show Default view of Policy Exception form on the Compliance Workspace instead of the Workspace view. 

When this view rule is active, clicking on the "Request extension" button shows a popup with the whole form of Policy Exception record instead of just the fields identified on the "add_extention" UI Page, like - valid to, valid from, extension date, etc. 

And it hinders the request extension functionality. 

Is there a way to avoid this behavior and show the popup as it is supposed to be, while enforcing the default view to show on the record page of Policy exception record in the workspace? 

This behavior is specific to workspace only. The same record on native view has the button functioning as expected. 

[satyasubraV3614]

Yes, this behavior can be controlled from the modal invocation itself.

To ensure the popup displays only the intended UI (such as the fields defined in the add_extension UI Page), you can use the g_modal.showFrame() method instead.

This approach allows you to explicitly control the rendering by passing parameters such as sysparm_view in the URL. By doing so, the modal will load the desired view (e.g., default) or UI Page content, effectively bypassing the Workspace View Rule for that popup.

[Kirthika D]

Well, we tried that. It shows the popup. 

But the UI page has scripts that should auto-populate values in specific fields on the popup. That isn't working.

Any ideas?