A VERY PECULIAR PROBLEM
Customer of mine recently complained that the Decision table was malfunctioning. Decisions have 3 states OOB: Pending, Approved, Rejected. When user was setting Decisions to Approved, they were automatically becoming rejected. Tried it on my instance to the same result.
Taking a closer look, whatever causes the issue happens before insert, because the Decision ever made it to Approved.
Using the "Watch Field" feature, I was able to find out what business rule was causing trouble.
THE PROBLEM REVEALED
The rule causing the state to switch was Task Closer, and I recommend everyone with an instance a few years old to look at it. It looks like an older version of this rule has got a newer updated date, and either avoids being modernized or overwrites modernized versions. I'm not sure which, but it makes a huge difference. Observe:
VERSION CAUSING BREAKAGE
VERSION FROM CLEAN INSTANCE, SAME PATCH LEVEL
The clean version is CLEARLY the most modern, but its Updated date is earlier. Also, in each case the business rule was deployed by the same package name, but different sys_id's in each case:
This leads me to believe anyone who's deployed the older ServiceManagement option packs (old school HR, Finance, Legal, etc) may have deployed a pre-requisite that conducts hoopla to fill this rule with tomfoolery.
TL;DR
If you've got an old instance, and you intend on deploying ITBM, make sure your Task Closer rule is clean *intended* version, not the older busted version with the newer Updated date.
