List Menu in a custom Now Experience Workspace cannot be loaded for non-admin role
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-08-2021 11:21 AM
Dear all,
I'm having a problem with List Menu component in a custom Now Experience Workspace. My users who are a non-admin role, could not load the list menu in the workspace I created for them. it appears that it will show an empty page as per the screen below.
- Update 1: it works if we grant the admin role to the user. so suspect it is due to ACL.
- Update 2: I tried creating a new app with the ready template in AES, users also facing the issue if they do not have admin role.
- Update 3: User can access to the home page, create record, view record, and able to create My Lists. just not able to view List Menu.
- Update 4: Use debug mode and did not throw any error on the graphql/glideListMenu for the user (I use impersonation to test)
So far I've tried a few things including
1. recreate the workspace using vanilla template - not working
2. set ACL for the user roles in the workspace to have the read access to sys_ux_list, sys_ux_list_category, sys_ux_list_menu_config, and sys_ux_my_list - not working
3. grant direct role to the user with 'workspace_user' role - not working
Im running out of idea what could have caused it. Hope if there is anyone in the forum is able to enlighten what could be the issues.
Thanks.
- Labels:
-
Now Experience UI Framework
- 2,859 Views

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-15-2021 09:14 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-15-2021 10:22 AM
Hi John,
Yes, created the necessary role in the AES. FYI, i have posted an reply on the other thread regarding to this issue. May be can shred some light of the problem in Now Experience Framework.
Workspace Lists in Quebec's UI Builder - Developer Community - Question - ServiceNow Community
ServiceNow support team still attending to this issue. Will post the updates once gotten better solution from them .
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-15-2021 10:35 AM
Guys, you may check on this. Gotten the reply from ServiceNow support team.
So apparently, we need to name the role we created in lower case. it is a known bug and will be fixed in Rome.
This is caused by multiple issues :
1) Applicability(audience) does not work if the role contains upper case characters [Existing PRB PRB1487424 fixed in Rome]
2) The users should have canvas_user role to access the workspaces created using the App Engine Studio [ Doc Request DOC129496 attached to this case]
3) Issue in creating the audience records when creating workspaces using App Engine Studio [Created a new Problem PRB1517144 and attached to this case]
Steps to relief :
For Cause 1 - Applicability does not work if the role contains upper case characters [Existing PRB PRB1487424 fixed in Rome]
[Fix] : Update the following roles' name to contain only lower case characters
https://dev4ytlcementtesttemp1.service-now.com/sys_user_role_list.do?sysparm_query=nameSTARTSWITHx_y...
For Cause 2- The users should have canvas_user role to access the workspaces created using the App Engine Studio
[Fix] :Add the role canvas_user to the user in question.
For Cause 3 - Issue in creating the audience records when creating workspaces using App Engine Studio