I have a situation where currently the request is to force end users to take a new risk assessment if they modify things like impact, start_date, and end_date. I feel like best practice would be to make these fields read only at the time of approvals to prevent users from getting x amount of approvals and then modifying the variables previously agreed to; however I had push back with this mindset.
I currently tried to keep it simple and use the risk value and reset it to trigger a previously created BR that aborts action if risk = none. I could not find what additional variables I needed to modify or documentation on it, but the field remained unchanged with my attempts.
Now I am trying to check against the asmt_assessment_instance table to see if an assessment is present, then delete it to allow a reset. I then realized I need to clear out the question related records prior as their is dependency protection blocking deletion and am trying to query through the 'asmt_assessment_instance_question' table using this table's 'instance' value against the initial core assessment table's 'number' value. I am producing results, but failing to loop through deleting each variable record and this approach honestly is starting to feel terrible and I am hoping there are many better suggestions out there.
