Restrict data according to privileges or information saved in session storage
In modern application development, securing and finely managing data access are essential. Thanks to the restrict event in 4D, it is possible to dynamically filter the data accessible to a user based on their profile, privileges, and session-stored information.
This blog explains how to leverage this event, particularly in the context of an integration with 4D Qodly Pro, to ensure that only relevant data is exposed.
ORDA – Restrict Data to Relevant Criteria
In 4D 19 R8, we introduced a robust permission system, granting you granular control over user access to your data. This system protects your data depending on who accesses it and which data is accessed, ensuring data security by restricting unauthorized access.
But what if you wanted to further refine read access based on specific criteria?
That’s where 4D 20 R5 steps in. Restricting read data according to some criteria.