Release 293 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
App Version Comparison Page
- Show a message to the user about inaccuracies with triggers for version comparisons before LTS12
Automation Run History Page
- Previously, Automations run history would present SQL connector function failures resulting from misconfigured database connections or malformed SQL as internal server errors. Now, the run history uses more specific language for these errors.
Connector Function, Connector Function Editor
- Allow letters from any languages, numbers, spaces, underscores and dashes for Connector function inputs and outputs.
Dev Mode, Player
- In Dev Mode, when running at a real station, the station's station group will now have its app assignments included in the change app menu.
General Improvements
- In the icon picker in the app editor, updates the names of several icons to be clearer and easier to locate.
- When viewing apps and app folders either in station assignments on the Stations page, or in the Player menu during Change App, they will now see apps and app folders listed in alphabetical order, making them easier to find quickly.
- Adds transition actions to the export trigger logic modal, enabling greater understanding of transitions between apps and steps caused by triggers.
- Adds connector functions to the export trigger logic modal. This will help users understand attributes of trigger actions that call connector functions, such as the connector function name, description, and outputs.
- Users can add external domains to the domain allowlist under user settings.
Player, Stations Page
- Improves page load time for player registration and stations page.
Bug Fixes
Release 293 contains multiple bug fixes:
| Referenced Ticket | Description |
|---|---|
| PLAT-38562 | Fixed an issue with exporting extraneous tulip table queries and aggregations. Previously table queries and aggregation that were used by published apps and referencing archived fields would break the export of the table. Note that exporting published apps that use table queries or aggregations that reference archived fields will still not be able to be exported and in this case either a different app version will need to be exported or the table field restored. |
| PLAT-38415 | Fixed an issue with the record history widget that showed an app pausing as an app cancellation in the completion record. |
| PLAT-38717 | Fixes the issue where custom widget functionality would be blocked if there exists an uncaught error in user's JS code. |
| PLAT-38770 | Fixes an issue with connector host that would create 408-type errors during connector setup. |
| PLAT-38557 | Fixes an issue where a user was unable to run apps despite having the proper permission. |
Full List of Ticket IDs included in Release 293
PLAT-38858
PLAT-38770
PLAT-38751
PLAT-38717
PLAT-38564
PLAT-38562
PLAT-38557
PLAT-38415
PLAT-38299
PLAT-38235
PLAT-38117
PLAT-38101
PLAT-37665
PLAT-37663
PLAT-36958
PLAT-36943