Platform Release 311 - March 2025

Article summary

Did you find this summary helpful?

Thank you for your feedback!

Release 311 brings updates to several features and bug fixes throughout the platform.

Let us know your thoughts and questions in the Tulip Community.

Features and Improvements

Customers with multiple workspaces can now use the workspace name and id app info properties (usable in triggers, expressions, and as datasource in the variable widget).
Radio buttons and checkboxes have a new look across the platform.

In r320 / LTS 15, some App trigger expression functions will begin failing if they are incorrectly configured. This change affects the functions {{ROUNDDATETIME}}, {{TEXTTODATETTIME}}, {{ADD_TIME}}, and {{SUBTRACT_TIME}}. In r320 / LTS 15, if these functions are configured with an invalid timezone or datetime, they will throw an error, causing the trigger to fail. Until then, the trigger will not fail, but it will show an error toast to notify the operator that there is an expression that needs to be fixed. These changes will help prevent faulty data from being created by these functions.

Release 311 contains multiple bug fixes:

Referenced Ticket	Description
PLAT-42725	Fixes a bug in import v2 which allows for the creation of improper column names when importing links, locking out further updates to the affected tables.
PLAT-42794	Fix issue where unpublished apps could not be run if the station is assigned to run "most recently published version" of the app, while the station group is assigned to run the dev version of the app.
PLAT-42327	Fix custom widget triggers showing the wrong datasources in the expression editor when switching between different triggers.
PLAT-42410	Fix bug where the "Run in player" button of the app editor would not work as expected if the player is on the splash screen for another app.
PLAT-34955	Fixes a bug where 'Viewer (with Player access)' role is able to be selected when creating a new user and SAML is active
PLAT-38574	When issuing two delete requests for the same record, the second one will now return a 204 (to represent a delete being an empty operation because the record doesn't exist) rather than a 500 (server error).

PLAT-42794
PLAT-42725
PLAT-42558
PLAT-42410
PLAT-42327
PLAT-42224
PLAT-38574
PLAT-34955
PLAT-18615

Was this article helpful?

Table of contents