In the latest ServiceNow update, Zurich (released Q4 2025), a change was made to the way Yes/No type Catalog Variables are interpreted. Yes now resolves to true, and No resolves to false. ServiceNow has documented this behavior change in their Support and Troubleshooting Knowledge Base. You can find the full details of the change and why it was implemented here.
While the change appears minor, it can be detrimental to organizations that are upgrading to Zurich. It may break existing logic in areas such as Flow logic, Activity Set Logic, and more where “Yes/No” was previously treated differently. If you’re seeing unexpected behavior, or simply wish to avoid missing any logic that needs revisiting, you can revert to the prior behavior via a system property.
Create a new true/false system property and name it “com.glide.hub.flow.catalog_variables.yes_no_as_boolean.” Don’t forget to set the new property to false.
If this update introduces issues in your environment or you’d prefer not to manage these changes alone, Pathways can help. Our team handles upgrades, configurations, and full implementations, so your instance gets all the benefits of the update without breaking your current configuration.
While the above technical tip has been provided with care and consideration, it’s important to acknowledge that individual circumstances may vary. Always ensure compatibility and feasibility within your specific ServiceNow environment before implementing any suggestions. Additionally, back up your data and proceed with caution when making any changes to your instance or workflows.
As with any change in ServiceNow, make sure you test any changes prior to moving to production.
