Article Type: Release Notes Audience: All Users Module: Platform Releases
Note: QA Release Date: October 7, 2025. Production Release Date: October 21, 2025.
We have a big pile of feature highlights that will shiver your bones this October - I promise they're all treat and no trick. Read on to learn more!
The October 2025 release includes a new way to browse data in Fuuz: an API tree data browser! This component is available as a standalone screen ("API Tree Browser") or as a screen designer element for use in custom screens. It allows users to view data in the Fuuz GraphQL API in an expandable tree format, which is great for browsing hierarchical data like inventory.

The tree data browser is part of our ongoing goal of making data in Fuuz easier to comprehend, emphasizing the strong data modeling capabilities in the Fuuz platform.
Since we released our data export system in May, we've had lots of users with a variety of experience levels use it, and they have provided some great feedback! With this month's release, we've completed a round of user experience improvements based on a combination of that user feedback and our own plans to improve the tool post-launch. We'll break those changes down into a few categories below!
First up, saved export configurations in Fuuz can now be scheduled to run on a recurring basis! The user who created the export configuration will be automatically emailed when the scheduled export is completed, and the export history can always be viewed in the Export History screen. This is a great feature for automating simple reporting or data backups from Fuuz - although as always, more complicated use cases can still be handled using the data flow system.

With this release, we've also made the process of getting a simple export more straightforward. The Export Data screen is now a simplified interface, and with as little as five clicks, users can get a full export of every record in a collection: just select a data model, select the desired fields, select an export format (CSV or JSON), and hit go!

Finally, we've implemented a significant round of changes to the Export Configurations and Export History tables and forms to improve consistency and make both screens flow more naturally. There's always further room for improvements, so we'd love your feedback - let us know what you think!

The 2025.10 release includes a new toolbox tab in the screen designer: Scripts! This tab displays a summary of all "dynamic" behavior in a screen, such as hide/show or data properties that have computed values based on other screen state. Each element with at least one dynamic script property is displayed in the panel, and users can hover over elements in the panel to see what properties on an element are scripted. Using the Search input on the panel, the elements can be quickly filtered by element name, scripted property name, or the content of the script.

Users can also click on any of the elements with scripts to edit the scripted value for any of the properties:

This new tab makes it easier to understand the dynamic behavior running in a screen, which is especially valuable for complex screens with a high level of interactivity and guided user experience.
Also included in this month's release is a new feature aimed at making life easier for developers of reusable applications: Application Substitutes! Substitutes are a system-wide method for implementing customizations to screens, flows, data mappings, and other application components, keeping those customizations separate from the original implementation. Fuuz will use the substitute anywhere the original component is referenced - links, flow nodes, etc. - and the base app can always be upgraded underneath those customizations to bring the latest features to a customized implementation (although updates to the customizations may also be needed). One notable exception to this system is the Schema Designer - data models don't have substitutes... that's what custom fields are for!
You can find the "Create a Substitute" button in each designer's file menu, and you'll find new columns on the relevant tables to indicate which entries substitute or are substituted by another one. To "remove" a substitute and return to the base app's behavior, simply deactivate or delete the substitute component.


client_credentials grant type$pdfToJson binding$convertUnit unit conversion binding, as well as a $getUnit binding to return unit information by name, code, or ID_and predicates