EdgeVerve / feel

Expression Language for creating and executing business rules in decision table based on DMN 1.1 specification for conformance level 3

EdgeVerve/feel Issues

not(true) seems not to work
Updated 9 months ago1
Decision table execution always return null
Closed a year ago3
No support for string() function
Updated a year ago1
Using results outside of the async
Closed a year ago1
Little bug when we try to nest decimal function
Closed 3 years ago
Realtime Condition/Action Update
Updated 3 years ago1
Add new DMN 1.2 numeric built-in functions
Closed 4 years ago1
Built-in list functions do not allow variable argument lists
Updated 4 years ago2
Unable to apply filter expression to a list literal
Closed 4 years ago3
list indexing should be one-based
Closed 4 years ago1
Empty values in context
Closed 4 years ago1
or list function results in parse error
Closed 4 years ago3
Webpack
Closed 4 years ago2
date("2018-07-31") - duration("P1M") fails
Closed 4 years ago1
date("2012-12-23") >= date("2012-12-24") evaluates to true
Closed 4 years ago1
Subtracting durations from date and time gives wrong year
Closed 4 years ago3
Does FEEL support units (UCUM)?
Closed 4 years ago1
Feature: indicate which rules were used to obtain results
Closed 4 years ago1
1 + 123 / > 3 parsed as valid
Updated 4 years ago3
Cannot parse valid dmn file
Closed 5 years ago1
DMN Technology Compatibility Kit
Updated 6 years ago3
Names in a qualified name are separated by "->" instead of "."
Closed 7 years ago3
1,2,3,4 (list of any type) parsed as error
Closed 7 years ago20
date_and_time isn't working as expected in execute_decision_table
Closed 7 years ago10
"now" equivalent ?
Closed 7 years ago2
"not(>=123,456)" is also parsed as valid
Closed 7 years ago3
<= ( 1 + 2 ) not working
Closed 7 years ago5
1 + 123 / [ 0 .. 3 ] parsed as valid
Closed 7 years ago1