Top of SEC

Index

Table of Contents

Feedback

SECF0033 - Maintain Correspondence Type Security

This form is used to restrict an individual user’s access to data associated with particular Correspondence Types. The purpose is to control access to Correspondence items, Correspondence details and Correspondence job outputs. Access to the functions that use this data is controlled by the security roles granted to the user. This function is used to control access to data within these functions. The form enables the recording of a user’s restricted set of Incoming Correspondence Types. These restrictions are used to control each user’s access to the Incoming Correspondence functionality by specifying the Correspondence Types the user can view and update.

The Person block contains: Person ID Sex Date of Birth The Correspondence Type Restriction block contains: Correspondence Type Description System Generated check box Closed check box Insert check box Update check box Delete check box Restricted Select Allowed check box

Rules/Notes: Validations include: Cannot save the record if the Insert, Update or Delete check boxes are selected and the Restricted Select Allowed isn't. The reverse also applies, that the above check boxes should all be unchecked before saving.

This form is accessed from the Maintain System Users form (SECF0021). The Person block displays previously recorded user details. Query functions cannot be performed in this block. Use this form to restrict access, for an individual user, to data associated with particular correspondence types. The purpose is to control access to correspondence items, correspondence details and correspondence job outputs. (For example, access can be restricted for correspondence type DISCIPLINE to a few authorised users). Access to the functions involved is controlled by the security roles granted to the user. This form is then used to control access to data within those functions. Additional information about the operation of user restrictions, and in particular 'certification' of functions for their use, is contained in Security Restrictions and Access to Data. For a particular correspondence type, if the user's security role would normally permit, then: deselecting the Insert checkbox removes the ability of the user to add data associated with the correspondence type deselecting the Update checkbox removes the ability of the user to modify data associated with the correspondence type deselecting the Delete checkbox removes the ability of the user to delete data associated with the correspondence type Selecting the above checkboxes allows the user to perform the operations. the Restricted Select Allowed checkbox, when selected, permits the user to view only data associated with the correspondence types recorded in this form. When deselected, the user can view data for any correspondence type allowed by their security role(s) but can only perform operations as indicated by the other checkboxes, on data of those correspondence types listed.

Rules/Notes: Restrictions only apply to users with a security role which has the appropriate restriction object registered against it Selecting an Update, Insert or Delete checkbox enables a user to perform that function for the correspondence type. Deselecting a checkbox will stop a user from being able to perform the function. Selecting a Restricted Select Allowed checkbox for any correspondence type restriction record causes the Restricted Select checkboxes for all records to be selected. Inquiry access is then restricted to the correspondence types recorded here. Adding restrictions to a user reduces the access inherited from their security role(s). Access cannot be increased beyond that specified by their security role(s). For example, if the role prevents deletion, setting the delete indicator in this form will not allow the user to delete. A record cannot have all three of Update, Insert, Delete, checkboxes set as this constitutes no restriction of access

Correspondence Type Policies

All the Correspondence Type policies are altered to ensure they are consistent with the Organisational Unit Security policies.

The policy functions:

• Take into account form, report and system self serve application (sssa) restriction overrides
• Utilise the sys_context variables (these define if you are in Callista and what form/report/sssa the user is in)
• All these changes are to ensure the Correspondence Type Restrictions are consistent with the Organisational Unit Restrictions.

Last Modified on 29 June, 2005