Chris,
Yes, we can only assure you the work item exists between it is triggered
and completed (or aborted). So if you want to access any data related
to it in an on-exit action or any further part of the process, it's
probably best to simply map that data to a process variable. This will
make yo
Hi Salaboy,
thanks for your response. Summing up I can say it was mostly lack
of understanding on my side... Kris's fix just made it visible. Please
let me know if I'm on the right track, my comments are inline.
Am 09.07.2010 16:56, schrieb Salaboy:
> Hi man,
> Did you recognize this error after
About the out-mapping attribute, you are right this will copy the values from
the variables inside the workitem to the process level.
Greetings
- CTO @ http://www.plugtree.com
- MyJourney @ http://salaboy.wordpress.com
- Co-Founder @ http://www.jbug.com.ar
- Mauricio "Salaboy" Salatino -
On Jul
Hi man,
Did you recognize this error after update?
Why are you doing that if you have the human tasks Apis to complete a task that
automatically set the result values.
I would like to take a look at your issue, can you provide me more info about
it?
Greetings
- CTO @ http://www.plugtree.com
Hi Kris,
we experienced some troubles with our drools flow integration today
(we upgraded to the lastest snapshot) and I found out that is has to
do with a fix (see [1]) you commited some time ago.
Our problem is, that we access the data submitted by the user to
finish a human task in the on exit
