How does the field "Inherit from Control Objective" field on Control record work?

[Khang1]

We just recently upgrade our GRC modules and notice that "Control Objective" field is now mandatory, even for our ad-hoc controls that doesn't tie to any Control Objective (CO). Per further investigation, we noted a UI Policy on Control record that make CO field mandatory if the "Inherit from Control Objective" is marked 'true'

For some reason all of our controls have this as 'true' and I cannot update the field, even with admin access. Can someone advise on how we can update the field, "Inherit from Control Objective", on the Control form?

Thank you!

[Community Alums]

Hi @Khang1 

Let's understand the use case , let's say on your control objective ," create controls automatically" is checked, this would mean that, the controls would be created automatically as per the entity type, so the controls which got generated , you would see the control automatically inherits the name and description of the control objective.

However, if you are creating a adhoc control and you will have to the option to check or uncheck the box of "Inherit from control objective" .  Now, if you see that "Inherit from control objective" is true by default and read only after associating a Control objective in the control form, that means at the CO level, then "create controls automatically" is checked and it got inherited to Control as well.

You will need to make the UI policy active "false". check if the associated CO has "create controls automatically" is true or false, if true then mark it false, then you can create the control.

Inherit from control objective : Option to indicate whether the control is created through item generation process. For more information, see Multiple controls for a unique entity–control objective combination.