|QER\Attestation\AutoCloseInactivePerson||If this configuration parameter is set, pending attestation cases for an employee are closed, when this employees is permanently deactivated.|
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.
|TIP: Write a corresponding condition for finding the attestation object on the attestation policies to prevent attestation cases being created for deactivated employees. For more information, see General Master Data for Attestation Policies.|
|Common\ProcessState\PropertyLog||When this configuration parameter is set, changes to individual values are logged and shown in the process view.|
The table AttestationCase expands very quickly when attestation is performed regularly. To limit the number of attestation cases in the One Identity Manager, 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 detailed 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 detailed information about the archiving process, see the One Identity Manager Data Archiving Administration Guide.|
To delete attestation cases automatically
Opens the Schema Editor.
These changes become effective the moment the DBQueue Processor has processed the tasks.
|TIP: If you want to prevent attestation cases being deleted for certain attestation policies, enter the value 0 for the obsolete task limit for this attestation policy.|
Attestation cases are deleted once
- OR -
The 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:
All columns are recorded, which are marked for logging on deletion.
The same number of attestation cases remain in the database as are specified in the obsolete tasks limit.
|NOTE: Closed attestation cases are are also deleted in the case of disabled attestation policies if the configuration parameter "Common\ProcessState\PropertyLog" is not set. In this case, the deleted attestation cases are not logged.|
|QER\Attestation\DefaultSenderAddress||This configuration parameter contains the sender email address for automatically generated messages during attestation.|
Messages are not sent ti 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
When a new attestation case is made, the attestor is notified by mail. Demands for attestation can be configured separately for each approval step.
To set up the notification procedure
|Mail template for demand||Select the mail template "|
|NOTE: You can schedule demands for |