Hi,
Why don’t you use the data value directly in the next step? Can you share a basic job example to take a look at?
If you need to do something outside data variables directly. You can use the data node step with the data gathered in the previous step, like this:
- defaultTab: nodes description: '' executionEnabled: true id: 825a2977-e82b-4e8f-b587-e5296abf219e loglevel: INFO name: HelloWorld nodeFilterEditable: false nodefilters: dispatch: excludePrecedence: true keepgoing: false rankOrder: ascending successOnEmptyNodeFilter: false threadcount: '1' filter: node.* nodesSelectedByDefault: true plugins: ExecutionLifecycle: {} scheduleEnabled: true sequence: commands: - exec: whoami plugins: LogFilter: - config: invalidKeyPattern: \s|\$|\{|\}|\\ logData: 'true' name: mydata regex: (.*) replaceFilteredResult: 'false' type: key-value-data - exec: echo "the data is ${data.mydata}" - configuration: data: mycustomdata=${data.mydata} format: properties nodeStep: true type: stub-node-step - exec: echo ${stub.mycustomdata} keepgoing: false strategy: node-first uuid: 825a2977-e82b-4e8f-b587-e5296abf219eIn this way, you can use it in the node context.
Regards!