nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

As we transition to the new Hyland Community, some post links may be temporarily disrupted as we finalize redirects. We apologize for the inconvenience and are working to resolve this as quickly as possible. Details.

Form property missing when BPMN Model converted to XML

vgaur

Hi,

I am trying to generate XML from BPMN model. I have a user task which has a Form Definition which in turn contains several properties.
when I convert this model into XML , I don't see the extension tag. All form properties are missing in the generated xml.

Do I need to set any special flag or something ?

Find more posts tagged with

Comments

vgaur

I just run test case in BPMN converter module and its creating the form properties properly. To give you more insight, I am using activiti-simple-workflow , creating workflow definition (with form properties) and converting it in XML.

vgaur

OK So I get this.
FormProperty id is a mandatory property and in simple-workflow-converter , when we convert HumanStep we set the id in formProperty with the name of formPropertyDefinition
<code>
formProperty.setId(propertyDefinition.getName());
</code>

trademak

So the issue is resolved?

vgaur

Yes Tijs,

I was not setting the name in FormPropertyDefinition and when I converted it into bpmn xml , the form properties were missing.
When I debugged I found that in org.activiti.bpmn.converter.BaseBpmnXMLConverter.writeFormProperties() there is check for id
<code> if (StringUtils.isNotEmpty(property.getId())) </code> .

So that means in FormPropertyDefinition name is a mandatory property. Ideally it should fail fast if name is not present. Also we should check if id is missing then only set id with name.

I have fixed few such issues and would like that to contribute if that helps.

jbarrez

All contributions are more than welcome! Looking forward to the pull request 😉