Workspace Lists in Quebec's UI Builder

Aaron Dalton
Tera Expert

Hey y'all!

I'm working on a Workspace in the new UI Framework/UI Builder that I created as an Experience after the Quebec upgrade. I've created a page using the List template, added lists, and setup the config. When I load the page as an admin, everything works as I'd expect it to. However, when a non-admin ITIL user opens the page, the components load, but the List Nav shows no lists in it.

Has anyone run into this? I also can't get the out of box CSM/FSM Configurable Workspace List to load as an ITIL user. I'm seeing this issue in both Patch 1 and Patch 3. I'm leaning more towards this being my configuration, but I've looked at audiences, list applicability, and the general ACLs. I'm not sure where else to look for this.

1 ACCEPTED SOLUTION

HI Aaron,

SNOW support team responded to my support ticket. just posting it here for your reference. I personally think it is totally unacceptable to reconfigure the List Applicability and Audience when it was created automatically by AES. You may check your Audience and List Applicability under the Now Experience Framework

------------------------------------------------------------------

Dear Michael

The lists were not visible to non-admin users because List Applicablility was not configured.
I have created an audience named "Basic Audience" and added List Applicability for each of the UX Lists that are shown on that workspace.

Below are the List Applicability Records -
https://XXXXXInstance.service-now.com/sys_ux_applicability_m2m_list_list.do?sysparm_query=applicability%3D9e2704c01b0230102647a600f54bcb94&sysparm_view=

Below is the link to the Audience record -
https://XXXXXInstance.service-now.com/nav_to.do?uri=sys_ux_applicability.do?sys_id=9e2704c01b0230102647a600f54bcb94

I have added these applicability for the "canvas_user" role and also provided that role to Abel Tuter and now Abel Tuter can see the lists.


This is a step you will need to perform whenever you create a list, otherwise, it will not be visible to non-admins. ->> this is the one I totally cannot accept it.

The solution is applied on XXXXXInstance, you can do the same on your "XXXXXInstance" instance and let us know if it works.

 

----------------------------------------------

screen shot of the steps:

1. Create a new Audience

find_real_file.png

 

2. Then go to List Applicability, recreate all the records for each List menu u set in AES.

find_real_file.png

3. Good luck identify the correct List Menu from the ref view. If you have 20 apps, and each have 20 list menu. I cant imagine how you gonna do this mapping.

find_real_file.png

View solution in original post

13 REPLIES 13

Gosia Urbanska
Giga Guru

I have the same issue. The List Nav is not loading lists

from component documentation:

Define list access privileges

Configure user permissions for the list menu. You can grant users the rights to create, read, update, or delete lists in the menu. When the component has appropriate permissions, users can modify existing lists for their own purpose, even if the New List button is hidden. See Interactions for details.

 

but no info where to define this; 

Yeah unfortunately I’m not seeing any way to define that as well. My case with ServiceNow has been escalated, but they don’t see any configuration to access issues as far as what I’ve done. Still waiting for a solution/further update from them.

Michael Chang1
Tera Guru

anyone find a way to resolve this? 

I’m still waiting to hear back on my case unfortunately. It was escalated and I’ve been told they didn’t see any issues with my configuration or ACLs. Waiting for a solution or another update still at this point.

HI Aaron,

SNOW support team responded to my support ticket. just posting it here for your reference. I personally think it is totally unacceptable to reconfigure the List Applicability and Audience when it was created automatically by AES. You may check your Audience and List Applicability under the Now Experience Framework

------------------------------------------------------------------

Dear Michael

The lists were not visible to non-admin users because List Applicablility was not configured.
I have created an audience named "Basic Audience" and added List Applicability for each of the UX Lists that are shown on that workspace.

Below are the List Applicability Records -
https://XXXXXInstance.service-now.com/sys_ux_applicability_m2m_list_list.do?sysparm_query=applicability%3D9e2704c01b0230102647a600f54bcb94&sysparm_view=

Below is the link to the Audience record -
https://XXXXXInstance.service-now.com/nav_to.do?uri=sys_ux_applicability.do?sys_id=9e2704c01b0230102647a600f54bcb94

I have added these applicability for the "canvas_user" role and also provided that role to Abel Tuter and now Abel Tuter can see the lists.


This is a step you will need to perform whenever you create a list, otherwise, it will not be visible to non-admins. ->> this is the one I totally cannot accept it.

The solution is applied on XXXXXInstance, you can do the same on your "XXXXXInstance" instance and let us know if it works.

 

----------------------------------------------

screen shot of the steps:

1. Create a new Audience

find_real_file.png

 

2. Then go to List Applicability, recreate all the records for each List menu u set in AES.

find_real_file.png

3. Good luck identify the correct List Menu from the ref view. If you have 20 apps, and each have 20 list menu. I cant imagine how you gonna do this mapping.

find_real_file.png