Unable to validate date and time ranges in decision table conditions. All attempted syntaxes for date/time comparison fail to match rules, while simple string matching (day codes) and numeric ranges (quantity) work correctly.
Expected Behavior
Decision table should support date and time range validation similar to how it supports numeric ranges, allowing rules like:
Date range: >= date('2025-01-01') && <= date('2025-12-31')
Time range: >= time('09:00') && <= time('18:00')
Current Behavior
✅ Works: Numeric ranges [1..100], string matching "MON","TUE","WED"
❌ Fails: Date ranges, time ranges with any syntax attempted
Tested Syntaxes (All Failed)
Range notation: [2025-01-01..2025-12-31] and ["09:00".."18:00"]
Comparison with AND: >= "2025-01-01" && <= "2025-12-31"
Function wrappers: >= date('2025-01-01') && <= date('2025-12-31')
Placeholders: date(?) >= date("2025-01-01") and date(@) >= date("2025-01-01")
Unable to validate date and time ranges in decision table conditions. All attempted syntaxes for date/time comparison fail to match rules, while simple string matching (day codes) and numeric ranges (quantity) work correctly.
Expected Behavior
Decision table should support date and time range validation similar to how it supports numeric ranges, allowing rules like:
Date range: >= date('2025-01-01') && <= date('2025-12-31')
Time range: >= time('09:00') && <= time('18:00')
Current Behavior
✅ Works: Numeric ranges [1..100], string matching "MON","TUE","WED"
❌ Fails: Date ranges, time ranges with any syntax attempted
Tested Syntaxes (All Failed)
Range notation: [2025-01-01..2025-12-31] and ["09:00".."18:00"]
Comparison with AND: >= "2025-01-01" && <= "2025-12-31"
Function wrappers: >= date('2025-01-01') && <= date('2025-12-31')
Placeholders: date(?) >= date("2025-01-01") and date(@) >= date("2025-01-01")