Uploaded image for project: 'jBPM'
  1. jBPM
  2. JBPM-9097

Case variable: "readonly" tag permits changing value after reopening case

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Minor Minor
    • 7.40.0.Final
    • 7.35.0.Final
    • Runtime Engine
    • None
    • NEW
    • NEW
    • Hide

      As we have the limitation of not being able to start a case with a case file containing a readonly variable, steps are the following:
      1.- startCase without the readonly variable
      2.- cancelCase, add the readonly variable to the data and reopening it passing the updated caseFile
      3.- Repeat step 2.
      Expected exception isn't thrown.

      Show
      As we have the limitation of not being able to start a case with a case file containing a readonly variable, steps are the following: 1.- startCase without the readonly variable 2.- cancelCase, add the readonly variable to the data and reopening it passing the updated caseFile 3.- Repeat step 2. Expected exception isn't thrown.
    • 2020 Week 22-24 (from May 25), 2020 Week 25-27 (from Jun 15)

      After cancelling a case, a variable tagged as "readonly" is added again in the case file with a different value when reopening the case. A VariableViolationException is expected, as these variables are not allowed to be set more than once, but it isn't thrown, changing its value and ignoring the restriction.

      Notice that currently for adding "readonly" variables when starting the case, it's not possible if the value is added through newCaseFileInstance, as when creating the case file with that variable, is considered as first assignation of the value and therefore it cannot be modified at startCase. This is also a weird behavior as makes "readonly" variables useless when starting the case.

              ftirados Francisco Javier Tirado Sarti
              gmunozfe@redhat.com Gonzalo Muñoz Fernández
              Gonzalo Muñoz Fernández Gonzalo Muñoz Fernández
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: