Action schedule effective start and end dates ignored when using an absolute trigger date
Here's an action schedule that did not go as expected:
Notice how there is an absolute date as the "When (trigger) date" that does not allow you to enter a time and also an "Effective Start Date" that does allow you to enter a time.
In the code we seem to ignore the effective start and end dates when an absolute date is specified.
So, this email was sent at 12:05 am on August 5th instead of 8:05 am on August 5th.
I get it. If you are specifying an absolute start date, why would you need an effective start date?
Well, in this case it's because you are fine-tuning with a time.
I see three options:
- Change the UI so that the effective start and end dates are greyed out if you enter an absolute date. This seems like the easiest to implement.
- Change the code so that we don't ignore the effective start and end date when using an absolute date. I'm not crazy about messing with the Action Schedule code. But, this seems like it could be pulled off without a lot of work or risk.
- Allow setting an absolute date with a time attached to it (and also doing number two). I would rather have a root canal than be responsible for this one. But, it does seem like the best option