What is the purpose of "Accept End Date" in an "Acceptance Risk Response Task"

[Kiara3]

Hello Experts,

We are currently working no 'Risk Management' Application in GRC Universe.

When user selects 'Accept' as the Response on the Risk Register, then an "Acceptance Risk Response Task" is generated. This task has a field called "Acceptance End Date".

Could anyone please explain what exactly is the functionality behind this Date field ?

Thanks.

[Community Alums]

Based on available App Files, the following was confirmed:
1) only future dates are allowed as valid acceptance end dates.
2) once a risk response task is closed (includes risk acceptance) all relevant fields get mapped to the parent Risk, which includes Acceptance end date for Risk Acceptance response tasks.
3) once this is done, a daily Scheduled Script Execution runs to check if any Risk has a past Acceptance end date and, if so, clears any acceptance related data and moves the Risk back to Draft so the Owners can manage it again.
4) finally, a Notification gets also sent out to the Risk Owner.

Supporting App Files:

• Scheduled Script Execution
  Risk acceptance exceeded: https://INSTANCE_NAME.service-now.com/nav_to.do?uri=sysauto_script.do?sys_id=77e3e45ac32003002a48db1...
• Business Rule
  Close task and copy info when monitor: https://INSTANCE_NAME.service-now.com/nav_to.do?uri=sys_script.do?sys_id=998c111ed7200300bbc783e80e6...
• Business Rule
  Copy task info when moves to review: https://INSTANCE_NAME.service-now.com/nav_to.do?uri=sys_script.do?sys_id=5f3b9e1eb7220010ec95dd78ee1...
• Business Rule
  Validate acceptance end date field: https://INSTANCE_NAME.service-now.com/nav_to.do?uri=sys_script.do?sys_id=621f307853212010ad9bddeeff7...
• >> Notification
  Risk acceptance exceeded: https://INSTANCE_NAME.service-now.com/nav_to.do?uri=sysevent_email_action.do?sys_id=45fa5452c3200300... 

[nikhil88c]

In the classic Risk Management process, I see the following OOTB components handling acceptance expiry:

• Scheduled Script Execution: Risk acceptance exceeded – checks if Acceptance End Date has passed, clears acceptance-related data, and moves the Risk back to Draft.
• Business Rules: Close task and copy info when monitor, Copy task info when moves to review, Validate acceptance end date field.
• Notification: Risk acceptance exceeded – alerts the Risk Owner when acceptance period ends.

This works as expected for classic risk. My question:

• Does the same logic (Scheduled Script Execution + BRs + Notification) apply when using Advanced Risk Assessment methodology?
• Or are there different OOTB scripts/flows for Advanced Risk that handle moving the Risk back to Draft (or Assess) after the Acceptance End Date expires?
• If different, could you point me to the relevant flows or scheduled jobs for Advanced Risk?

Thanks in advance for clarifying!