Workspace Rule (sysrule_view_workspace) not firing at all

[IrfanS070204351]

I have an issue where there are two UI views created (Example A & B) in sys_ui_view for two different projects in same instance for sn_audit_advanced_plan and sn_audit_engagement tables form view with custom roles created for users under those projects and single UI rule created in sysrule_view and sysrule_view_workspace to ensure logged in users depending on roles they have is re-directed to respective UI view while admin should not be restricted to any view and can change the view as we have two teams currently working on different views.

The issue is that while sysrule_view rule works correctly for classic UI view where users from both tracks are correctly re-directed to respective UI views when they open respective tables of IRM but sysrule_view_workspace rule for those tables never fire and always default to a view called "workspace" which is a kind of default view and specific fields added on those two UI views (Example A & B) are missing though the "Advanced" script in both UI View rules are exactly same and only workspace rule do not work.  Has someone come across this weird issue where classic UI only works and sysrule_view_workspace do not trigger at all (logging in sysrule_view_workspace is not captured confirming rule is not firing) in any case? Any help or insights on this use case would be great. 

[An Le]

Hi @IrfanS070204351 ,

 Please check these 2 articles; I think they are useful for you:

https://www.servicenow.com/community/next-experience-articles/how-to-create-a-workspace-experience-v...

https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB1276673

Kind regards,

An Le

[IrfanS070204351]

I do not have access to these articles. Can you share its content in this thread please? 

[An Le]

Hi @IrfanS070204351 ,

please check

Cause

This issue can occur when:

• The UX View Rules Configuration [sys_ux_view_rules_configuration] record is missing.
• The View rule [sysrule_view_workspace] record is not in the same scope as the workspace.

Resolution

For details on configuring view rules, see How to use view rules in a Workspace Experience in Related Links.

For details on configuring view rules, see "How to use view rules in a Workspace Experience" in Related Links.

Verify the view rule configuration

1. Confirm the view works on the platform by appending the view name to the URL: sysparm_view=<view_name>&sysparm_view_forced=true
2. Verify the View rule [sysrule_view_workspace] record is in the same scope as the workspace.
3. Check if the Process Automation Experience Demo playbook view is affecting the configuration: https://instancename.service-now.com/nav_to.do?uri=sysrule_view_workspace.do?sys_id=5aaa060bff422010...
4. If the UX View Rules Configuration record does not exist, create a UX Page Property record with the following values:
   • Name: viewRuleConfigId
   • Value: The sys_id of the view rules configuration record
   Note: Customer Service Management (CSM) and Field Service Management (FSM) workspaces have this configured by default. See the following URL for reference: https://<instance_name>.service-now.com/nav_to.do?uri=sys_ux_page_property.do?sys_id=32eb9cfd53c3101043d7ddeeff7b1214

[IrfanS070204351]

Thank you for your response.  UX View Rules Configuration [sys_ux_view_rules_configuration] record is available and also tried to create new sysrule_view_workspace in both Audit and Risk workspace application scope (original record is in GRC:Advanced Audit application scope) and deactivated other UI View rules for testing but issue persists.
Even sysparm_view_forced=true in URL do not work in workspace view