7.6 Attestation

The Attestation cycle follows the approval cycle and precedes the publication of the object. In the attestation cycle, users associated with the object through the defined RASCI-VS value(s) will receive a pending attestation task. This cycle ensures that all key users are aware of the new changes before they are published.

How to Configure

*Only System Admins can configure the Attestation

1. Navigate to the Advanced settings.
2. Activate the cycle by updating the ENABLE_ATTESTATION field from ‘false’ to ‘true’.
3. By default, the Verifier (V) users will perform the attestation. To change this, modify the RASCIVS_ATTESTATION field to Responsible, Accountable, Support, Consulted, Informed, and/or Signatory.
   • You can use one RASCI-VS value or multiple.
4. Ensure the affected users have ‘Read Latest’ permission on the object since they will attest versions before publication.

The Attestation Workflow

1. When an object is marked as approved, affected users will automatically receive notifications about a pending attestation task.

!Attestation cannot be initiated independently or outside of an approval cycle. If no approval cycle is in place, no attestation task will be triggered.