Changelog

An updated Theming experience is now available. Users on the Business and Enterprise plans can now see a revamped organization-level theme editing experience with expanded functionality, including:

• The ability to create custom color, typography, and metric tokens for use in the theme editor and app component styles.
• The ability to create multiple modes within a theme and switch between modes in an app using theme.setMode().
• The ability to configure default styles for individual components, as well as bulk edit shared styles for multiple components at once.
• Expanded typography controls—including the ability to configure multiple fonts in a theme using a CSS import or Google Fonts, set a default font family, and control font family and font weight for headings.

For users on all plans:

• Component-level font weight and font family style controls.
• A refreshed app-level theme experience with expanded typography controls.
• An updated component style editing experience.

Retool will deprecate the use of YAML for protected apps, queries, and resources in Source Control. Support will be removed in self-hosted Retool 3.196 and later.

Self-hosted organizations still using YAML serialization of these elements in Source Control must migrate to Toolscript prior to upgrading.

Retool now supports Amazon SNS. You can use the Amazon SNS integration in apps and workflows to publish messages to a topic. Once configured, you can subscribe to the topic using Amazon SQS, enabling you to use Retool's SQS integration to respond to events as they occur.

A new version of the Alert component is now available. It is a significant upgrade over the previous version, with new options to customize alert messaging.

You can create custom alert states that represent different alert types or severity, and configure them with the following options:

• Title and description.
• Icon, icon position, and tooltip.
• Action text to trigger event handlers on click.

Existing apps can continue to use the previous version, which is now deprecated.

Retool Mobile now supports the use of ProGlove scanners with Android devices. Once configured, you use the ProGlove mobile component to capture events from, initiate pairing with, and disconnect from ProGlove scanners.

Retool now supports Amazon SQS. You can use the Amazon SQS integration in Retool Apps and Retool Workflows to send, receive, and delete messages from a queue. This integration enables you to respond to events as they occur, triggering changes and actions in your workflows or apps.

Retool now enables you to test your custom single sign-on integration with the click of a button. When you click the Test Connection button on the Single Sign-On (SSO) > Custom SSO settings page, Retool checks that the proper groups are mapped, the right user metadata is sent from your identity provider, and the integration works seamlessly. Testing this connection does not change the current user's permission groups, and you won't be locked out if SSO is misconfigured.

Retool now supports Apache Kafka. You can use the Kafka integration in apps and workflows to produce, consume, or commit messages to a topic. This integration enables you to respond to events as they occur, triggering changes and actions in your workflows or apps.

Subfolders is now available to all users on cloud instances and self-hosted instances on versions 3.93 and later. Subfolders helps you manage and organize your Retool apps, workflows, and resources. To implement proper inheritance for security measures, we also now enforce the following:

• A child subfolder or app must be at least as permissive as its parent.
• In order to move an object, you must have Own access to the object (App or Folder) being moved and Edit or Own on its destination.

In making changes to certain groups’ folder permissions, this means some users may no longer create apps inside of folders. Access to any existing apps or modules has changed. You can always update your group settings to enable app creation within folders.

Dynamic queries enable users to access several different resources from a single query. These queries decrease the maintenance burden for apps that need to query various similar resources.

Some example use cases for dynamic queries include:

• An app for your support team to interact with customer data when every customer’s data is hosted on a standalone database with unique credentials.
• An admin panel to measure the health of customers’ deploys when every customer has their own tenant.
• A generic budget dashboard for client projects when every client has their own database.