Control form - Frequency vs Attestation Frequency

[AmeetPatra1]

If populated, does Control form's Frequency field overrides Attestation Frequency which comes from Entity form ?

If not populated, does Attestation Frequency take over?

If I change Attestation Frequency within Control form, provided Control form's Frequency is empty, it does not change the value within Attestation Frequency field present within Entity form. But then how would the execution of the attestation happen.

This is in Xanadu release where we have both Frequency and Attestation Frequency fields within Control Form

#irm #grc #policyandcompliance

[ShafrazMubarak]

In Xanadu release, Servicenow manages attestation scheduling through a hierarchical approach.

The Frequency field on the Control form is designed as the primary driver for attestation scheduling. When populated, this field overrides any Attestation Frequency that might be inherited from the associated Entity record. This means that the specific attestation schedule for that control will be determined solely by the value in the Control's Frequency field.

Conversely, if the Frequency field on the Control form is left empty, the system defaults to using the Attestation Frequency defined on the Entity record. This Attestation Frequency serves as a default, ensuring that the Control inherits its schedule from the broader Entity context.

Critically, changes to the Attestation Frequency field directly on the Control form (while the Frequency field remains empty) do not propagate back to the Entity form. The Entity's Attestation Frequency remains a centrally managed default, and attestation execution will occur based on that Entity-level setting, not a localized change on the Control form.