Retool updated the custom component support library to version 1.9.0, which adds a new verbose option with deploy and sync commands. When running into unknown failures, you can add the -v option to deploy and sync commands to print more detailed errors for help with debugging.

This library is automatically included as a dependency of the custom component collection template repository. Existing users can run npm update @tryretool/custom-component-support to get the latest version with these updates.

Organization admins can now control whether users can create draft apps on a per-group basis. If an admin disables the draft apps feature on a permission group, users within the group will not be able to create unpublished apps in their own drafts folder.

Modules now support typed data inputs. This change makes your modules more reliable by catching mismatched data types early.

Previously, modules offered only a Data input for passing in property values. Now, you can choose from the following options when configuring a module input:

• Any
• String
• Number
• Boolean
• Enum

Choose from String, Number, Boolean, or Enum for type validation on your module input. Selecting a Type enforces stricter validation rules and displays a warning if the input type does not match what you selected. You can also define additional characteristics about the input, such as options for Enum, and default values for all types.

If you set the Type to Any, Retool performs no validation on the module input.

Organizations on the Business or Enterprise plan can now restrict users from accessing specific app pages with per-page permissions. When configuring a permission group, you can now also specify permissions for each page.

Retool has rolled out unique identifiers (UUID) for app pages. If you use Source Control, Retool recommends that you create a new branch with no changes and push it to Source Control. If you use Retool Cloud or self-hosted Retool 3.191-edge or later, Retool automatically creates a migration commit to add UUIDs to each page. Once you merge this commit, you can successfully configure per-page permissions on your protected app.

Retool added two new configuration settings that enable you to customize the layout of modules:

• Height: Whether the default height of the module is automatic or fixed.
• Overflow: Whether overflow content in the module is hidden or accessible via scroll.

When you configure these settings inside the module editor, the settings apply as the default values only to new module instances. Existing module instances are unchanged. You can also override these settings for a single module instance by changing them in the Inspector of the app that contains the module.

Retool recently made changes that make it easier to review changes in source control. Retool now separates system-generated updates related to version upgrades into their own migration commit, so your pull requests are cleaner and easier to understand.

This feature is generally available on Retool Cloud. It is available in private beta to Self-hosted Retool organizations on edge version 3.203.0-edge or later, and will be generally available in an upcoming stable release. Self-hosted Retool organizations can reach out to support to enable this feature.

What's new​

Instead of bundling migration changes with user changes, they now appear in a dedicated commit.

No setup needed—this happens automatically when you make commits.

Retool renamed the Chat component to LLM Chat to provide more clarity on the purpose of the component. No user action is required.

Retool can record user behavior and interactions with apps using Fullstory. When enabled, data about user interactions with apps are reported directly to Fullstory for you to review in detail. You can then analyze app analytics, evaluate impact, and review interactions with session replay. This integration is useful for monitoring user activity across different apps, and using advanced analytical tools like heatmaps and funnels to identify usage patterns, debug errors, and improve the overall user experience.

Retool updated the Export to Module feature for usability improvements. This feature allows you to select components on the canvas and “refactor” them into a module.

The following key changes were made:

• You can now export a single component to a module. For example, you could export a single container (and all its children) to a module.
• When making the export, all the related logic, such as queries, variables, and transformers, is automatically included in the exported module. This eliminates the need to manually copy logic to the module.
• Once the export is complete, Retool automatically replaces the selection with the newly created module. This eliminates the need to import the module after you export the selection.

Access Export to Module in one of the following ways:

• Select one or multiple components, right-click, and select Export to module.
• Select multiple components and click in the Inspector.