How to pass data between nodes in a workflow and use it in a Decision controller ?

[Gros-Jambon-Fr]

Hi,

I'm trying to build a workflow that checks the current day of the week and uses a Decision controller to branch accordingly (e.g. run different jobs on weekdays vs. Sunday).
My approach was to create a first Shell Plugin job that outputs the current day as JSON:

#!/bin/bash
DAY=$(date +%u)
echo '{"complete":1,"data":{"day":'$DAY'}}'

Then use a Decision controller with the expression input.data.day == 7 to check if it's Sunday.

However, the expression always evaluates to false, even though the job completes successfully and outputs the correct JSON. Looking at the Expression Builder, the data appears to remain in the output field as a raw string rather than being parsed and made available under input.data.

I also tried enabling "Interpret JSON in Output" in the Shell Plugin settings, but the behavior is the same.

I also tried using new Date().getDay() == 0 directly in the Decision controller without any preceding job, but JEXL doesn't seem to support the new keyword.

Am I missing something? What is the correct way to pass structured data from a Shell Plugin job to a Decision controller in a workflow?

Thanks!

[jhuckaby]

So sorry for the confusion. When you output JSON for xyOps to read, you need to include a top-level xy property set to 1. This is how xyOps knows to consume the JSON and interpret it. Otherwise it just passes it through. This should do the trick:

echo '{"xy":1,"complete":1,"data":{"day":'$DAY'}}'

[Gros-Jambon-Fr]

Thanks for the quick answer :) It works perfectly !

[jhuckaby]

I was reading your description again:

I'm trying to build a workflow that checks the current day of the week and uses a Decision controller to branch accordingly (e.g. run different jobs on weekdays vs. Sunday).

Just FYI, there is another way you can do this. A workflow allows for multiple points of entry, so each trigger node can connect to a different job. For example:

Dunno if this works for you, but just letting you know the feature exists 😉

Enjoy!

[Gros-Jambon-Fr]

The thing is in my case, i need to have only one trigger but i need to branch in the middle of the workflow. So i will use the first solution with the bash script and the decision node !

Thanks