Release 347 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
Import/Export V2
- Fixed issues related to table aggregations (TAs) and table queries (TQs):
- Fixed an issue where, upon app import or app restore, TAs might have appeared broken in the app editor records tab. Now we will differentiate between TA development versions and snapshots.
- Fixed an issue where in rare edge cases, an app could incorrectly use multiple versions of the same TA, leading to inconsistency. Apps that were previously in this state will now reference the most recent version of the aggregation that was in use in the query, preferring snapshots.
From now on, to support the accurate deduplication of table aggregations and queries for Import/Export v2, the import behavior will change slightly as follows:
- A TA or TQ will import as a development version.
- A TA or TQ will import as a snapshot if it already exists in the target (e.g. workspace, instance) and has a different configuration.
Learn more here.
Custom User Role
- In Custom User Roles, the App Import and App Export permissions are now split into two separate permissions. This was a request from our Community members here!
Bug Fixes
Release 347 contains multiple bug fixes:
| Referenced Ticket | Description |
|---|---|
| PLAT-49244 | Fixed a bug causing the connector host to crash when attempting to connect to an OPC UA server configured with an invalid URL. |
| PLAT-48949 | Fixed an issue where if an error occurs after generating a completion, but before cancelling or completing, the app could prevent future app completions from saving. Now, the operator is taken to the splash screen if this error occurs. |
| PLAT-47989 | Fixed an issue where a broken record placeholder in an app caused an error when reading completions and 500 errors in the Record History Widget. |
Full List of Ticket IDs included in Release 347
PLAT-49244
PLAT-48949
PLAT-48714
PLAT-47989
PLAT-45434