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

Tasklist does not submit form field with default value if variable has already that value

    XMLWordPrintable

Details

    • Bug Report
    • Resolution: Fixed
    • L3 - Default
    • 7.12.0, 7.10.9, 7.11.3, 7.12.0-alpha3
    • 7.11.1, 7.12.0-alpha2
    • tasklist
    • camunda-bpm-ee-tomcat-7.11.1-ee

    Description

      Scenario:

      • A task with a generated form
      • The form has one form field that has a default value x
      • The variable exists already in the process instance with value y

      Action:

      • I enter x in the form field and submit the form

      Current behavior:

      • Variable value x is not submitted with the form; the backend changes the variable value to the default value x

      Expected behavior:

      • Variable value x is submitted to avoid the backend overriding the variable value

      What are the steps to reproduce your problem?

      1. Deploy attached example.bpmn
      2. Start a new process instance
      3. Complete the user task form with a value of 6
      4. Complete the new user task with the same value of 6

      What is the problem?
      The form payload is the correct one the first time ->
      but empty the second one -> .
      The result is that the variable value changes to its default one (2) -> .

      What would be the expected behavior:
      The form payload of the 2nd try is the same and the variable value is set to 6

      mgm-controller-panel

        This is the controller panel for Smart Panels app

        Attachments

          1. after 2nd try.png
            80 kB
            Ilias
          2. after first try.png
            128 kB
            Ilias
          3. example.bpmn
            2 kB
            Ilias
          4. first try.png
            146 kB
            Ilias
          5. second try.png
            128 kB
            Ilias

          Activity

            People

              akif.hazarvi Akif
              ilias.kourtoudis Ilias
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Salesforce