Workspace Lists in Quebec's UI Builder

[Aaron Dalton]

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.

[Aaron Dalton]

This did it! I recreated the list applicabilities for all 61 of my lists.

1. I had previously created an audience for my Workspace. I just added canvas_user to the roles (this role will change, but it's what I picked for testing) for this.
2. Recreated List Applicabilities on sys_ux_applicability_m2m_list for all 61 of my lists and related them to the audience I created.
3. Impersonated a non-admin and it's now working!

[Michael Chang1]

Hi Aaron,

SNOW has responded and recognise this as an issue and created a PRB. It is due to the role created in AES, must be all lower case, besides, to grant user as canvas_user role. I have tested it with new workspace with the roles created in lowercase, it works without creating the additional audiences and applicability. 

see the reply from them as below:

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

1. Do we create roles without capital letter for all the workspaces we create in AES?
Yes, roles' name should contain only lower case characters.

2. By creating the role in small letter, does it link and audience and Applicability automatically?
No, it does not. There is an other issue in creating audience / configs for workspaces created via App Engine Studio. We have reported a PRB for Development team PRB1517144 for this one.

3. Do we need to run the script to patch existing workspace I have created? Or just rename the existing role and grant the user canvas_user role?
Yes, you need grant the role canvas_user to the user who are impacted and you need to run the background script to correct the configuration.

To reiterate, you need to apply all 3 fixes below to resolve the issue at hand

1) Change the roles' names to contain only lower case letters
2) Run the script to correct the audience configuration 
3) Grant the role canvas_user to impacted users.

This is the background scripts to patch the existing workspace. You may need to change the sys id.

// Remove the relation between sys_ux_applicability_m2m_list and the applicability for existing records
var applicability_m2mGr = new GlideRecord("sys_ux_applicability_m2m_list");
applicability_m2mGr.addQuery('applicability','bfa248ee1b35b0104a54ed7de54bcbb0');
applicability_m2mGr.query();
while(applicability_m2mGr.next()){
    gs.info("Updating the record " + applicability_m2mGr.sys_id);
    applicability_m2mGr.applicability = '';
    applicability_m2mGr.update();
}

// Create new sys_ux_applicability_m2m_list for list records with "IT Project Management Workspace_menu_config"

var uxlistGr = new GlideRecord('sys_ux_list');
uxlistGr.addQuery('configuration=4e43e3681b7970504a54ed7de54bcb4d');
uxlistGr.query();
while(uxlistGr.next()){
    var applicability_m2m = new GlideRecord("sys_ux_applicability_m2m_list");
    applicability_m2m.active = true;
    applicability_m2m.applicability = 'bfa248ee1b35b0104a54ed7de54bcbb0';
    applicability_m2m.list = uxlistGr.sys_id;
    applicability_m2m.order = 100
    applicability_m2m.insert();
    gs.info("Created the record " + applicability_m2m.sys_id);
}

[Edvin-Karalius]

It has been 4 years now and they still haven't fixed this...

amazing!

[Michael Chang1]

Hi Aaron,

Gotten the update from SNOW Support team. You may check the name of the role you set in the AES.

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