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

Missing defaults for RequiredRules and RepetitionRules without condition

    XMLWordPrintable

Details

    Description

      Given

      • A RequiredRule or RepetitionRule is specified
      • No expression is provided

      Then

      • The rule is currently evaluated to "false". But should be true

      Expected behavior

      • if I provide a Require/Repetition Rule without an expression, the rule evaluates to true.

      Context:

      This report is related to the bug-report OMG-12.

      If a required-rule-marker or a repetition-rule-marker is added (without specifying a condition) to a task in Camunda Modeler, the required-rule respectively the repetition-rule should be considered true.

      This would be consistent with the behavior implemented for the Manual Activation Rule in CAM-6362.

      Regarding the required-rule, see also the following corresponding text of the ticket mentioned above:
      "In Table 5.51 (RequiredRule attributes) on page 52 (PDF 68):
      Replace "Expression[1]" with "Expression[0..1]".
      Add the following sentence to the description of the attribute condition:
      "If no Expression is specified, then the default is considered "true.""

      The repetition-rule-marker should behave equivalent to this, see also the following corresponding text of the ticket mentioned above:
      "In Table 5.52 (RepetitionRule attributes) on page 53 (PDF 69):
      Replace "Expression[1]" with "Expression[0..1]".
      Add the following sentence to the description of the attribute condition:
      "If no Expression is specified, then the default is considered "true.""

      mgm-controller-panel

        This is the controller panel for Smart Panels app

        Attachments

          Issue Links

            Activity

              People

                roman.smirnov Roman Smirnov
                tobias.stegemann Tobias Stegemann
                Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved:

                  Salesforce