Issue with Flow Designer True/False Subflow Inputs After Upgrade to Xanadu Version

[siddharthgu]

Hello ServiceNow Community,

We are encountering an issue with Flow Designer after upgrading to the Xanadu version. Specifically, when trying to save or pass the input value for True/False subflow inputs, the value is not being saved. Has anyone else experienced this issue or know why this might be happening?

Please refer to the screenshot below for reference.

Any insights or solutions would be greatly appreciated.

Thank you!

[Ankur Bawiskar]

@siddharthgu 

So you are saying it was working fine in Washington but not working in Xanadu?

If yes then might be a issue with the version.

Till the time this is fixed try to come up with a workaround and achieve your requirement.

If my response helped please mark it correct and close the thread so that it benefits future readers.

[Ankur Bawiskar]

@siddharthgu 

Thank you for marking my response as helpful.

If my response helped please mark it correct and close the thread so that it benefits future readers.

[Ron28]

In my case all of this was working on WashingtonDC, we still have WashingtonDC instances and I've compared the two - definately introduced by the Xanadu upgrade.
Ron

[Ron28]

Yes I've also noticed issues and reported it to ServiceNow.
In my case, I have outputs from a FD Action in array.string format. These outputs are passed as inputs on a sub-flow. But upon saving the flow that calls the subflow, all inputs in array.string value disappear. There's no error, the flow says it is saved ok.

In addition to that, also relating to array.string values. I created a new FD action today (scripted) and push data into the outputs object, with outputs.atmProfiles.push(...)
For my own sanity, put a gs.info immediately after which confirms there's data in the outputs.atmProfiles array.
But the step output shows no data in output variable atmProfiles (array.string).

Ron