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

I can use variables in on parts for sentries

XMLWordPrintable

    • Icon: Feature Request Feature Request
    • Resolution: Fixed
    • Icon: L3 - Default L3 - Default
    • 7.6.0, 7.6.0-alpha3
    • None
    • engine

      The CMMN specification defines PlanItemOnParts (already implemented).
      The specification also defines "CaseFileItemOnParts" which refer to "case files" which are not implemented by our java engine since we use the more poverful and flexible model of variables.
      Still it should be possible to define a counterpart to the "CaseFileItemOnParts" which reacts changes of the variables.

      Related forum post:
      https://groups.google.com/forum/#!topic/camunda-bpm-users/d9uNMf54aOU

        This is the controller panel for Smart Panels app

            [CAM-4225] I can use variables in on parts for sentries

            Daniel Meyer added a comment - - edited

            Events (plan item lifecycle transitions, variable lifecycle) can happen before a sentry listens for them. We need to define the behavior for such situations.

            • Find out whether Sentries are currently implemented in a way that they can cope with such situations
              [Answer]: With the current implementation, sentries cannot listen for plan item or variable lifecycle transitions that has happened before the respective sentry is created.
            • Find out what the Specification says about this. (for planItemOnPart, and caseFileItemOnPart)
              [CMMN1.1 Spec]: Entry criterion sentries are considered ready for evaluation while the task, stage, or milestone is in Available state. Sentries are evaluated when events arrive to the system or when events are generated by the system.

            Daniel Meyer added a comment - - edited Events (plan item lifecycle transitions, variable lifecycle) can happen before a sentry listens for them. We need to define the behavior for such situations. Find out whether Sentries are currently implemented in a way that they can cope with such situations [Answer] : With the current implementation, sentries cannot listen for plan item or variable lifecycle transitions that has happened before the respective sentry is created. Find out what the Specification says about this. (for planItemOnPart, and caseFileItemOnPart) [CMMN1.1 Spec] : Entry criterion sentries are considered ready for evaluation while the task, stage, or milestone is in Available state. Sentries are evaluated when events arrive to the system or when events are generated by the system.

            Daniel Meyer added a comment -

            First increment:

            • Single Task with sentry having variableOnPart (create)
            • Scenario:
              • Start Case
              • Set the variable
              • Expected: task is enabled

            Daniel Meyer added a comment - First increment: Single Task with sentry having variableOnPart (create) Scenario: Start Case Set the variable Expected: task is enabled

            Daniel Meyer added a comment - - edited

            TODO: understand first increment and break it down into issues that can be done in 1-2 days

            Daniel Meyer added a comment - - edited TODO: understand first increment and break it down into issues that can be done in 1-2 days

              deivarayan.azhagappan Deivarayan
              thorben.lindhauer Thorben Lindhauer
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: