Why is control state changed back to draft when control objective data are updated ?

[Natacha Rasson1]

Hello,

When I update the data in a control objective (eg reference), the controls linked to this control objective is set back to "draft" state. 

Could you explain why ? What is the reason behind ?

[Sulabh Garg]

Hi Natacha,

You might be updating the 'Attestation' field on control objective and as per OOB functionality if you have updated the control objective's attestation field then all controls under that control objective has to use the same attestation.

This is the reason all controls moved back to "Draft" state so that new attestation to be performed again on the controls.

Please see below screenshot

Please Mark ✅ Correct/helpful, if applicable, Thanks!! 
Regards
Sulabh Garg

[Natacha Rasson1]

Hello,

Thank you for your answer.

Still, a change in the reference is setting all ctrl's at "draft".
Isn't it a bit too much ?

In your example, it makes perfect sense.
But I do not see the added value of the mechanism for a change in the reference of the CO.

Regards

[Srinivasulu Lag]

Hi Natacha,

Are you seeing this behaviour from OOB? If yes, please provide us the repro steps along with following information. 
From which family release this issue is occurring?
Which version of P&C we are using?
List of GRC plugin names which are installed?

Thanks,

Srinivasulu Laggala

[Sulabh Garg · Accepted solution]

Hi Natacha,

Yes, This is the OOB functionality and there is a Business rule "Cascade Changes" on control objective table which trigger this logic.

You may change the logic in the business rule (which is not recommended) to achieve your requirement.

Please Mark ✅ Correct/helpful, if applicable, Thanks!! 
Regards
Sulabh Garg