
Hi,
The best way to pass a data value to another job is to use a “receiver option” in the second job, in that way you can use the job reference step and pass the data value as an argument from the first job, let me share an example:
JobA (creates a multiline data capture output and store it on a data value, later pass that data value to JobB using job reference step):
<joblist>
<job>
<defaultTab>nodes</defaultTab>
<description></description>
<executionEnabled>true</executionEnabled>
<id>710dc75c-1409-4e11-a7e0-5f87a537094b</id>
<loglevel>INFO</loglevel>
<name>JobA</name>
<nodeFilterEditable>false</nodeFilterEditable>
<plugins />
<scheduleEnabled>true</scheduleEnabled>
<sequence keepgoing='false' strategy='node-first'>
<command>
<fileExtension>.sh</fileExtension>
<plugins>
<LogFilter type='key-value-data-multilines'>
<config>
<hideOutput>false</hideOutput>
<logData>true</logData>
<name>mydata</name>
<regex>^(.*)</regex>
</config>
</LogFilter>
</plugins>
<script><![CDATA[echo "one"
echo "two"
echo "three"
echo "four"
echo "five"]]></script>
<scriptargs />
<scriptinterpreter>/bin/bash</scriptinterpreter>
</command>
<command>
<jobref name='JobB' nodeStep='true'>
<arg line='-optb ${data.mydata}' />
<uuid>4b229654-f441-4530-a859-4cd528fea9d2</uuid>
</jobref>
</command>
</sequence>
<uuid>710dc75c-1409-4e11-a7e0-5f87a537094b</uuid>
</job>
</joblist>
JobB (receives the JobA data value using an option):
<joblist>
<job>
<context>
<options preserveOrder='true'>
<option name='optb' />
</options>
</context>
<defaultTab>nodes</defaultTab>
<description></description>
<executionEnabled>true</executionEnabled>
<id>4b229654-f441-4530-a859-4cd528fea9d2</id>
<loglevel>INFO</loglevel>
<name>JobB</name>
<nodeFilterEditable>false</nodeFilterEditable>
<plugins />
<scheduleEnabled>true</scheduleEnabled>
<sequence keepgoing='false' strategy='node-first'>
<command>
<exec>echo ${option.optb}</exec>
</command>
</sequence>
<uuid>4b229654-f441-4530-a859-4cd528fea9d2</uuid>
</job>
</joblist>
Hope it helps!