Release 386 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
App Editor
- In the App Editor, the header no longer shows a back arrow next to the app title. Click the app title or the "Apps" breadcrumb to return to the app overview.
App Editor, Widget
- In the Button widget's icon picker, added an exit/sign-out icon, so "Log Out" and "Exit app" buttons can use a matching icon instead of the power symbol.
App Version Comparison Page
- App version comparison now shows when the version of the table query or table aggregation used in an app version has changed.
Connector
- The support grace period for LTS15 connector hosts has been extended by 8 weeks.
Settings - Connectors
- When publishing an app or automation, the behavior to create a snapshot of the connector functions used is now an account setting. Account owners can control it under Account Settings > Connectors > Snapshotting behavior with the "Create snapshot during publishing" toggle. This setting is on by default, but will remain off for instances that previously had this behavior turned off.
Settings - Users, User Role
- On instances where Workspaces is disabled, the role filter on the user settings page now includes a "No Role" option. This allows Account Owners to find users who have no role and assign them one. Previously, users with no role could only be found through the Workspaces filter "Unassigned" option, which isn't available when Workspaces is disabled.
Widget
- Improved the interactive table widget performance where, if the table was configured with a large Rows per Page value, selecting a record in the widget caused a delay before an app transition.
Bug Fixes
Release 386 contains the following bug fixes:
| Referenced Ticket | Description |
|---|---|
| PLAT-57830 | Fixed a bug where, on instances with Workspaces disabled, a user's profile page showed "Operator" in the role dropdown when that user had no role assigned. The dropdown now correctly shows that no role is assigned. |
| PLAT-57779 | Fixed an issue where Oracle connector functions could fail with an "Invalid key length" error when a connector host opened several Oracle connections at the same time. This affected sites with Oracle accounts created under different password verifier settings. |
| PLAT-57516 | Fixed an issue with the connector permission check. Now, moving a connector between workspaces requires permission to remove connectors from the workspace the connector is currently in. |
| PLAT-57438 | Fixed a bug where app builders could not create or save triggers on a Speech-to-Text input widget. |
| PLAT-57426 | Fixed a bug where, in rare cases, a connector function that completed successfully could be reported as timing out because its result was not received by the platform. |
| PLAT-57397 | Fixed an issue where the Player could briefly show a login screen on startup even when already registered. If a user logged in on that screen and proceeded with registration, the Player could be re-registered, deleting the previously registered interface. |
| PLAT-57384 | Fixed a bug where HTTP connector functions failed when a File or Image URL input pointed at a file stored in Tulip. |
| PLAT-57371 | The "Refresh machine secret" action is no longer offered for Connector Hosts running on Tulip Edge devices. Those devices manage their own machine credentials, and refreshing the secret from Account Settings would have left the Connector Host disconnected until it was re-provisioned. The action remains available for self-hosted On-Premise Connector Hosts. |
| PLAT-56720 | In the Player, fixed a bug where a table query using both an "is in" filter and a "contains" filter on the same field would return no records if the "contains" value was an empty string. Table queries with both filters now return all records matching the "is in" filter. |
| PLAT-56676 | Fixed a bug where a connector host could keep polling and reporting machine attributes after their mappings were deleted or their data source was reconfigured, until the host was restarted. |
| PLAT-54275 | Fixed a bug where machine attribute data could stop being recorded if the connection to Tulip's internal message broker dropped while a message was awaiting confirmation. Processing would stall indefinitely while the service continued reporting as healthy. Publishing now fails with an error and processing continues instead of stalling. |
| PLAT-54271 | Fixed a bug where machine and device events could stop reaching app triggers after an interruption to Tulip's internal message broker, such as a broker node restart. Event delivery stopped silently: no error was raised, and the service continued reporting as healthy. Tulip now detects the interruption and automatically restores event delivery. |
| PLAT-52139 | Fixed a bug where the "create and load table record" trigger action reported a failure in the Player despite creating the record, which could result in duplicate records when operators retried. |
Full List of Ticket IDs included in Release 386
PLAT-57963
PLAT-57830
PLAT-57779
PLAT-57728
PLAT-57516
PLAT-57467
PLAT-57438
PLAT-57426
PLAT-57397
PLAT-57384
PLAT-57371
PLAT-57318
PLAT-57100
PLAT-56720
PLAT-56676
PLAT-54275
PLAT-54271
PLAT-52139
PLAT-51143
PLAT-48871