-
1. Re: propagating updates to process variables
kukeltje Mar 8, 2008 12:09 PM (in response to aapthorp)no, not without you writing some code. In 3.0 there were no task specific variables so each (parallel) task could modify the processvariables. Most users found this unwelcome and therefore the behaviour changed.
About how (and if) superstates could help I have no clue.. -
2. Re: propagating updates to process variables
aapthorp Mar 8, 2008 3:32 PM (in response to aapthorp)Ronald, thanks, I had a suspicion this was the case. Strange I would've thought this would be a common requirement. Hmm, need to find the right way to model this first. I tried having an update task in the task node with the task I want to have updated - but couldn't figure out how to signal the target task instance when the update occurred.
-
3. Re: propagating updates to process variables
kukeltje Mar 8, 2008 3:42 PM (in response to aapthorp)I think you should create an action, put that on each (task) node-leave event. In that action, search al tasks with the same parent token (meaning they are in parallel) and then update the variables of those tasks.
-
4. Re: propagating updates to process variables
kukeltje Mar 8, 2008 3:45 PM (in response to aapthorp)s/should/might be able to/