check first http://jira.jboss.com/jira/browse/JBPM-854
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4042433#4042433
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4042433
___
check http://jira.jboss.com/jira/browse/JBPM-854 ...
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4040890#4040890
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4040890
___
jb
Take a look at this issue then, might be related to your problem:
http://jira.jboss.com/jira/browse/JBPM-854
Looks like conditions on transitions are not correctly retrieved from db, for
3.2. If your process def works ok in a JUnit test without persistence in db
(but parsing directly the def fr
simply try to write your conditions in decision node simpler, like this:
|
|
| var1 == '1'
|
|
| var1 == '2'
|
|
|
i think it should work (from my experience). if you still want to use #{...}
expresions, i think
Hi,
I think your problem is related to this:
http://jira.jboss.com/jira/browse/JBPM-913
I ended up removing the unique constraint on (KEY_, PROCESSDEFINITION_) for
table JBPM_PROCESSINSTANCE in order to make Jpbm 3.2 work on Oracle DB. (there
still remained an index on PROCESSDEFINITION_ due
JBPM-854 is not related, i've checked it already.
But http://jira.jboss.com/jira/browse/JBPM-853 is exactly this issue (haven't
found it before), and explains the cause and a fix.
thanks, topic can be closed.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=404
correction (condition tags missing):
| x == 'xxx'
|
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4040017#4040017
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4040017
_
from what i've seen, you can use simpler condition / access context variables
in a simpler way in conditions.
you should try like this (hope it works for you):
x =='xxx'
, where x is a variable on the process context.
did it work ? :)
View the original post :
http://www.jboss.com/index.html
Hi,
I had this problem: some process definition using decisions worked well on JBPM
3.1.4, but when I tried upgrading to 3.2GA, decision nodes didn't work
correctly anymore: they always chose the default transition.
After some work, I've seen that the conditions simply do not work in that
syn
