Unfortunately we’ve faced with this issue too. In out-of-the-box Tasklist application ‘maxlength’ constraint works correct, but engine generates an error. When this bug will be fixed? Thanks.
Could you please provide an example which is working in Tasklist and failing on engine side.
Other than that feel free to open a bug report or raise a pull request.
I see @f_a described in details at top. The fix is dead easy - just change ‘<’ to ‘<=’ in MaxLengthValidator.java.
Can you explain me how I can open a bug report and raise a pull request? We’ve worked with Camunda for a month only. At the moment evaluating it for our business.
I was curious that it is working in Tasklist for you.
You can open a bug report via Jira [1]
Or if you’re interesting in providing a pull request please check github page [2]
and our How to contribute guide [3]
If you have questions, please do not hesitate to ask.
@StephenOTT, thank you. Your script can be useful in some apps.
However I described bug in camunda engine (general maxlength bpmn constraint validation).
Yes, the bug is identified as part of the validator. But you can still recreate the same validation outcome without using that specific validator; thus bypassing the bug. Using the script validation plugin you can do a min and max length validation directly in Js