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

Execute conditional event dispatching only if conditional events exist in process definition

    • Icon: Task Task
    • Resolution: Fixed
    • Icon: L3 - Default L3 - Default
    • 7.6.0, 7.6.0-alpha6
    • None
    • engine
    • None

      Right now the check will be evaluated every time a variable is set:

      The process definition should contain a flag or property which indicates if a conditional event exist in the process

        This is the controller panel for Smart Panels app

            [CAM-6966] Execute conditional event dispatching only if conditional events exist in process definition

            Christopher Kujawa created issue -
            Christopher Kujawa made changes -
            Rank New: Ranked higher
            Christopher Kujawa made changes -
            Status Original: Open [ 1 ] New: In Progress [ 3 ]
            Christopher Kujawa made changes -
            Status Original: In Progress [ 3 ] New: Open [ 1 ]
            Christopher Kujawa made changes -
            Status Original: Open [ 1 ] New: In Progress [ 3 ]
            Christopher Kujawa made changes -
            Assignee Original: Christopher Kujawa [ christopher.zell ] New: Thorben Lindhauer [ thorben.lindhauer ]
            Resolution New: Fixed [ 1 ]
            Status Original: In Progress [ 3 ] New: Resolved [ 5 ]
            Remaining Estimate New: 0 minutes [ 0 ]
            Original Estimate New: 0 minutes [ 0 ]
            Thorben Lindhauer made changes -
            Issue Type Original: Feature Request [ 2 ] New: Task [ 3 ]

            Thorben Lindhauer added a comment - - edited

            Review feedback:

            • let's pull the check for the property a little bit up. Either to the point where variable events are delayed or to the start point where events are consumed
            • use typed properties
            • remove Corba import
            • test cases: Either write no additional tests (since this is a refactoring, that is ok in our testing approach) or unit test the internal behavior entirely (i.e. on top of testing the property, test that this property is respected when events are delayed)
            • comment "must not be executed" => "need not be executed"

            Thorben Lindhauer added a comment - - edited Review feedback: let's pull the check for the property a little bit up. Either to the point where variable events are delayed or to the start point where events are consumed use typed properties remove Corba import test cases: Either write no additional tests (since this is a refactoring, that is ok in our testing approach) or unit test the internal behavior entirely (i.e. on top of testing the property, test that this property is respected when events are delayed) comment "must not be executed" => "need not be executed"
            Thorben Lindhauer made changes -
            Assignee Original: Thorben Lindhauer [ thorben.lindhauer ] New: Christopher Kujawa [ christopher.zell ]
            Resolution Original: Fixed [ 1 ]
            Status Original: Resolved [ 5 ] New: Reopened [ 4 ]
            Christopher Kujawa made changes -
            Status Original: Reopened [ 4 ] New: In Progress [ 3 ]

              thorben.lindhauer Thorben Lindhauer
              christopher.zell Christopher Kujawa
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: