7.6 Attestation

The Attestation cycle occurs after the approval cycle and before the object is published. During this stage, users assigned to the object based on their RASCI-VS role(s) receive a pending attestation task. This ensures that key users review changes before publication.

This guide explains how to:

• Configure the attestation cycle
• Assign RASCI-VS roles for attestation
• Complete the attestation workflow
  

Configuring the Attestation Cycle

*Only System Admins can configure attestation settings.

1. Navigate to the Advanced settings.
2. Locate the ENABLE_ATTESTATION field and change its value from ‘false’ to ‘true’ to activate the cycle.
3. By default, users with the verifier role perform attestations. To modify this, update the RASCIVS_ATTESTATION field to include one or more of the following roles:
   • Responsible
   • Accountable
   • Support
   • Consulted
   • Informed
   • Signatory
4. Ensure the affected users have ‘Read Latest’ permission on the object as they will attest to versions before publication.

Attestation Workflow

When an object is approved, the assigned users will receive an EPC notification and an email about the pending attestation task.

To complete the attestation task:

1. Open the object requiring attestation.
2. Locate the Pending Attestation action box.
3. Add a comment (optional).
4. Click Attest to confirm.
   

Once all assigned users have completed attestation, the user who submitted the object for approval will be notified that it is ready for publication.

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