Reference lookup opens behind modal in Playbook

Yathvika · 3 weeks ago

Hi everyone,

I’m facing an issue in a Workspace Playbook. When I click the Save button on playbook activity, a modal opens with a task form. If I click the lookup icon on a reference field (e.g., Assigned To), the lookup dialog opens behind the Save modal instead of in front.

Has anyone experienced this issue? Is there a known fix or workaround for reference lookups opening behind a modal in Workspace/Playbooks?

Thanks in advance!

KPNow · 3 weeks ago

In my opinion, the standard workaround would be to adjust the field presentation or navigation behavior within the Playbook experience. Rather than relying on the modal lookup icon, you can configure the field to use type-ahead search (auto-complete) or convert the modal user action into a direct record view within the Playbook stage workspace rather than spawning a nested modal form. If a modal is strictly required, applying a global UX Theme CSS variable override targeting .now-modal and .now-popover z-index properties (or updating to the latest Playbook Experience store app version where modal stacking contexts have been patched) will ensure reference dialogs render on top.

Hope this helps!

vijaydodla · 3 weeks ago

Hi @Yathvika - Did you check this article https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB1645501 . If this doesn't help, pls do let me know.

Yathvika · 3 weeks ago

Hi @vijaydodla - I don't have access for this article. Can you share me the screenshots in the article if possible.

TIA.

vijaydodla · 3 weeks ago

Here are the details of the article

Issue

Field values are not getting populated when the value is selected from the reference modal by clicking the magnifier icon on the form in custom workspaces. Noticed the below error in the console while selecting the value.

getDataBrokerOperationHandlers.js:93 Unable to locate data broker with id = , operation name = RECORD#GFORM_SET_VALUE
getDataBrokerOperationHandlers.js:93 Unable to locate data broker with id = record, operation name = RECORD#CLOSE_MODAL

Release

All releases

Cause

This issue is seen only on the custom workspaces due to the "controllerElementId" being set to empty ("") for the operationName: RECORD#CLOSE_MODAL in the composition section of the 'sys_ux_macroponent' record of that page variant.

Resolution

Follow the below steps for the issue to be fixed:

Open the page variant that is affected in the UI builder
Go to settings
Click the dropdown under 'Actions' & select 'Page definition' - this will open the sys_ux_macroponent record
Scroll down to the composition section
Within this section, scroll down till you find the elementId: "modalContainerViewport"
Scroll down till you find operationName: RECORD#CLOSE_MODAL
Go to extensionPoints method
Here, replace the empty value ("") of "controllerElementId" with "record" & save the form.
Close the workspace & test the issue, notice the issue is fixed & value gets populated.

Here is the screenshot for your reference.

Please mark the solution Accepted if the above details helped to resolve the issue. Thank you !