Property patterns for date are currently barely usable. You can define that the value must be:
- One of the following values only
- Must not contains the following values
I can't thing of any real use case for such condition with fields like accountExpires & the likes; enumerating valid options is nearly impossible and suboptimal. It would be in my opinion way better to have comparison based conditions like:
- AccountExpires cannot exceed %datetime%+3
- AccountExpires cannot be before %datetime%
We are currently doing those checks using a business rules, but it would look cleaner if the property pattern could handle that natively.