I agree with J - it's all about the data model. In order to do this, the application must know how the people in your organization are related to each other - a database version of an org chart. Typically what is done is to add a ParentUserID to the User information. In Outsystems it is common practice to create a UserExtend entity which is a one-for-one match to the User entity which would contain these types of extra fields. You need to create a screen to be able to set these values. Once the data is there its easy to write an aggregate that selects data for an individual, a team leader (all ParentUserId = team leader User Id) and Team Chief (all team leaders with ParentUserId = team chief and all subordinates). If the user has privileges for all data then just select all data.
In a project I'm working on I'm trying to create this type of mechanism that leverages the Outsystems Groups and Roles and create the parent/child relationship between roles. That would be a more advanced way of doing this. Unfortunately I'm really early in my design so have nothing I can show you at the moment.
Hope this helps,
Curt
In a project I'm working on I'm trying to create this type of mechanism that leverages the Outsystems Groups and Roles and create the parent/child relationship between roles. That would be a more advanced way of doing this. Unfortunately I'm really early in my design so have nothing I can show you at the moment.
Hope this helps,
Curt