Need help debugging changes in the approval field

[peterraeves]

We have the situation where changing the problem.approval field to Requested, it sets all Approval records back to 'Requested'. I tried this on an OOTB instance and noticed it did not happen there. We would like to modify the modification, but I cannot locate the change... In a desperate attempt, I have deactivated all Business Rules and all Client Scripts on Problem and Task and it stills happens. I have checked the workflow context and there were none. Where should I search next? What else could modify the sysapproval record like this...

[Chuck Tomasi]

Hi Peter.

You're on the right track. Have you tried using the field watcher to see if you can track down anything?

Field Watcher

[peterraeves]

Why haven't I used the field watcher before... This is so useful...

Though I'm not there yet. The output is as follows, but I cannot seem to locate where the code is for 'com.glide.policy.ApprovalActionHandler' or which Save button it is that is used.

14:22:41 (566)SCRIPT ENGINE - com.glide.policy.ApprovalActionHandlerApproved → Requested

→ REQUEST ACTION - Save

→ → UI ACTION - Save

→ → → SCRIPT ENGINE - com.glide.policy.ApprovalActionHandler

[sndangibbard · Accepted solution]

If this is not being managed by Business Rules or Workflows then it may be from Approval Rules.

System Properties > Approval Engines will show you how approvals on various tables are managed. If the Problem or Task tables shows 'Approval Rules' then you can manage these through System Policy > Rules > Approval

From your debug output above this looks like it might be the case!

[peterraeves]

The Problem (and Task) table uses 'Approval Rules' indeed, though in the approval rules table, there are no records for both the problem as task table