Skip to main content

Changelog

Updates, changes, and improvements at Retool.

The App Inspector now appears when you have the Inspector open but no component selected. The App Inspector includes the following settings that were previously found in the App Settings sidebar:

  • Browser title
  • Custom URL
  • Custom shortcuts
  • Max width

The App Inspector also includes the Persist URL parameters setting, which configures search query parameters and hash parameters to persist during page navigation and when switching pages with the “Go to Page” event handler.

The directory structure for apps protected using Source Control is changing to reduce the likelihood of merge conflicts.

Component positioning information (stored in ToolScript files) is now organized by page. The apps directory contains a .positions directory, which contains one file per page in the format .pageName.positions.json.

Previously, all positioning information was stored in one .positions.json file. The new structure prevents merge conflicts.

This change is live on Retool Cloud, and it will be available in a subsequent release of Self-hosted Retool.

app-name
└── .defaults.json
└── .positions.json
└── .mobilePositions.json
└── lib
└── sqlQueryName.sql
└── jsQueryName.js
└── src
└── container1.rsx
└── functions.rsx
└── main.rsx
└── metadata.json

Retool now supports Drafts, a tab of the Apps landing page that provides a personal folder for each standard user to develop and test apps. Only you and organization admins have access to view or edit apps that you create in this section. This feature is useful for organizations where creating applications and folders is restricted, because admins don't have to give users explicit permission to create apps in their Drafts.

The availability of the Drafts tab can be managed by admins in Settings > Beta.

The Drafts tab is currently rolling out on Retool Cloud and will be available on the next edge release of self-hosted Retool.

Improvements to Debug Tools in the App IDE are now available.

This update includes the following changes and improvements to the Debug Tools:

  • New filters in the Linting tab: Errors and Accessibility.
  • New filters in the Performance tab: Severe, Moderate, and Minor.
  • In-line actions for automatic performance optimizations.
  • Actionable recommendations to the most common performance bottlenecks.
  • Links to relevant docs for further learning.
  • Removal of performance score and app stats.

Refer to the Web app and Mobile app best practices guides for more information.

Retool updated the layout of the Retool Apps landing page to reduce clutter and make it easier to find the apps you need. The updated organziation includes the following tabs:

  • Recent: The most recent 50 apps that you visited. The Viewed by me column shows the last time you opened the app, and the Location column shows you where the app is located.
  • Published: All items that you have access to within your organization. Use the dropdown to filter by Apps, Folders, Modules, and Protected.
  • Starred: The apps and folders that you starred.
  • Trash: The apps and folders in your organization that were deleted.

Retool recently discovered a bug in certain versions of self-hosted Retool that affects workflows using custom JavaScript libraries. This issue can:

  • Prevent you from adding new libraries to a workflow.
  • Cause existing workflows that use custom libraries to fail.

This issue can occur after upgrading from an earlier version of self-hosted Retool to one of following affected versions:

ChannelAffected versions
Stable3.114.1-stable to 3.114.8-stable
Edge3.114.0-edge to 3.144.0-edge

Retool has released 3.114.9 on the Stable channel which resolves the issue. The next Edge channel release will also include the bug fix.

If you have a deployment that currently runs an earlier version of self-hosted Retool, do not upgrade to an affected version.

Retool released several changes to the Command Palette that improve the experience when using apps with multiple pages. The following new features are supported:

  • New contexts: You can now select a page or a Main frame to use as a context for your search.
  • Page actions: You can now delete, duplicate, or create new pages.
  • Improved organization: When searching for components, results are now prefixed with their page ID, making it easier to tell where each component lives.

Use the Wait block to pause workflow execution for a specified amount of time. This block is useful for creating a single process that might need to take several hours, days, or weeks. For example, you could use the Wait block to:

  • Grant a temporary access token, and revoke it after 24 hours.
  • Send abandoned cart emails 1 hour after a customer leaves the website, and again after two days.
  • Add a delay between several API calls in a loop to avoid hitting rate limits.

After the Wait block finishes executing, the workflow continues execution of the blocks downstream. Wait blocks only pause execution for blocks that are directly downstream, and they not do not affect blocks that are executed in parallel.

Workflow blocks, which enable you to trigger one workflow from another, now support two execution modes:

  • Finished: The current workflow execution is paused until the triggered workflow run has completed.
  • Queued: The current workflow execution continues and the triggered workflow run is queued. Both workflows may run simultaneously.

A new and improved version of the Cascader component is now available on Retool Cloud and for self-hosted organizations. 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.