[jBPM][3.1.1] Transition with condition in decision

[ephemeris-lappis]

Hello.

I've been testing using simple JPDL examples.
I've understood a transition can be selected according to a condition expressed in a condition node.

Here an example of my tests :

<decision name="decision-after-activity-1">
 <transition name="2a" to="activity-2a" />
 <transition name="2b" to="activity-2b">
 <condition expression="#{contextInstance.variables['V1'] == 1}" />
 </transition>
</decision>

In these lines the two transition tags contain a name attribute that the documentation says to be optional. In my processs definition, this works. If the given variable is previously set with the expected value, the condition is matched and the second transition is selected...

But if i remove the name attribute, in particular in the second transition that supports the condition, the expression doesn't match anymore and the first transition is followed...

Is this a documentation interpretation error, about the option name attribute, or a strange bug ?

Thanks.

[kukeltje]

In the forum, there has been some discussion about the 'default' transition. Use some of these terms to search. I'm not sure myself what the current (3.1.x or 3.2) behaviour is. Maybe the 3.2 docs in cvs have some explanation, but I do not have access to these atm.

[ephemeris-lappis]

I've searched the forum for something about that, but i'm sorry : it seems that nothing matches.
Indeed i've also read something about a new behaviour of the default transition that seems to be the first one in the decision block in the recent version.
This is not exactly my problem : i've just doubts about the name of the transition that seems to be optional in the schema, but mandatory at runtime to make the execution take the condition into account.

In my exemple, the second transition with its name works as expected :

 <transition
 name="2b"
 to="activity-2b">
 <condition expression="#{contextInstance.variables['V1'] == 1}" />
 </transition>

But if i just remove the name like that :

 <transition
 to="activity-2b">
 <condition expression="#{contextInstance.variables['V1'] == 1}" />
 </transition>

It doesn't work anymore, and the decision fails !

An idea ?
Thanks anyway...

[kukeltje]

so don't remove the name. It is more clear also in the GPD if there is a name.

The schema and runtime validation are not fully in sync. It is best to just add it. Is your problem solved then?

[ephemeris-lappis]

Yes, i already had the solution you say : let the transition with its name !
But i think this point should be clarified in the documentation (and/or schema) for those that are going to do the same and spend time looking why this don't work...

Thanks anyway.

[kukeltje]

point taken, can you file a jira issue on this? There is already one with an issue about an empty transition name. Refer to this from the new issue.

[icyjamie]

Yeah, also had a hard time debugging why conditions did not work. Now it is on our tips and tricks for jBpm wiki:

DON'T FORGET TO NAME THAT TRANSITION :-)