Changelog

We’ve added the ability to work with resources and apps that have multiple environments in Retool Mobile using our new environment switcher

• Added a Databricks integration.
• Added an improved version of the Slack integration.
• Added support for parent window communication in the latest runtime.
• Added the ability to select components directly from hover tooltips in the query editor.
• Fixed an issue where linting errors would incorrectly show on the await keyword.
• Fixed an issue where Multiselect and Multiselect Listbox components included undefined in value when options were dynamically removed.
• Fixed an issue where Retool Database schemas were unnecessarily refetched.
• Fixed an issue where SSO login on Retool Mobile would show an error when switching between apps on Android devices.
• Fixed an issue with broken custom auth template strings.
• Fixed Cmd+L keyboard shortcut to format code in Retool Workflows.
• Improved error reporting in custom authentication.
• Improved error reporting in List View components in the latest runtime.
• Improved spacing and styling of the JavaScript query code editor.
• Improved the Elasticsearch integration.
• Improved the layout of the Slack block in Retool Workflows.
• Improved the load time of the Workflows home page.

We’re excited to launch a new version of the Retool Inspector! By reducing clutter and improving consistency across components, we’ve made it easy to find important properties when you need them most.

With this re-design, we're adding:

• A new add-ons section
• Progressive disclosure for list editors
• Advanced panels
• More consistent property grouping

New add-ons section​

We’ve added a new section under “Content” called “Add-ons”. These add-ons include properties that were formerly known as “Adornments”, such as prefix icons, suffix text, and tooltips.

We’ve also split some components up into their constituent parts and are adding them to “Add-ons” as well. Each of these add-ons has its own properties and corresponding Inspector view (e.g. the Label add-on below). These add-ons are also visible on the editor canvas and can be directly clicked to open up the right panel.

Progressive disclosure for list editors​

Currently, we use the list editor pattern for adding event handlers. We're now applying this same pattern to Add-ons, Validation rules, and Styles. This hides away properties that have not yet been set, but can be added on an as-needed basis. You can add any of these properties by clicking the plus button next to each list editor’s header.

Advanced panels​

Instead of showing every property in each section, we now hide less frequently used settings inside of an advanced panel. You can access these properties by clicking on the advanced button in the header of each section.

Consistent property grouping​

Each component now has the same three sections, which makes it easier to find similar properties across different components:

• Content: Data that gets piped into the component, as well as any add-ons.
• Interaction: Event handlers, validation rules, and any properties that impact the behavior of the component.
• Appearance: Properties that change the look of a component, such as layout, style, and show/hide toggles.

We're excited to see what you think! Feel free to send any feedback to jessicasun@retool.com.

A line of sight into your business operations is critical to decision-making as you scale. With Usage Analytics, Retool admins have a single place to:

• Monitor all app and user adoption.
• Gain insight into aggregate usage to effectively manage teams and apps.

Usage Analytics is available to all Cloud and Self-hosted customers on the Enterprise plan. You can access it in your Organization settings.

Usage Analytics for Self-hosted deployments requires Self-hosted Retool v2.113 or later. Check out the docs to enable Usage Analytics.

The Response block in Retool Workflows allows for synchronous webhook runs. Workflows can now return data as a webhook response at any time during a run or upon completion.

The Response block works in conjunction with the Webhook trigger and enables you to configure your own responses. You can specify the HTTP status code and a JSON response body to return, which can include any data from the workflow. For example, use a workflow to look up a customer's mailing address based on their email, use multiple blocks to return different types of data depending on execution logic, or even use a Response block as an error handler to signal that something went wrong.

Response blocks are represented as a new block type; just drag out a block, select Response in the context menu, and your webhook will now wait until the Response block is executed to return. Check out the docs to learn more.