"Less than or equal to Rule Date" excluding records from today seems like unexpected behavior from the user's perspective.
For filters on a DateTime field, it would be nice if we were able to either:
1) Have an option to tell the rules engine to treat the value as a Date. From a SOQL perspective, possibly using the DAY_ONLY() function detailed
here.
or 2) Have an extra parameter to choose the time we want to filter against. So in Rob's example, he could say "Created Date <= Rule Date, 24:00".
This is extremely important, can someone please review.
Still open.
Hey Rob - Was thinking of removing the option of Equals & Not Equals when a date time field is selected. Is that sane?
That would be a place to start, but we also need to make less than or equal to function correctly (equate to the last second of the day rather than the first).
Is there an update on this?
Sundar - Let's add this to our top list for Rules Engine and Reports filtering changes as this has been a challenge for a long time (and still causing escalations and loss of confidence with customers). The services team is doing workarounds in MDA (creating truncated date only fields to avoid this confusion) that is completely solvable within our product
Discussed with Sundar and Murthy. Proposal is to address this - pending timing confirmation from Sundar this week (week of 10/31) and may be able to include in a patch.
What is the proposed fix? There are hundreds of rules built off of DateTime fields that I am sure have been configured "incorrectly" in an effort to circumvent this issue.
Thanks for the heads up Rob. My guess is end of Nov or First week of Dec.
What breaks now?
Rule is scheduled to run at 09:00 AM. There is a filter condition for Created DateTime > (Subtract 1 day from Rule date) AND Created Date <= Rule date. This filters the data that is created b/w 09:01 AM previous day and 9:00 AM of Today (Rule date)
Proposed Fix : Honor simple english
Created date < Rule date 12:00AM
Created date >= Rule date 12:00 AM
Created date > Rule date 11:59 PM
Created date <= Rule date 11:59 PM
Also operate in the timezone that is set in Rules Engine.
Makes sense, thanks Sundar.
I think that most of the rules will still work, but I know there are situations where people, rather than doing less than or equal to Rule Date -1, would do less than Rule Date to avoid the bug. I think these scenarios will still function correctly with your proposed fix. I will brainstorm to see if I can think of any edge cases that might not port over correctly.
Hi Everyone - I've made this post public now to get the opinion from Rules Engine Admins.
A subtle issue with Rule date which is actually working as dateTime instead of just date and also taking the scheduled time for the time component instead of Start / End of day. Proposed fix is explained in my comment above, let me know if this approach breaks anywhere.
This is the comment Sundar is referring to that describes the proposed logic.
With Timezone standardisation in place, this problem is solved and these changes are part of SFDC 5.6 release.
