Release 337 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
Connectors
- In the Connector details side panel, there is now an Edit button to manage connector metadata (name and description) and environment settings.
- Connectors and connector functions can now be sorted according to their name, last updated date and type (for connectors only).
Enterprise Authentication
- SCIM implementation now supports Bearer token authentication, enabling it to be used from identity providers that require a Bearer token, including Microsoft Entra.
App Editor
- When enabled by Tulip, User data is excluded from the Expression Editor to improve app trigger editor performance.
- In the trigger editor for device triggers, the output selection UI is now a basic dropdown with two options: "this station" and "specific device". Choosing the latter will prompt an additional dropdown to select the device. This update also applies to the "Run device function" action. All existing triggers will be converted into this new multi-dropdown format.
Machine Data Source
- Added a help link for editing MQTT datasources to provide quick access to documentation.
Bug Fixes
Release 337 contains multiple bug fixes:
| Referenced Ticket | Description |
|---|---|
| PLAT-47463 | Fixed an issue where invalid port values (and conversion errors) prevented connector configurations from being edited. |
| PLAT-47359 | Fixed a bug where the "Use customer prompt headers" option could not be disabled in the HTTP connector environments configuration. |
Full List of Ticket IDs included in Release 337
PLAT-47530
PLAT-47463
PLAT-47443
PLAT-47408
PLAT-47359
PLAT-46695
PLAT-42303
PLAT-38656