ACLs for fields that are different scope from their table
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Hello,
Given the HR Lifecycle Event (sn_hr_le_case) table, I have applied 2 wildcard ACLs:
1. "sn_hr_le_case.*" with condition "HR Service is 123" that allow all fields only if the script returns true.
2. "sn_hr_le_case.*" with condition "HR Service is NOT 123", that is just the wildcard out of the box one.
Then added few field ACLs with condition "HR Service is 123" and generically allow access for snc_internal role and they show as expected.
The problem is with custom fields that were created for the HR LCE Case table but with a different scope - "Agent Workspace for HR Case Management", those ACLs just don't work and they are shows as orange "Passed" when using Access Analyzer.
Anyone experienced that?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago - last edited 3 weeks ago
Check Cross-Scope Privileges:
Since your custom fields were created in a different scope than the sn_hr_core_case table, you need to ensure proper cross-scope access is configured.
Navigate to Application Restricted Caller Access ( Cross-Scope Privileges) within your application's settings and verify that your custom application is granted the necessary read/write access to the HR case table and its fields.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
