Release Notes > Release Notes for ThingWorx Platform 9.1 > Fixed Issues in ThingWorx Platform 9.1.6
Fixed Issues in ThingWorx Platform 9.1.6
The following fixed issues are part of ThingWorx Platform 9.1.6.
Fixed Issues
Fixed potential security issues, including items proactively identified by vulnerability scanning software or PTC Quality Assurance testing. Please upgrade as soon as possible to take advantage of these important improvements.
PTC has recently implemented a new support policy with respect to Identity and Access Management (IAM) solutions. Please see the appropriate eSupport center section for more information.
See this technical support article for important recommendations regarding the use and update of third-party software for ThingWorx.
Tracking Number
Made the following updates to the Support Subsystem:
The Support Subsystem is always enabled and cannot be stopped.
The Diagnostic Watchdog is enabled by default.
Changed the runwatchdog filename to runstacktrace.
Added the CreateRunStackTraceFile and RemoveRunStackTraceFile services.
The ownership of an entity can be viewed and set in ThingWorx Composer.
Fixed an issue with the File Transfer Subsystem and related services that was causing performance issues.
Fixed an issue with SSO that was causing the user_model to get updated on every login even if there wasn't a difference in the user.
Fixed an issue that was causing an internal server error in the Application and Security Logs.
Fixed an issue that was causing an anomaly alert to get initialized even if the configuration was set incorrectly in the Alert Processing Subsystem.
Fixed an issue that was causing authentication issues with applications.
Fixed an issue that was causing an upgrade to fail on a Linux system.
Mashup Builder
Tracking Number
Fixed an issue that was preventing the selection event on the Label widget from triggering within the collection.
Fixed an issue that was preventing second level menus from displaying.
Fixed an issue that was preventing text specified for filtering results in a List dropdown widget from clearing even after data bound to the widget was changed.
ThingWorx Flow
Tracking Number
Fixed an issue that was preventing reports from being downloaded.
Known Issues and Limitations
The following items are known issues and are scheduled to be fixed in a future release.
Tracking Number
Entity import sometimes fails with "1,018 Data Store unknown error" when the ID/ entity name already exists in the database.
ThingWorx High Availability Clustering is not supported on Windows OS. To configure ThingWorx to operate in an HA environment in cluster mode, you must run on Ubuntu. If Apache Ignite has connection or network latency issues, you can enable advanced configurations in the platform-settings.json file. For more information, see Troubleshooting for HA Clustering.
When running a ThingWorx HA landscape, if a file transfer job fails due to a time out issue, the job is not cleared from the in memory cache. The reservation ID is not released and you will receive errors trying to remove the job reservation. The job will remain in tracker. If you receive this error, contact PTC technical support.
Mashup Builder
Tracking Number
When the ItemLoad behavior is set to Load/Unload, the Collection widget scrolls automatically.
The JSON mashup parameter type does not pass through data in the advanced tree grid.
The selected text of a dropdown widget is independent if the selection is bound from another dropdown widget. If the selections do not match, it does not revert back to selection the first row (if autoselect first row is enabled).
The Schedule chart is causing memory leaks.
The Grid Advanced does not fill the entire space of a dynamic panel widget when it expands and collapses.
Collection widget re-rendering causes memory leaks and slow responsiveness.
ThingWorx Flow
Tracking Number
When a connector is imported with the same name of an existing connector, but with a different connection type (such as Basic, OAuth named user), a duplicated connector is created instead of ignoring the imported credential. The workaround is to delete the duplicated connector that was created.
Was this helpful?