SlicerDicer applies the user ' s security when it retrieves data, and a user who lacks authorization for particular data will not receive that data. In this scenario, the session loads but returns no data for the restricted content. The user is not shown protected information, and no override is offered. A generic error is not the designed behavior, since the application does not treat the restriction as a failure. The session does not save automatically as a result of a security restriction; saving is a deliberate action. A summary is not displayed in place of the restricted detail, which would risk disclosing information the user is not entitled to see. The outcome can be confusing to users, who may assume that the data does not exist, and support staff should recognize the pattern: an empty result for a population that should have members suggests a security limit. The same applies when a shared session is opened by a recipient with narrower access, who may see fewer records than the sender. Reviewing the recipient ' s security classes is the appropriate diagnostic step in both situations.
[Reference: Cogito Fundamentals – SlicerDicer: Security and Data Access, ===============, ]
Contribute your Thoughts:
Chosen Answer:
This is a voting comment (?). You can switch to a simple comment. It is better to Upvote an existing comment if you don't have anything to add.
Submit