DMN Decision Table Date related collection functions #2788
Assignees
Comments
tijsrademakers
pushed a commit
that referenced
this issue
Feb 17, 2021
rgorzkowski
pushed a commit
to Stepwisepl/flowable-engine
that referenced
this issue
May 3, 2021
* flowable#2788 fixes issue when using Date input variables and collection operations in DMN decision tables * flowable#2788 added java.time.LocalDate to input variable pre processing (DMN decision table execution)
|
i was using the decision table collection all of its not working properly i will ping screen shot to u |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When using a Date input variable in the DMN decision table and creating a rule use collection related operators an exception can occur while executing the decision table.
This is should not be the case.
There is transformation logic in place which can instantiate collection during runtime based on the strings in the rule expression. This provides the flexibility to create collections with string literals in the decision table editor.
In the current transformation logic the case of using a Date object is not covered. It always tries to convert based on the
.toStringvalue. This is incorrect and should be fixed.The text was updated successfully, but these errors were encountered: