What's new on Retool

Retool for Startups

Eligible startups now get 12 months of free Retool credits (up to $1200 value), and we've partnered with companies like HubSpot, Segment, DigitalOcean, and Brex to offer many more startup discounts (apply here!).

If you applied and were accepted into the Retool for Startups program, you now have access to a new Startup Offers section in your Settings. To view more details and redemption instructions, go to Settings > Startup Offers:

Questions about the program? Enrolling in these offers? Drop us a note at support@retool.com (also, if you'd like to feature a startup deal for your company on the Startup Offers page, apply here).

Fixes and improvements

• Added a new event handler action type to set and clear local storage key/value pairs
• Added a toggle to the Number Input component to allow null values
• Fixed a regression that would cause the editor to crash when deleting temporary state variables
• Improved the app homepage search results to show what folders apps are in
• Fixed the "hide reset button" switch on the Wizard component
• Fixed default values and "Change" event types for the Range Slider component
• Fixed app versioning such that the editor always shows the most up to date version, even if an earlier release is published
• Added a tooltip to display the full app name on hover for the "Go to app" event handler
• Fixed the Tags component so that it can reference other queries/components (e.g. {{ .. }}) when setting tag titles
• Updated the labels for undo/redo shortcuts to be platform-specific

Check out this guide to see the on-prem versions and their release notes. These fixes and improvements will be rolling out to on-prem customers in the next few weeks.

Switching between component types

You can now easily switch the type of a component (e.g. Button →Link), and we’ll transfer over all applicable settings like label configuration, tooltips, and more! Let's say that you’ve set up a Number Input with a default value, min/max, label, and tooltip, and then you decide you actually want your users to be able to select their value via a Slider.

Previously, you’d have to drag out a new Slider component and manually copy over each of your settings one by one. Now, all you need to do is click on the three dots menu in the component inspector (right-hand panel) and click “switch component":

For most input components, you can now switch to a preset or other similar component type (for Number Input, that’s Slider, Percent, Currency, Rating, and Range Slider). Sometimes, we’ll prompt you for additional action when we can’t automatically convert all of your settings: like when switching from a Slider to a Range Slider, you’ll have to choose start and end values. There are so many different options to try out: like switching between different styles of Buttons (Button, Outline Button, and Link)!

We’re rolling out this new functionality to all users over the next week. Additionally, we’re working on fully overhauling additional components like Select and Multiselect, so you won’t see these options on those components just yet. Let us know how “Switch component” works for you, and any other components/presets you’d like to see at support@retool.com!

Fixes and improvements

• Improved start time when running query
• Improved performance during drag-and-drop
• Fixed an edge case where multiple queries to the same resource would occasionally fail
• Added support for plain numbers in the border radius style editor (assumes px unit)
• Fixed file parsing for the new file input component types on Windows
• Added a new option to the Text Input component to show a character count
• Improved search in the component list
• Fixed a rare edge case where the preview button in editor mode would hang indefinitely
• Fixed GraphQL queries to exclude empty optional fields
• Added support for using self-signed certificates with MongoDB connection string

Check out this guide to see the on-prem versions and their release notes. These features and performance improvements will be rolling out to on-prem customers in the next few weeks.

Resource permissions

All admins will now be able to assign two different permission levels for any given resource: (1) "use," which allows an editor to write queries with that resource and (2) "edit," which additionally allows an editor to modify the resource's configuration.

Previously, admins had minimal control over permissions to resources — any resource permission granted at a group level would allow members of that group to modify the configuration of the resource. We know configuration for some resources can be sensitive and complex to change, so we've shipped these new permission levels to give admins more control over their user's access.

Additionally, to allow editors to create new resources or delete existing ones, admins can assign a group to have “universal access” at the “edit” level. As always, a “viewer” of an app (e.g. no edit permissions) can still view and use an app that leverages a resource for which they do not have explicit permissions granted.

These new resource permissions are available to all admins across Pro+ plans. Drop us a note at support@retool.com to let us know how they're working for you!

Fixes and improvements

• Added a new Progress Bar component with an indeterminate state
• Added a new scalable Progress Circle component
• Fixed local storage dependencies such that values nested inside a third level now trigger updates correctly (e.g. localStorage.values.x.y)
• Fixed dynamic height for direct children of Modules and Modals
• Removed inconsistent right panel behavior in favor of the pop out code editor
• Updated the Divider component to support an optional text label
• Added the ability to see tables that are related to your query in the query editor's schema browser
• Fixed the visible scrollbar on single line, fixed height Text components
• Fixed an issue where transformers do not run on page load if they depend on disabled queries

Check out this guide to see the on-prem versions and their release notes. These features will be rolling out to on-prem customers in the next few weeks.

Event handlers for queries

When your query succeeds or fails, you can now trigger other queries, control components, call additional APIs, and more–all using event handlers!

For most Retool apps you've built in the past, you've probably set up the "After this query runs" triggers. For example, let's say you have a query, selectUsers, populating a Table component; if you insert a new record to the users table, you probably want to re-run that selectUsers query so that your Table is up to date:

However, anything more complex–showing a notification, controlling components (e.g. opening a modal)–previously required creating and wiring up a JavaScript query, and writing custom code.

A few months ago, we rolled out new event handlers to all of your components. We're now replacing the old query triggers, and bringing those powerful event handlers to your queries! You can configure any number of event handlers to run when your query succeeds or fails (e.g. on success, show a notification to your end user and open a modal to prompt a new workflow).

Anything you can do with Retool’s JS API (e.g. query1.trigger(), modal.open(), utils.showNotification(...)) you can do with event handlers. If you do have a need to write some custom JavaScript, it's even easier than before. You can just use the "run script" event handler and write your code, without creating and wiring up a new query.

As you build with these new event handlers on your queries, we want to hear from you! Are there more kinds of event handlers you'd like to see us add? Any feedback? Drop us a note at support@retool.com.

Fixes and improvements

• Updated default component IDs to use camelCase (e.g., checkboxGroup1)
• Added advanced editor features to the Text Area component, including autocomplete, autocapitalization, and spell check
• Added support for exploring queries and transformers in the model browser (left-hand panel) while actively editing a different query or transformer
• Added a change event handler to BoundingBox component
• Added a Front integration
• Fixed Folders and Apps so that they're sorted consistently
• Fixed an edge case with query trigger migrations for the new query event handlers
• Fixed an edge case where the "Go to app" event handler wouldn't successfully navigate

Check out this guide to see the on-prem versions and their release notes. These features will be rolling out to on-prem customers in the next few weeks.