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

Validation of minlength and maxlength constraints inconsistent

    XMLWordPrintable

    Details

    • Type: Bug Report
    • Status: Closed
    • Priority: L2 - Critical
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 7.14.0
    • Component/s: engine
    • Labels:

      Description

      Steps to reproduce

      1. Deploy a BPMN model with a User Task and the following form field constraints:
        <camunda:formField id="StringField" label="A string field" type="string">
          <camunda:validation>
            <camunda:constraint name="maxlength" config="20" />
          </camunda:validation>
        </camunda:formField>
        
      1. In Tasklist, start a new process instance
      2. Enter a string with 20 characters
      3. Complete the task

      Observed Behavior

      • The frontend validation passes
      • The backend validation fails

      Expected Behavior

      The backend validation for maxlength is inclusive (similarity to minlength) and therefore accepts a string with 20 characters.

      Hints

      Forum link

        Attachments

          Activity

            People

            Assignee:
            tassilo.weidner Tassilo Weidner
            Reporter:
            bulbenov Alex Bulbenov
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: