Eclipse Community Forums: BPMN 2.0 Modeler » Why Documentation property was made single line?

Home » Eclipse Projects » BPMN 2.0 Modeler » Why Documentation property was made single line?(Can multiline Documentation be back?)

Show: Today's Messages :: Show Polls :: Message Navigator

Why Documentation property was made single line? [message #1100877]

Tue, 03 September 2013 18:38

Mikhail Mising name

Messages: 2
Registered: July 2013

Junior Member

I remember seeing Documentation property as a multiline entry. It was quite handy to enter notes like that. However I noticed that recent updates have Documentation as a single line entry and all my newlines appear as squares (as missing unicode placeholder).

Is there any particular reason for having it a single line vs multiline?

Report message to a moderator

Re: Why Documentation property was made single line? [message #1100926 is a reply to message #1100877]

Tue, 03 September 2013 20:10

Robert Brodt

Messages: 811
Registered: August 2010
Location: Colorado Springs, CO

Senior Member

Hi Mikhail,

There was a request from the jBPM folks to make Documentation a single line entry, probably because this field wasn't being used very often. As you know, a BaseElement can actually have a List of Documentation elements, which is rendered in the Property View as a list of items. Each of those items contains an ID, a text body and text format string (mime type). Really, the only attribute of any interest here was the text body since text format was always assumed to be "text/plain". Looking back on this now, it does make sense to use a Multiline Text field in the Property View. Can you please file an enhancement request in bugzilla?

Thanks,
Bob

Report message to a moderator