New lines in custom element properties are removed when editing in “Extension” Tab.
When editing in Extension tab, it shows all the property values without new line. If you change any one of the property, then all the properties loose new line character.
It shows without any new lines in extension:
Adding a new property in extension:
The field value is changed without new lines as seen in XML or general tab
Seems like new lines are not properly escaped in camunda:property elements.
What does the serialized result in the BPMN 2.0 XML look like?
XML when added custom field property:
This is how it shows in extensions:
Without any updates in extensions tab, XML is preserved as is:
Updating any property, updates others as well:
Could be because the text type for property is preserved in custom elements, but in property extension it is treated as string.
New lines in text fields are simply discarded. Because of that when saving Foo\nBar will be saved as Foo Bar.
Hi,
I think retaining new lines (as entered in text boxes in the modeler) is important in several cases.
Consider a script task for example. If you create a JavaScript script task, new lines are essentially treated like a semicolon – they end a statement. So stripping out new lines causes JavaScript tasks to break, and can be disconcerting to developers accustomed to using the new line style. We encountered this, and were very confused at first, until we figured out that adding back in the semicolons at the end of each line fixed the issue.
Another important case, is if you want to preserve formatting in a text field that is used as input to a custom task (e.g. a JavaDelegate). While there is a workaround for the JavaScript case, there appears to be no workaround in this case.
Thanks,
Galen
Hey I need a help, While passing the message from user task form field of string type, camunda is accepting it if it doesn’t have line break or tab,but it fails the request if it have any of those