Closing attestation cases for deactivated employees
Pending attestation cases must still be processed even if they have permanently deactivated in the meantime. This is not required very often because the affected employee may have, for example, left the company. In this case, you can use the option to close an employee's pending attestation cases automatically, if the employee is permanently disabled.
To close attestation cases automatically
The configuration parameter only applies if the employee to be attested is deactivated after the attestation case was created.
The configuration parameter does not apply if the employee is temporarily deactivated.
Deleting attestation cases
The AttestationCase table expands very quickly when attestation is performed regularly. To limit the number of attestation cases in the One Identity Manager database, you can delete obsolete, closed attestation cases from the database. The attestation case properties are logged and then the attestation cases are deleted. The same number of attestation cases remain in the database as are specified in the attestation policy. For more information about logging data changes tags, see the One Identity Manager Configuration Guide.
NOTE: Ensure that the logged request procedures are archived for audit reasons. For more information about the archiving process, see the One Identity Manager Data Archiving Administration Guide.
Prerequisites
To delete attestation cases automatically
-
Set the Log changes when deleting option on at least three columns in the AttestationCase table.
-
In the Designer, select the Database schema > Tables > AttestationCase category.
-
Select the Show table definition task.
This opens the Schema Editor.
-
Select a column in the Schema Editor.
-
In the edit view of the schema editor, select the More tab.
-
Set the option Log changes when deleting.
-
Repeat steps (c) to (e) for all columns that are to be recorded on deletion. There must be at least three.
-
Click on Commit to database and save the changes.
The changes take effect as soon as the DBQueue Processor has performed the calculation tasks.
-
Set the Log changes when deleting option on at least three columns in the AttestationHistory table.
-
In the Designer, select the Database schema > Tables > AttestationHistory category.
-
Repeat the steps 1(b) to 1(h) for the AttestationHistory table.
-
Enter the number of obsolete cases in the attestation policies.
-
In the Manager, select the Attestation > Attestation policies category.
-
Select the attestation policy in the result list whose attestation cases should be deleted.
-
Select the Change main data task.
-
In the Obsolete tasks limit field, enter a value greater than 0.
- Save the changes.
TIP: If you want to prevent attestation cases being deleted for certain attestation policies, enter the value 0 for the obsolete task limit for these attestation policies.
Attestation cases are deleted as soon as a new attestation is started for an attestation policy.
One Identity Manager tests how many closed attestation cases exists in the database for each attestation object of this attestation policy. If the number is more than the number of obsolete attestation cases:
-
The attestation case properties and their approval sequence are recorded.
All columns are recorded, which are marked for logging on deletion.
-
The attestation cases are deleted.
The same number of attestation cases remain in the database as are specified in the obsolete tasks limit.
If the Common | ProcessState | PropertyLog configuration parameter is deactivated later or not enough columns are marked with the Record on delete option, the value for Number of obsolete processes has no effect.
Notes for disabling attestation policies
-
Disabling an attestation policy always deletes all attestation cases.
-
The number of obsolete cases is not taken into account.
-
The attestation case are also deleted if the Common | ProcessState | PropertyLog configuration parameter is disabled. In this case, the deleted attestation cases are not logged.
Related topics
Notifications in the attestation process
In an attestation process, various email notifications can be sent to attestors and other employees. The notification procedure uses mail templates to create notifications. The mail text in a mail template is defined in several languages. This ensures that the language of the recipient is taken into account when the email is generated. Mail templates are supplied in the default installation with which you can configure the notification procedure.
Messages are not sent to the chief approval team by default. Fallback approvers are only notified if not enough approvers could be found for an approval step.
To use notification in the request process
-
Ensure that the email notification system is configured in One Identity Manager. For more information, see the One Identity Manager Installation Guide.
-
In the Designer, set the QER | Attestation | DefaultSenderAddress configuration parameter and enter the sender address used to send the email notifications.
-
Ensure that all employees have a default email address. Notifications are sent to this address. For more information, see the One Identity Manager Identity Management Base Module Administration Guide.
-
Ensure that a language can be determined for all employees. Only then can they receive email notifications in their own language. For more information, see the One Identity Manager Identity Management Base Module Administration Guide.
-
Configure the notification procedure.
Related topics
Requesting attestation
When a new attestation case is made, the attestor is notified by mail. Requests for attestation can be configured separately for each approval step.
Prerequisite
To set up the notification procedure
-
On the Mail templates tab of the approval step, enter the following data:
Mail template request: Attestation - approval required
TIP: To allow approval by email, select the Attestation - approval required (by email) mail template.
NOTE: You can schedule requests for attestation to send a general notification if there are attestations pending. This replaces single requests for attestation at each approval step.
Related topics
