Uploaded image for project: 'camunda BPM'
  1. camunda BPM
  2. CAM-11319

In FEEL Scala Engine, I can compare POJOs with > < = operators

    XMLWordPrintable

Details

    • Feature Request
    • Resolution: Won't Fix
    • L3 - Default
    • None
    • None
    • None
    • None

    Description

       This is a breaking change; The legacy FEEL Engine can compare Java objects in case the Comparable interface was implemented

      Steps to reproduce

      1. Use a pojo variable as input expression
      2. Use the pojo variable in the input rule (implicit equals)

      Observed behavior
      I see the following exception:

      16:35:38.734 [main] ERROR org.camunda.bpm.engine.context - ENGINE-16004 Exception while closing command context: failed to evaluate expression 'pojo': expected Number, Boolean, String, Date, Time or Duration but found 'ValContext(CacheContext(ObjectContext(TestPojo{foo='okay', bar=13.37})))'
org.camunda.bpm.dmn.feel.impl.FeelException: failed to evaluate expression 'pojo': expected Number, Boolean, String, Date, Time or Duration but found 'ValContext(CacheContext(ObjectContext(TestPojo{foo='okay', bar=13.37})))'

      Expected behavior
      Pojos can be compared.

      mgm-controller-panel

        This is the controller panel for Smart Panels app

        Attachments

          Issue Links

            causes

            Feature Request - A new feature of the product, which has yet to be developed. CAM-12067 In FEEL Scala Engine, I can use Joda Date/Time typed variables

            • L3 - Default - Minor issue or issue with existing workaround, feature requests and questions
            • Closed
            depends on

            Feature Request - A new feature of the product, which has yet to be developed. CAM-11184 Add support for full FEEL 1.2 feature set

            • L3 - Default - Minor issue or issue with existing workaround, feature requests and questions
            • Closed
            is related to

            Sub-task - The sub-task of the issue CAM-11282 Identify breaking changes due to different type handling

            • L3 - Default - Minor issue or issue with existing workaround, feature requests and questions
            • Closed

            Activity

              People

                tassilo.weidner Tassilo Weidner
                tassilo.weidner Tassilo Weidner
                Votes:
                1 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved:

                  Salesforce