Control not moving to 'Attest' state from 'Monitor' state based on the Frequency defined.DescriptionWhen attestation method was attestation earlier, the control attestations were not monitored based on the frequency. Monitoring the control attestations has been enhanced based on the created or updated date. Steps to Reproduce Issue Definition: Control continues in Monitor state and not switching to Attest state as per the defined FrequencySteps to reproduce:.1. Impersonate as Compliance Manager2. Select an active control record that is in Monitor state and set the Frequency to Daily with an assessment that is in Open state.3. Take the assessment.4. After a day from the time of submitting the assessment the control should move from the Monitor to Attest state, which fails to happen.WorkaroundTo address the issue with the smart assessments for control, there is currently no other workaround. Hence, it is recommended to upgrade to version 20.0.4 or above of the GRC: Policy and Compliance Management plugin (ID: sn_compliance) to overcome this issue. Monitoring the control attestations has been enhanced based on the created or updated date with a new property "sn_compliance.attestation_run_reference_date_field". You can configure this property by navigating to Policy and compliance > Administration > properties. In this new version, a new field called Attestation frequency has been added to the control to monitor the attestations. A nightly job will be executed based on the Attestation frequency field on the Control attestations. For existing users, the frequency will be automatically transferred to the Attestation frequency field. To monitor control attestations, use the Attestation frequency field, which is in the Attestation section. Copy entity frequency action copies the attestation frequency of the entity to the control attestation frequency. Note: Frequency field on the control form will be used for control testing or reporting purpose.Related Problem: PRB1815986