Release 377 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
API Tokens
- API tokens can be granted a dedicated
attributes:writescope that controls writing values to machine attributes in Tulip. Separately, the scope required to report machine attribute values has been renamed from "attributes:write" to "attributes:report". Existing tokens are automatically migrated, so current integrations continue to work.
Connector
- Subdomains are now available for all HTTP connectors without a toggle. The subdomain field is always shown on the connector's configuration page. Each connector function can optionally use its own subdomain, and a connector-level default subdomain is applied to newly created functions.
Connector Host
- LTS15 on-premise connector hosts (OPCH) have entered their deprecation grace period (r377 through r382) on weekly releases. See On-Prem Connector Host Version Support for the full support timeline.
Custom Widget
- Added enforcement where Custom Widgets options appear in the platform when the "Enable Custom Widgets" toggle is disabled. Users can still place, load, and import custom widgets within an app, but the ability to create a custom widget is removed.
Functions
- On the Functions page, added a preview pane that displays details for the selected function.
Bug Fixes
Release 377 contains the following bug fixes:
| Referenced Ticket | Description |
|---|---|
| PLAT-55898 | Fixed a bug where, in rare cases, could cause issues in the Tulip Player after logging out, such as completion records not being recorded. |
| PLAT-55889 | Fixed a bug in Text widgets where a variable-bound color in translated (multilingual) rich text would revert to its default color after publishing the app. |
| PLAT-55837 | Improved the load times of the connector details and connector functions pages on instances with a large number of connectors. |
| PLAT-55808 | Fixed an issue where triggers containing a static datetime or color value could not be saved. |
| PLAT-55232 | On the Account Usage page, fixed an issue where deleted machines still rendered a link that would appear broken. Now, machine names only render as clickable links when a valid destination exists. |
| PLAT-54151 | Fixed an issue with custom user roles where users with the "Apps - Edit only" permission could not be granted "Can edit" access on specific apps. The "Apps - Edit only" permission also now includes the ability to archive apps. |
| PLAT-53615 | Fixed an issue where images and files in apps could fail to load during long app runs. Cached asset URLs that had expired can be reused, as the client now re-validates them against the server before use. |
| PLAT-53157 | Fixed an issue that could cause app publishing, snapshotting, and submitting to fail when an app contained deleted assets that referenced connector functions, functions, or AI agents. |
| PLAT-53076 | Fixed an issue where an app completion containing a Datetime value with an invalid year (ex. "0000") could fail to save, causing the entire completion's data to be lost. The invalid Datetime is now discarded, and the rest of the completion is saved. |
Full List of Ticket IDs included in Release 377
PLAT-55898
PLAT-55889
PLAT-55837
PLAT-55808
PLAT-55785
PLAT-55232
PLAT-54664
PLAT-54151
PLAT-53962
PLAT-53615
PLAT-53157
PLAT-53076
PLAT-38503
PLAT-36855