ASSIGN SECURITY RIGHTS#
Data security is handled using the IMSV function. This is used to control access to subsets of data on the forms and tables. For example, you can restrict by user, which department codes that user can have access to.
When specifying AUTHAREAMATCH in IMSV, ensure that in your value parameter, you have a trailing % (i.e. PW%). Although the People Selection list and some reports will append the % themselves, there are other reports and external access through our secured views do not append the %. As a result, an AUTHAREAMATCH of PW will result in NOTHING being selected.
The definition data for the Assign Security Rights screen is stored in the P2K_AM_SECURITY_VALUES table.
- User
- This field identifies the individual to whom the security right is being assigned.
- Role
- This field identifies the role the security right is being assigned to.
- Security Right
- This field identifies the security right you wish to assign to the user/role. i.e Entity, AuthArea, Group
- Look Up Value
- This field allows the user to select the value the security restriction applies to. The values in the LOV will be derived automatically based on the Security Right selected. For example, if Entity was selected in the Security Right, the Look Up Value will be all of the defined Entities in the application.
- Rule
- This field identifies the rule associated with the security value, for example, 'Restricted To' or 'Restricted From'.
- Security Value
- This field will display the id of the security value selected in the Look Up Value field.
Unless you set the preference RSTRCT_INCL_NULL(System_Preference) to "Y", this means that your users will not be able to see records that have NO value set (NULL) as that is an unknown value which may contravene your security settings.
