-
Feature Request
-
Resolution: Fixed
-
L3 - Default
-
None
-
None
- Based on scala engine
AT
I can...
- ...use FEEL in the following DMN Notation Elements...
- ...Input Expression
- ...Input Entries
- ...Output Entires
- ...Literal Expression
- ...register Custom Functions
- ...handle SPIN-based JSON & XML variables
- ...restore the legacy FEEL behavior
This is the controller panel for Smart Panels app
- causes
-
CAM-11269 In Scala FEEL Engine, unary-test comparison without braces cannot be evaluated
- Closed
-
CAM-11304 In Scala FEEL Engine, number comparison does not work for type short
- Closed
-
CAM-11382 In Scala FEEL Engine, max double & max-float cannot be handled
- Closed
-
CAM-11365 Scala FEEL Engine cannot be used with IBM Java 8 SDK Build pxa6480-20150129_02
- Closed
- is depended on by
-
CAM-11261 In the DMN Engine, I can enable the FEEL legacy flag per decision definition
- Open
-
CAM-11288 Support FEEL Scala Engine as integrated Script Engine
- Open
-
CAM-11286 In DMN Engine, introduce type references for Joda and Java 8 date types
- Closed
-
CAM-11319 In FEEL Scala Engine, I can compare POJOs with > < = operators
- Closed
-
CAM-11433 In FEEL Scala Engine, beans are automatically looked-up & resolved
- Closed
-
CAM-11515 In FEEL Scala Engine, display more expressive error message when using single-quoted string literals
- Open
-
CAM-11446 FEEL Scala Engine integration artifact is minimized
- Closed
-
CAM-11745 Documentation of FEEL Scala Engine is versioned
- Closed
- is related to
-
CAM-11329 In Scala FEEL Engine, non-community CI is used
- Closed
-
CAM-10402 Spike on official Support of Camunda Scala DMN and FEEL engines
- Closed
- links to