Hi Curt!
thank you for your reply. Please excuse if I am asking trivial things, but I am a littl bit overwhelmed by the huge amount of available documentation. I could, until now, only find documentation about how I can express read restrictions on a role-enetity base (role X is not allowed to read entities of type Y). As said, I need to express such restrictions with conditions. Can you perhaps give me a hint where I can find documentation about this or where in the product I should look to get a deeper insight?
Kind regards,
Markus
Curt Raddatz wrote:
thank you for your reply. Please excuse if I am asking trivial things, but I am a littl bit overwhelmed by the huge amount of available documentation. I could, until now, only find documentation about how I can express read restrictions on a role-enetity base (role X is not allowed to read entities of type Y). As said, I need to express such restrictions with conditions. Can you perhaps give me a hint where I can find documentation about this or where in the product I should look to get a deeper insight?
Kind regards,
Markus
Curt Raddatz wrote:
The Outsystems platform, like most other software development platforms, provides the tools you need to do this but it's almost all in how you design the database. Even if you use the built in Roles and Groups, you must still define the relationship between projects and individuals and define the organizational hierarchy. The later is needed so you can 'show all project for which <name> is a project manager'. Assuming you have a competent database designer this would work exactly the same as any other platform.
Hope this helps,
Curt
Hope this helps,
Curt