Release 384 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
Automations, Functions
- In Automations and Functions, the "Contains" and "Does Not Contain" conditions can now check whether a list contains a value. Previously, these conditions could only check whether text contained a substring.
Bug Fixes
Release 384 contains the following bug fixes:
| Referenced Ticket | Description |
|---|---|
| PLAT-57557 | Fixed an issue on Azure-hosted instances where importing or exporting an app would stall and then fail after several retry attempts. |
| 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-57384 | Fixed a bug where HTTP connector functions failed when a File or Image URL input pointed at a file stored in Tulip. |
| PLAT-57329 | Fixed an issue where analysis widgets with a changing filter value could ignore the refresh interval and re-run the query repeatedly, adding load that could slow the instance. |
| PLAT-57283 | Fixed an issue with forwarding logs externally from the on-premise Connector Host to Datadog and Splunk. Previously, configuring either destination prevented the Connector Host from starting. |
| PLAT-57190 | Fixed an issue with fowarding logs externally from the on-premise Connector Host to a Grafana Loki endpoint. Previously, configuring a Loki endpoint prevented the Connector Host from starting. Additionally, forwarded logs are now also labeled with the instance name. |
| PLAT-57008 | Fixed a bug where comparing app versions showed a trigger as changed if the app referenced a function containing a connector function snapshot, even if the function had not changed. This fix applies to newly published versions and does not apply to previously published versions. |
| PLAT-56934 | Fixed an issue where importing an app that used a legacy connector snapshot didn't reuse the original connector ID and could point the imported connector function to the wrong development version. |
| PLAT-56440 | Fixed a bug where importing a function or automation that used a table with a linked record could break a downstream "Get table record" action, and show a "Results changed, must be updated" warning. |
| PLAT-53299 | In the Player, fixed a bug where canceling a sign-out could prevent the operator from signing out again for the remainder of the session, requiring them to reload the Player. |
| PLAT-49285 | In Functions and Automations, traces now use table field names when rendering inputs and outputs. Previously, some actions displayed internal IDs instead. |
| PLAT-43683 | In the trigger editor, fixed a bug where configuring a Run Function action could link to an out-of-date version of that function until the page was refreshed. |
Full List of Ticket IDs included in Release 384
PLAT-57557
PLAT-57438
PLAT-57426
PLAT-57384
PLAT-57329
PLAT-57283
PLAT-57190
PLAT-57008
PLAT-56934
PLAT-56440
PLAT-53299
PLAT-49285
PLAT-43683
PLAT-23354