Release 375 contains updates to several features and bug fixes throughout the platform.
Let us know your thoughts and questions in the Tulip Community thread.
Features and Improvements
API, Triggers
- Backend improvement to the app editor service. This update does not change the behavior of triggers or widgets, but includes the following minor improvements:
- Success and error notifications are clearer for undo, copy, cut, and paste.
- Default names are more consistent when copying, cutting, pasting, or duplicating widgets and triggers.
- Triggers are created on paste, instead of only on save, and appear immediately in the triggers list.
- When pasting triggers that contain translated text into apps without translations enabled, the user will see an error message.
- If a user alt-drags base layout widgets while not on the base layout step, only the widgets belonging to the current step are cloned and dragged.
Automations, Functions
- Invalid regular expressions in the function conditions "Matches Regular Expression" and "Doesn't Match Regular Expression" now surface specific, user-friendly errors. This change only applies to functions and automations.
Connector, Connector Environment, Connectors Page
- Editing a connector configuration now shows a loading indicator while the configuration is retrieved, so changes made while loading are no longer lost.
Copilot
- The default Tulip AI agent in the Agent Chat widget can now search table records and read text from files and PDFs attached to table records. Note: reading file and PDF content requires document processing (embeddings) to be enabled on the table.
Tulip Platform
- Errors (e.g. when logging in or registering an interface without the required role) now direct users to contact their Tulip administrator. Previously, users were shown a generic message.
Bug Fixes
Release 375 contains the following bug fixes:
| Referenced Ticket | Description |
|---|---|
| PLAT-55639 | Fixed an issue where Japanese translations for certain phrases (i.e. stations) were incorrect or misleading. |
| PLAT-55445 | Fixed an issue that could cause OAuth-based connectors to fail during token refresh when the authentication provider returned {expires_in} in an unexpected format. |
| PLAT-55271 | Fixed an issue where MQTT connector functions could fail with an HTTP 500 error. |
| PLAT-55270 | Fixed an issue related to API usage where certain delete operations could proceed even when the user did not have the required permissions. |
| PLAT-55245 | Fixed a bug in Developer Mode where table records created during a test session could not be linked to other records. |
| PLAT-54472 | Fixed an issue where files and images sent through connector functions in form requests were missing their file type multipart/form-data information. Each file is now sent with the correct type, so downstream systems can process it properly. |
| PLAT-54403 | Fixed a bug where multiline input widget labels were not being translated when using "Translate with AI" to translate an app. |
| PLAT-54359 | Fixed a bug where a connector function could still send a request-body parameter after that parameter was removed or renamed. This could happen when a function was duplicated, edited, and exported to another instance, where the exported copy could continue requesting the old parameter instead of using its current definition. |
| PLAT-50136 | Fixed an error where, when audit history is enabled, table records with IDs longer than 255 characters could not be created. |
Full List of Ticket IDs included in Release 375
PLAT-55639
PLAT-55445
PLAT-55271
PLAT-55270
PLAT-55245
PLAT-55174
PLAT-54961
PLAT-54749
PLAT-54472
PLAT-54403
PLAT-54359
PLAT-53930
PLAT-51464
PLAT-50136