Attestations Using smart Assessment Engine

Vedant deshmukh
Tera Contributor

Hello everyone

so I had a question in attestation part of the control 

When we selected the attestation and move the control to attest state the attestation respondent has to  respond to the attestation. 

After he submits the attestation the control goes to review state. 

Once the attestation is submitted its state changes to complete

So after that the control can be either sent to monitor state or it can be sent back to draft state.

So we have a requirement, once the attestation is submitted there should be a Button to send back attestations to the respondent if the answers are found unsatisfactory it should not create a new attestation it should use the existing attestation itself.

Once the attestation is submitted its state changes to close so if the station is send back to attest state the closed attestation should open instead of creating a new attestation record. 

 

I tried this functionality with the help of new smart assessment engine but there also after the attestation is submitted we don't have the option to send back the attestation if the answers are unsatisfactory.

2 REPLIES 2

Phil Swann
Tera Guru
Tera Guru

The workflow for controls is handled by UI actions, so an action to change the state to Attest should suffice.

You can either create a brand new UI action which shows in Monitor, or update the existing UI Action to allow the conditions to include Monitor state (probably this). 

You are not changing the workflow here, so would suggest this is fairly safe and transparent. You are just making the existing workflow more efficient. Otherwise , manually you have to revert to Draft and then click Attest - its the same process and outcome, ultimately. 

Jay Van
Tera Contributor

Hi Vedant, the OOTB design of the attestation closing and not re-open is to trigger downstream functions (change the status of the control to compliant or non-compliant) and create a record for non-repudiation. 

 

If the control passed, and the answer was unsatisfactory, moving the control back to attest shows the activity and keeps a record of the respondent's previous answer for audits and (if the response is satisfactory), the design allows the respondent (smart attestation) to see how they previously answered for the next attestation. 

 

If the control attestation failed by mistake, this raises an issue for the non-compliant control as a result of the failed control attestation. If the same attestation were re-opened and closed as a passed attestation, the issue would still open and tied to the control, creating conflict because the control shows compliant. Worse case if closed again as failed, a second issue for a failed control attestation would be raised!