Hi,
Thanks for reporting this issue. I have already fixed it in v4.101, but have a few other small things I hoped to get into this release. I will publish it within a few days.
Let me know if this bug is a show-stopper for you – I could publish a fix for this specific issue.
When do you think you will be releasing 4.101 front end to fix the date issue? Also, is it possible to use [today] in the trigger? Date1 greater than [today]-90 for example? If not can a calculated column be used date1 greater than {fieldinternalname}? Thank you as always!