Welcome to Community Week 2025! Join us to learn, connect, and be recognized as we celebrate the spirit of Community and the power of AI. Get the details  

Flow Designer Get Catalog Variables - Yes/No type output value in Zurich

Alex Aluchi
Mega Sage

Hello - we have this Zurich issue and would apreciate your input.

In Zurich release we observed that Service Catalog type Yes/No variables when leveraged with Flow Designer > Get Catalog Variables action output Runtime Value true/false as opposed to yes/no in Yokohama or Xanadu releases (added some screen shots for context)

Are you aware of some system property that mitigates this issue? Any feedback is appreciated. Thanks all.

Screenshot 2025-10-16 at 17.57.45.png

Screenshot 2025-10-16 at 18.03.05.png

 

1 ACCEPTED SOLUTION

Alex Aluchi
Mega Sage

@Ankur Bawiskar @Dr Atul G- LNG @kaushal_snow ServiceNow answered to the HI Case and they do have a property that will revert behaviour. 
Add system property "com.glide.hub.flow.catalog_variables.yes_no_as_boolean" and set value to false.

View solution in original post

12 REPLIES 12

kaushal_snow
Giga Sage

@Alex Aluchi ,

 

In Zurich, Get Catalog Variables returns true/false for Yes/No catalog variables because in the Zurich version they’re mapped to Boolean type (True/false) in Flow Designer....

 

If you found my response helpful, please mark it as ‘Accept as Solution’ and ‘Helpful’. This helps other community members find the right answer more easily and supports the community.

 

Thanks and Regards,
Kaushal Kumar Jha - ServiceNow Consultant - Lets connect on Linkedin: https://www.linkedin.com/in/kaushalkrjha/

You often have to explicitly convert back to Yes/No via a script step (checking if the variable == 'Yes' then returning 'Yes' or 'No') to work with choice fields...

 

Thanks and Regards,
Kaushal Kumar Jha - ServiceNow Consultant - Lets connect on Linkedin: https://www.linkedin.com/in/kaushalkrjha/

Thanks for the feedback Kaushal. The refactor and regression testing is extensive and with high impact. I still hope there is a fallback option other than not upgrading until refactoring all impacted areas.

Ankur Bawiskar
Tera Patron
Tera Patron

@Alex Aluchi 

I don't think it's because of Upgrade.

Did you compare it against your instance which is in Yokoham/Xanadu?

Seems something similar was reported earlier as well

AnkurBawiskar_0-1760629316783.png

 

💡 If my response helped, please mark it as correct and close the thread 🔒— this helps future readers find the solution faster! 🙏

Regards,
Ankur
Certified Technical Architect  ||  9x ServiceNow MVP  ||  ServiceNow Community Leader