BUG? - candidate start users/groups

[unknown-user]

Hi all,

If you enter a candidate start user/group in Designer (5.10) and save the process, once you re-open the process it will be empty…

Thanks,
Markus

[unknown-user]

Apparently only concerns processes that have been edited with Designer versions prior 5.10?
If you create a new process everything is ok…

[unknown-user]

Update: the error only occurs, if you enter both, candiate start users/groups and a text in the documentation field???

[frederikherema1]

That's really strange… So this happens in the new designer as well? If so, can you create a JIRA for this, explaining how to reproduce the error?

[swissedge]

It is a bug in the methode BPMN20ExportMarshaller::marshallBPMNDiagram().
if we have a process property with documentation and candidate (user or group) then the documentation will create a new element before the attributes candidate user and group, which will raise an exception.
I guess If you move the  documentation calls after candidate (user and group) calls then it should work. I couldn't find a JIRA… should I create a new one?
…
        if (StringUtils.isNotEmpty(process.getDocumentation())) {
 
          xtw.writeStartElement("documentation");
          xtw.writeCharacters(process.getDocumentation());
          xtw.writeEndElement();
        }
       
        if (process.getCandidateStarterUsers().size() > 0) {
            Iterator<String> candidateStarterUserIterator = process.getCandidateStarterUsers().iterator();
            String candidateStarterUsers = candidateStarterUserIterator.next();
            while (candidateStarterUserIterator.hasNext()) {
             candidateStarterUsers += ", " + candidateStarterUserIterator.next();
            }
            xtw.writeAttribute(ACTIVITI_EXTENSIONS_PREFIX, ACTIVITI_EXTENSIONS_NAMESPACE, "candidateStarterUsers", candidateStarterUsers);
          }

[tiesebarrell]

I see what you mean and can reproduce the problem. Please create a Jira ticket for this. Also, make sure you mention that this applies to configuration on the process' start node, not on regular user tasks. I tested those too and they don't seem to have the same problem.