UI Policy on GRC Attestation Form

trmiller
Kilo Expert

I am trying to figure out how to make a couple fields not mandatory based on another question's answer. Using the Attestation Designer, I can make the fields visible or not. In our case, we want "Explain" and "Attach evidence" to be visible, but not required when "Is the control implemented" = No. If yes, the 2 fields can be mandatory. Usually I would do a UI policy, but cannot figure out how on an attestation form.

find_real_file.png

1 ACCEPTED SOLUTION

Chris Smith4
Mega Guru

I'm not aware of a way to set up UI Policies for attestations like this. But you can set up the desired record form using the following:

 

  1. In the Attestation Designer, create duplicates of the [Explain] and [Attach evidence] fields
    • Have the Question text be the same for the duplicate fields, but have the names be unique for maintenance purposes (example-- Name: 'Explain (yes)', 'Explain (no)', 'Attach Evidence (yes)', 'Attach Evidence (no)').
  2. Make the 'Explain (yes)' and 'Attach evidence (yes)' fields dependent on : Is the control implemented? = Yes
    • Make these two fields Mandatory
  3. Make the 'Explain (no)' and 'Attach evidence (no)' fields dependent on : Is the control implemented? = No
    • Leave these two fields NOT Mandatory

 

Now when the user takes the attestation, they will see only one set of Explain and Attach evidence fields regardless of their response, but these two fields will only be mandatory if they respond "Yes" to the control being implemented.

 

Implemented = Yes:

find_real_file.png

 

Implemented = No:

find_real_file.png

 

Hope this helps!

Chris

View solution in original post

5 REPLIES 5

Chris Smith4
Mega Guru

I'm not aware of a way to set up UI Policies for attestations like this. But you can set up the desired record form using the following:

 

  1. In the Attestation Designer, create duplicates of the [Explain] and [Attach evidence] fields
    • Have the Question text be the same for the duplicate fields, but have the names be unique for maintenance purposes (example-- Name: 'Explain (yes)', 'Explain (no)', 'Attach Evidence (yes)', 'Attach Evidence (no)').
  2. Make the 'Explain (yes)' and 'Attach evidence (yes)' fields dependent on : Is the control implemented? = Yes
    • Make these two fields Mandatory
  3. Make the 'Explain (no)' and 'Attach evidence (no)' fields dependent on : Is the control implemented? = No
    • Leave these two fields NOT Mandatory

 

Now when the user takes the attestation, they will see only one set of Explain and Attach evidence fields regardless of their response, but these two fields will only be mandatory if they respond "Yes" to the control being implemented.

 

Implemented = Yes:

find_real_file.png

 

Implemented = No:

find_real_file.png

 

Hope this helps!

Chris

Thanks Chris. This was my first guess to solve for as well, but thought there might be a better way instead of having the overhead of the extra fields. Thanks for chiming in!

uma17
Tera Guru

Hi ,

The Attestation Designer button is not coming up on my instance , any idea why ? It s owkring good in my PDI but in the actual instance its not working

 

Thanks

Uma

Hi Uma,

Are you a user in your instance or a System Administrator?

If you're a user, you might just need to request that the sn_compliance.attestation_creator role be added to your account. Its a separate role not inherited by the sn_compliance.user or sn_compliance.manager roles.

If you're an Admin, the first thing I'd check when troubleshooting UI Actions is the [Condition] field on the UI Action record associated with the button you're looking for. 

find_real_file.png

 

Hope this helps!

Chris