WorkWithPlus integrates with GAM in order to provide security to your KB. You can read further information about this in the following link: GAM + WorkWithPlus
The verification whether some user can access an object (Web Panel, or Report) will be done automatically by GAM Security.
So, we only have to care about assigning security to actions, links, tabs or attributes. WorkWithPlus will add the code in order to verify if some user can click in some action or link and will hide/disable the action when user does not have permission for it.
The same occurs for attributes non-editable or non-visible. There are some fields of the person’s transaction that the customer wants to hide for some users, and there are some fields that cannot be updated by every user. Therefore, the customer requests to configure this at runtime associated to the roles.
In order to achieve this, turn on the following properties in the PersonFirstName attribute:
You should turn on this property for PersonLastName, PersonFullName and PersonGender too.
Tip: You can select more than one attribute at a time and change that property massively.
After you assign the functionality name to the attributes, WorkWithPlus needs to create the structure associated to these assignations in the DataProvider SecGAMGetAdvancedSecurityWWPFunctionalities. In order to do this, you should go to WorkWithPlus Settings, and select the option "Update Security Objects Code":
After making this, the object SecGAMGetAdvancedSecurityWWPFunctionalities is updated with the new functionalities keys.
The, run the application. Log in with the user “admin” and password “admin123” (you can Access to GAMHome in order to configure users and roles). From the GAM Backend add a role named ‘Visitor’. Assign to this role the following permissions of objects (screens):
Log in with this role and verify that you can't visualize PersonFirstName, PersonLastName, PersonFullName and PersonGender.
Log out, and log in again with the admin user and assign to "Visitor", the permissions to PersonFirstName, PersonLastName, PersonFullName and PersonGender. Login with "Visitor" again and verify that you can visualize now PersonFirstName, PersonLastName, PersonFullName and PersonGender.
Well done! You should now be able to:
- Add security to attributes
- Understand the security that WorkWithPlus generates and how it integrates with GAM
|