Changelog

Concurrent developer warnings​

• Added a notification to the header that shows who else is modifying the same Retool app.
• You can use this to avoid overwriting changes that your team mates are making to the Retool app.

Deleting apps​

• Added ability for admins to permanently delete apps that are in the archive folder.

New​

• Added the option to specify the ACL for files uploaded to Google Cloud Storage
• Added option to allow users to define custom values in Multiselects. Enable this by using the "Allow user defined values" option in Multiselects.

Resource access levels​

• Extended the access control levels in Retool to allow admins to restrict access to Resources connected in Retool.
• You can use this feature to do things like:
  • Only allow analysts to use readonly database connections.
  • Only allow developers to use apis / databases that they manage.

Here, the group lets the "Awesome Intern" use the onboarding_db (readonly) and onboarding_api resources to create / modify apps

Query playground​

• Added the Query Playground which lets developers write queries quickly without having to create an app.

• Coming soon: reusing queries you write in the playground within your Retool apps.

Tile homepage view​

• Added a new tile-based home screen for Retool apps
• You can customize the image you use for each tile.
• You can also "favorite" your most frequently used apps so that always appear at the top of the page.

New​

• Added support for deleting S3 files.
• Added support for S3 bucket URLs in APIs that use the AWSv4 authentication method.
• Increased maximum timeout for queries to 10 minutes.

Fixed​

• Fixed how custom redirect flows in "Custom Auth" APIs work in "staging" environments.
• Fixed POST/PUT/DELETE requests in the Stripe integration that have an empty body.

Query Caching​

• Added query caching as a way to optimize the performance of Retool apps.
• Queries can have its results cached for up to one day (the cache TTL)
  • The first time you run a cacheable query, it will run the query normally and then remember the query result.
  • Anytime anybody runs the query again the remembered result gets returned instantly.
  • The remembered result is deleted after the cache TTL expires.
• You can configure this option in the "Advanced options" section of the query editor.

Retool community!​

• Visit the community forum to join the community 🙂

New and Improved​

• Added lastUploadedFileName to the S3 Uploader component. Works similarly to the lastUploadedFileUrl.
• Added live warnings to make it easier to write Javascript scripts.
• Added a utils.downloadFile function to Javascript scripts. Use this to with API queries that return pdfs / docx / xlsx / etc. to download the files returned. Docs here.

Fixed​

• Changed the MongoDB insertOne queries to also return the created object, including the MongoDB _id.
• Fixed deadlink on the Permissions dashboard.

RethinkDB Integration​

• Added RethinkDB as a Retool integration.
• Run get, insert, update, delete, and find queries on your database.
• Let us know what else we can add.

Lambda Integration​

• Added AWS Lambda as a Retool integration.
• Invoke lambda functions with whatever payload you need.
• See more info in our docs here.

Improved​

• Added support for sharded Microsoft SQL Server databases.
• Improved the user management screen in Retool. Disabled users are greyed out, and we show accurate last active dates for each user.

Fixed​

• Fixed how Custom Auth API integrations work in staging environments
• Fixed how non-string values are passed in FormData API requests.
• Fixed error that Slack webhooks would return in on premise Retool.
• Disabled overly aggressive cache headers in on premise Retool.
• Fixed editing JSON columns in editable tables.

Filter Audit Logs by User​

• The Audit Logs can now be filtered by users as well.

Firestore References​

• Firestore query by reference / inserting and updating references.
• Here's an example of how to specify that a string should be a "reference" type:

• Inspired by the MongoDB Extended JSON syntax, you use $ref to specify that the string should be a ref. In any place where you might be a normal value you can now use the following to refer to a reference.

{ $ref: "collection/documentId" }

Misc​

• The moment-timezone library has been added to Retool. You can now use expressions like {{ moment.tz('2019-10-10 13:43', 'America/New_York').toISOString() }} to convert dates in different timezones

Performance Improvements​

• We've optimized filtering through the audit logs that Retool collects so that you can now efficiently trawl through all the queries that your users have run in Retool.
• Apps should now start up between 1-2s faster on average.
• Tables are more efficient when rendering large amounts of data.

Disabled Controls​

• Every control in Retool now can be dynamically disabled
• This includes Text Inputs, Dropdowns, MultiSelects, RadioGroups, Checkboxes, Checkbox Groups, Button Groups, Rating components, and more.

Custom Tooltips​

• Every control can now also have a custom tooltip!

Git Integration​

• Retool supports version controlling and serializing apps to a git repo
• Retool also supports reading and recreating apps from a git repo
• This allows for designing pull-request flows for deploying apps from staging environments to production environments.
• To learn more, see the documentation.

Permissions Redesign​

• The entire UI for interacting with users, groups, and apps have been modified for more clarity.

Fixed and Misc Features​

• Components in modals will render with the correct sizes in Firefox.
• We've added a Date Time column type to Tables.
• Deleting components will automatically trigger a save point in Retool.
• You can now trigger queries when checkboxes are switched on and off.
• MongoDB validations for field, limit, and skip have been fixed.
• Retool apps now live on /apps instead of /presentation
• The Retool autocomplete now triggers in more sensible scenarios
• Retool folders are now sorted alphabetically

We're excited to publicly launch Retool. We usually update our changelogs every 2-3 days so be sure to check here often!

We'll be following semantic versioning https://semver.org and we'll be careful to annotate any potentially breaking changes that we release.

For our on-premise customers we'll also be posting the version numbers of all our releases.