Changelog

A new and improved version of the Cascader component is now available. Retool recommends using the new component, and the legacy version will be deprecated. You can click Upgrade in the Inspector of an existing Cascader component to use the new version.

The new Cascader features:

• The ability to manually add an option list or dynamically map one to existing data.
• A new dropdown look, similar to the Select component.
• New label options (customizeable caption, color, icon).
• Options now support numeric values in addition to string values.

Some additional changes in this version include:

• The value of the new Cascader component is the value of the selected option. A new valuePath property enables you to have access to the path of values leading to the selected option.
• Option values must be unique.
• Like other modern Retool components, values for options need to be unique. If you use the one-click upgrade for Cascaders, duplicate values will have parent values appended to make them unique.
• Like Checkbox Group and Navigation, the data source is expected to be an array of objects with a property that points to its parent. Cascader nests options by parent value.

Retool now provides the ability to add and customize shadows on most app components.

All users can customize the default shadows in app-level themes. Enterprise and Business plan users can customize and add shadows in organization-level themes.

Three default shadows are provided: low, medium, and high elevation. Users can also create custom shadows, which use CSS box-shadow syntax.

Retool Vectors now supports adding filter labels, and metadata to vector resources.

Retool AI supports using filters and metadata to query Retool Vectors with the Generate text, and Generate chat response AI actions.

Retool Vectors can be queried from Retool Apps or Retool Workflows using AI Actions.

An OpenAI reasoning model, o1, is now available for use in Retool AI actions.

Multipage apps are now generally available. Any new Retool apps that you create will support multiple pages by default. The creation of single-page apps is still supported but they are now considered legacy. Multipage for mobile apps remains in beta.

Building apps with multiple pages enables you to combine functionality and use cases. Retool only evaluates the code and components of the page currently in view, providing the following benefits:

• Greater performance of large and complex apps. Since Retool only evaluates code and components for the current page, apps can perform 30-40% faster.
• Seamless navigation between pages. Navigation between pages is seamless and more responsive than before as Retool only evaluates the current page, not the entire app.
• Improved app management. Multiple pages can replace multiple apps in your organization, such as a team's frequently used apps. This reduces the number of apps to maintain and allows for easier permission management.
• Reduced module dependency. Modules are commonly used to create shared navigation menus across multiple apps. With multiple pages, you can eliminate the need for additional modules and the complexities with maintaining them.

Each app uses global and page scopes to separate pages. Globally scoped code, and Header and Sidebar frames, are available for use across every page, while each page has its own page-scoped code and components.

You can now test deployments when using Source Control, preventing changes that leave your Retool instance in a broken state. Retool added the Test source control changes endpoint to the Retool API, which enables you to test whether implementing a change will result in deployment issues.

You can also incorporate this check into your continuous integration process if desired.

Improvements to the Navigation component are now available. When you add a Navigation component to an app with multiple pages, Retool automatically configures the menu items to map to the pages of your app. Event handlers are also preconfigured, and clicking a menu item takes you to the corresponding page.

You can still customize the Navigation component to have different behavior, if desired. Refer to the Navigation guide for more information.

This change also made retoolContext.pages and retoolContext.currentPage available. Refer to the Retool Context reference for more information.

Self-hosted Retool 3.114 is now available on the Stable release channel.

Retool has deprecated version 1.0 of the Databricks connector. If your organization has any Databricks resources that still use this connector version, update the resource configuration to use the version 2.0 connector.

Self-hosted customers must also enable the Java DBConnector to use version 2.0 of Databricks connector.

Change the connector version from the Databricks resource's configuration settings. Any existing queries that previously worked with version 1.0 will continue to work with version 2.0.

The option to use version 1.0 of the Databricks connector will be removed in Q2 2025 from cloud instances and subsequent releases for self-hosted instances.

Retool has deprecated version 1.0 of the MySQL connector. If your organization has any MySQL resources that still use this connector version, update their configuration to use the version 2.0 connector.

The option to use version 1.0 of the MySQL connector will be removed in Q2 2025 from cloud instances and subsequent releases of self-hosted Retool.