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.

Deceased support for Exclusive Gateway 'default' transition

mmaker1234

Hello Activiti Designer developers,

Recently we tried to deploy in an Activiti 5.11 engine a process definition developed with Activiti Designer 5.11.1 and received the following message:

WARNING: Exclusive Gateway has outgoing sequence flow 'flow31' condition which is not the default flow. We assume it to be the flow, but it is bad modeling practice, better set the default in your gateway. | MyProcess.bpmn | line 0 | column 0

Yesterday we reviewed the process definition in Activiti Designer 5.11.2 and realized that there is an Exclusive Gateway with two outgoing transitions - one with a condition and another one (flow31) without condition. The "default" property of the Exclusive Gateway was not set. We set the property and saved the file. Then we compared the file to the source repository and found that there are … no differences.

Today we tried to set the property on the dev.env. of the process developer (Activiti Designer 5.11.1). The result was the same - there was no change in the BPMN file.

Then I tried to change the property on my environment - Activiti Designer 5.10.0. The property was set and stored to the file.

Please revive the deceased functionality.

Find more posts tagged with

Comments

mmaker1234

Sorry, I too late found that the problem was reported at http://forums.activiti.org/en/viewtopic.php?f=8&t=5971 and there is registered a Jira issue http://jira.codehaus.org/browse/ACT-1546

leggebroten

It appears this bug is back.

Reported fixed for 5.12 (Activiti ACT-1546 Impossible to assign default flow on exclusive gateways)

But I am having the same "failure to save" behavior using 5.14.

jbarrez

Do you mean it doesn't work on designer side or on engine side?

leggebroten

The designer does not preserve default flows.
When I add them by hand in the XML, they are not rendered in the designer.
If I add them in the designer, they are no preserved (e.g. they are not present in an exported model nor are they present if you edit that model again)

I have not tested whether the engine will recognize them when added by hand.

jbarrez

I've verified and it is fixed currently on the master branch. The current plan is to release this version (which includes this fix) before christmas.

leggebroten

Cool. Thanks