OOB UI policy Show HR service fields on load is causing cross scope errorsDescriptionIf you have a case field in a scope other than HR core scope (e.g. a custom field in LE case table which belongs to LE scope), and you added this custom field to the HR service (for LE COE) service table fields, it will give a cross scope access error on loading the LE case form. Example of the error message: 'Display true not set on field 'u_customfield': cross-scope access denied'.Steps to Reproduce Configure an HR service record.Configure the form layout in a corresponding scope, to manually add the same service table fields.Configure the 'Hide HR service fields and related lists' UI policy. Expected behavior: The 'Show HR service fields on load' UI Policy should automatically take place. Actual behavior: When landing on a sn_hr_le_case form, an error message displays at the bottom.Workaround1. Apply all the changes from the defect fix. 2. There is a limitation were fields cannot be controlled unless they are in the scope of the table they are on (e.g., cannot control a Lifecycle Event scope field that is added to HR Case table) 3. Custom fields that need to be controlled by the show/hide UI policies should be added in the same scope as the table they are added to (e.g., Fields added to the HR Case table should be in the sn_hr_core scope. Related docs: https://docs.servicenow.com/bundle/utah-employee-service-management/page/product/human-resources/task/configure-case-form-for-hr-service.htmlRelated Problem: PRB1618841