Release 371 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
- The API reference for the create user endpoint now documents the existing
429 Too Many Requestsresponse and notes that the endpoint is rate limited to 30 requests per minute.
App Editor
- In the App Editor, removed the Grid widget's right-click context menu. All operations previously available through this menu remain accessible via the Widget tab in the side pane.
General Improvements
- Platform improvement to ensure operator session data is consistent after logout.
Widget
- Improved the performance of the Interactive Table Widget when displaying large variables.
Bug Fixes
Release 371 contains the following bug fixes:
| Referenced Ticket | Description |
|---|---|
| PLAT-54440 | Fixed an internal configuration issue that could cause MQTT WebSocket connections to fail. |
| PLAT-54376 | Fixed an issue where users with a custom user role that has "Configure edge devices" (full access), but not "Development mode access" could receive an error when accessing the driver configuration page. |
| PLAT-54130 | Fixed an issue across multiple features (Tulip AI, Connector functions "where used" in Triggers, and the App Editor) where fetching a table aggregation could return a 500 error message. |
| PLAT-54044 | Fixed an issue where reloading the Player on during startup could cause the previous session's logout or app cancellation to be skipped and the operator to be marked as still online. Now, logout and app cancellation complete on the next startup. |
| PLAT-53976 | Improved app performance when updating variables in apps that contain large amounts of data. |
| PLAT-53645 | Fixed an issue where testing an unverified connector would show an "executable config not found" error. Now, users will see an unverified connector error instead. |
| PLAT-52045 | Resolved an issue on Mobile Player where, if an operator backgrounded the app for more than 10 minutes, the Player would automatically refresh on return. In instances configured with Validation Mode (or "Cancel apps on logout") combined with inactivity logout or logout-on-close, this refresh could cause the operator to be placed at their last step before the completion rather than starting a fresh session — meaning that if they ran the app through to the end again, that second completion would not be recorded. Customers who do not use Mobile Player, or whose instances are not configured with the above settings, are not affected. |
| PLAT-51102 | Fixed a bug where automations with object variables containing the property "language" could not be saved or published. |
| PLAT-47807 | Fixed an issue in the CSV export of users, where the field "Last Online" could be blank for instances with a large number of users. |
Full List of Ticket IDs included in Release 371
PLAT-54440
PLAT-54376
PLAT-54196
PLAT-54130
PLAT-54044
PLAT-53976
PLAT-53871
PLAT-53645
PLAT-53584
PLAT-52937
PLAT-52045
PLAT-51102
PLAT-47807