Application Cross Scope privilege not working.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
28m ago
& There is no sys_restricted_caller_access record & no sys_scope_privilege record made against this custom scope table.
As per my perspective custom table record should not delete but actually record is deleted, Why????
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
20m ago
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
46 seconds ago
hi @SatyendraS18225 ,
The important thing to understand here is that the Can delete setting under Application Access is related to cross-scope access. It does not necessarily block a server-side GlideRecord.deleteRecord() call when the code is executing within the same application scope as the target table.
In your example, I would check the following:
-
Application scope: Confirm the scope in which the Business Rule executes and compare it with the scope of
x_1981567_peak_de_iceing. -
Cross-scope access: If the Business Rule runs from a different scope, check the cross-scope privileges and restricted caller access configuration.
-
Delete ACLs: Check whether any applicable delete ACLs restrict deletion. Standard
GlideRecorddoes not enforce record ACLs in the same way asGlideRecordSecure. -
Test with
GlideRecordSecure: You can use this to verify whether ACL enforcement changes the result, although it is not a substitute for checking cross-scope access.
Also, make sure you distinguish between Application Access restrictions and ACL enforcement. They are separate security mechanisms.
If the Business Rule and the custom table are both in the Peak scope, the deletion may be allowed because the operation is occurring within the same scope, even though the Can delete checkbox is unchecked.
If this helps, please mark it helpful or accept it as the solution.
Regards,
Tejas
