Why are controls not created in attest state when created through a control objective?

[Sujan Reddy1]

Could someone explain why controls that got created through a control objective are in draft state to the contrary of what's mentioned in product documentation.

https://docs.servicenow.com/en-US/bundle/utah-governance-risk-compliance/page/product/grc-policy-and...

[Community Alums]

Hi @Sujan Reddy1 ,

When the Controls are created through Control Objectives, it would be in "Draft" state itself by design and it's mentioned correctly in doc as well.

Because , these controls are just created but they are not sending any attestations to the control/entity owner so it's in "Draft" state. Once you send the attestations to the control/entity owner, then that particular control moves into "Attest" state.

[Sujan Reddy1]

Hi @Community Alums  :

Thanks for your reply, But if you see the screenshot I've added , it says "when a control is created from a control objective, controls are in this(attest) state" I wonder what it means in this context.