If you have a Panel which only contains attributes and variables, and all of those attributes and variables have Show/Hide security enabled, WorkWithPlus will automatically hide the panel when some user do not have permission to visualize any of the attributes and variables within that Panel.
For example, lets suppose that you need to restrict the visualization of the information of Auditing for Company transaction (date, user that created the record, and date, user that modify for last that record of Company) .
So, you open Company transaction, select the four attributes and enable Hide/Show Security (changing the property 'Enable Show/Hide Security to True)':
Then, if you visualize the form of Company transaction (in the instance), these four auditing attributes are grouped into a panel named 'Auditing'
As these four attributes have security enabled, if some user logs in to the application and does not have permission to visualize any of these attributes, the panel will be hidden.
It is important to have in mind that every time that we change some 'Security Functionality Key' (in this case we have new permissions for these attributes) and we want to impact these changes in the application at runtime, we have to follow the steps of the section Update Security Functionalities of Advanced Security or GAM (depending on the Security that we have enabled):
Then, after following the steps above and making build all, you can visualize the changes at runtime (the security for attributes using Advanced Security or GAM is the same from developers point of view, the only difference is that they use different objects in order to configure the permissions of each role).
So, john logs in to the application (john has associated 'New Role' role), and he doesn't have permission to any of the four auditing attributes of Company. He goes to edit some Company and visualize what follows:
As we can visualize, panel 'Auditing' is not visible. Now, lets give permission to 'New Role' role, for visualizing just 'CompanyCreateDate' attribute (we log in as an administrator in order to do this):
Finally, John logs in to the application and goes to edit a Company. He is able to visualize the panel 'Auditing' and some of the content:
And it analogous with Tabs, if you have a Tab which only contains attributes, and all of those attribute have Show/Hide security enabled, WorkWithPlus will automatically hide the tab when some user do not have permission to visualize any of the attributes within that tab.
For example, lets supose that all the attributes within the second tab of Person must have security of visualization:
We select them and enable Show/Hide Security:
As it is explained beofre, every time that we change some 'Security Functionality Key' (in this case we have new permissions for these attributes) and we want to impact these changes in the application at runtime, we have to follow the steps of the section Update Security Functionalities of Advanced Security or GAM (depending on the Security that we have enabled):
Then, after following the steps above and making build all, you can visualize the changes at runtime (the security for attributes using Advanced Security or GAM is the same from developers point of view, the only difference is that they use different objects in order to configure the permissions of each role).
John logs in to the application, and goes to edit some Person:
Now the administrator logs in and gives permission to John (role 'New Role' to visualize PersonHomeAddressRequired, PersonHomeAddress, PersonCellNumber and PersonHomeTellNumber):
John logs in to the application and goes to edit some Person, now he can visualize some attributes within the third tab:
|