Updates, changes, and improvements at Retool.
Refer to the stable and edge release notes for detailed information about self-hosted releases.
Using the built-in Mobile Push Notifications resource, you can write queries that send push notifications to specific users from any Retool web app, Retool Mobile app, or Retool Workflow via webhook. Contact us to get started or read our push notification docs to learn more.
You don't have to upgrade existing apps that use the legacy Table component. You can continue to configure the legacy Table in your existing apps, and then use the new Table component when you have an app to build.
If you want to migrate an existing app to use the new Table component, use this guide to learn more about the differences before migrating.
The new Table no longer supports the Auto column format. Each column must have an explicit format. Each column can contain an optional source key, which maps the column to a field in the data source. If the source key is omitted, the column is effectively a custom column.
Some commonly used Table properties have been renamed. Anywhere in your app where you reference these properties, you’ll want to update those references to the new property names.
selectedRowThe property to access the Table’s selected row changed from table1.selectedRow.data to table1.selectedRow.
currentRowcurrentRow in a column’s mapped values is now currentSourceRow, to make it explicit that it references the underlying source row’s data.
recordUpdates and changeSetThe legacy Table’s edited fields were exposed in recordUpdates and changeSet. These fields are now changesetArray and changesetObject, respectively. These properties no longer contain the entire row’s data, and instead only contain the modified fields.
Pagination controls are now nested under table1.pagination. This means referencing a table’s pageSize, for example, is done using table1.pagination.pageSize. Pagination is now accessible in the Table’s Add-ons section in the Inspect tab.
The new Table exposes the built-in save and cancel buttons for bulk editing in the Add-ons section of the Inspect tab.
The legacy Table exposed several fields to represent the Table’s sorting state: defaultSortDescending, defaultSortByColumn, sortedColumn, sortedDesc. The new Table exposes the sortArray property, which represents the entire sort state of the table.
The legacy Table did not support nested filtering. The new Table supports nested filters with the filterStack property.
See below for a feature-by-feature comparison of the legacy Table and the new Table.
| Category | Feature | Description |
|---|---|---|
| Column type | Auto column | The new Table forces explicit column types. |
| Column type | Button column | The new Table has redesigned actions for triggering events. |
| Column type | User Email column | The new Table has an Avatar column that serves the same purpose. |
| Column type | Modal column | Modal columns are not supported natively in the new Table, but can be implemented by using a Column event handler to trigger a Modal component open. |
| Actions | Action button columns | The new Table floats all action buttons to the right edge of the table when you hover over a row. |
| Category | Feature | Description |
|---|---|---|
| Column type | Rating column | You can use a Tag column to represent a rating cell instead. |
| Sorting | Sort columns by raw value | The new Table sorts columns by their mapped values. |
| Styling | Row color | Row color is not supported in the new Table. |
Retool Mobile now enables you build white-label Retool Mobile apps and launch them in the iOS App Store and Google Play. With a white-labeled app, you can choose your app’s name, icon, and splash screen, and also manage the version of the app available to your users to take full control of what you build. White-labeled apps are available to customers on our Enterprise plans. Contact us to get started or read our white-label app docs to learn more.
The Retool Mobile app now includes a side drawer to access frequently used apps. Users can also open Retool Mobile and automatically launch the most recently used app.
You can now configure app linking event handlers to enable users to navigate from one mobile app to another. In the App editor, configure an event handler with the **Navigation **action, the Open app method, and select the app to use.
You can now set a width-factor on containers to create more complex layouts in Retool Mobile.
We’ve added the ability to work with resources and apps that have multiple environments in Retool Mobile using our new environment switcher
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:
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.
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.
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.
Each component now has the same three sections, which makes it easier to find similar properties across different components:
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:
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.
