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.

Forwarding variables to the next task

kpagratis

I have a workflow with three parallel paths.
I want to assign task variables at any time, but have those variables be forwarded to the next task. Is this possible?

Find more posts tagged with

Comments

frederikherema1

This doesn't happen out of the box. The best way I can think of is adding a TaskListener to the tasks, flushing the variables to the execution and loading them again in next task eg:

<br><userTask id="firstTask" name="My Task" ><br>&nbsp; <extensionElements><br>&nbsp;&nbsp;&nbsp; <activiti:taskListener event="complete" class="org.activiti.FlushVarsListener" /><br>&nbsp; </extensionElements><br></userTask><br><br><userTask id="nextTask" name="My Task" ><br>&nbsp; <extensionElements><br>&nbsp;&nbsp;&nbsp; <activiti:taskListener event="complete" class="org.activiti.ReadVarsListener" /><br>&nbsp; </extensionElements><br></userTask><br>

<br>public class FlushListener implements TaskListener {<br><br>&nbsp; public void notify(DelegateTask delegateTask) {<br>&nbsp;&nbsp;&nbsp;&nbsp; for(Entry<String, Object> var : delegateTask.getVariables().entrySet()) {<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; delegateTask.getExecution().setVariable(var.getKey(), var.getValue());<br>&nbsp;&nbsp;&nbsp;&nbsp; }<br>&nbsp; }<br>}<br><br>public class ReadVarsListener implements TaskListener {<br><br>&nbsp; public void notify(DelegateTask delegateTask) {<br>&nbsp;&nbsp;&nbsp;&nbsp; delegateTask.setVariableLocal("previousTaskVar", delegateTask.getExecution().getVariable("taskVar"));<br>&nbsp;&nbsp;&nbsp;&nbsp; &hellip;<br>&nbsp; }<br>}<br>

tombaeyens

Frederik, are you sure?

If you don't declare variables and you set the variable value the first time, then the variables are created in the process instance scope. Which means that they will be visible in the next task. no?

In other words, I think it should just work out of the box as the default behavior.

jbarrez

This would indeed work, but only if the three parallel paths dont share the same variable names.
If using task-local vars, then the solution of Frederik can be used.

kpagratis

thanks for the reply. I'll try it out.