-
Type:
Feature Request
-
Resolution: Won't Fix
-
Priority:
L3 - Default
-
None
-
Affects Version/s: 7.2.3
-
Component/s: bpmn model api
-
None
The CamundaProperties object has CamundaID, CamundaName and CamundaValue attributes associated with it. This seems to be because on a form field the pair used is id/value, whereas on a task the attributes used are name/value.
I'd like to recommend that when parsing either, both id and name are populated, to give people a better feel of the API. Currently if I want to generically parse the CamundaProperties object, I need to do something like this:
if(camundaProperties != null && camundaProperties.getCamundaProperties() != null) { for(CamundaProperty prop : camundaProperties.getCamundaProperties()) { if(prop.getCamundaId() != null) { map.put(prop.getCamundaId(), prop.getCamundaValue()); } else { map.put(prop.getCamundaName(), prop.getCamundaValue()); } } }
Which is not ideal.