Release Notes > Release Notes for ThingWorx Platform 9.0 > Fixed Issues in ThingWorx Platform 9.0.3
Fixed Issues in ThingWorx Platform 9.0.3
The following bug fixes are part of ThingWorx 9.0.3.
Bug Fixes
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.
ThingWorx High Availability Clustering
Due to changes to data classes used by Apache Ignite, upgrading your ThingWorx high availability cluster to 9.0.3 requires a full cluster restart. You cannot perform a rolling upgrade. For more information, see Upgrading ThingWorx High Availability Clustering.
Tracking Number
Fixed an issue that was preventing an Industrial Gateway value stream from being exported.
Fixed an issue that was preventing an Industrial Thing from connecting to Kepware.
Fixed an issue that was causing an upgrade from 8.2 to 8.5.3 on PostgreSQL to get stuck waiting on database queries.
Fixed an issue that was causing the Edge to get flooded with synchronizeState events corresponding to actions performed before the Thing was connected.
Fixed an issue with the ExtractZipArchive service that was causing an error when extracting files with special characters in the file name.
Mashup Builder
Tracking Number
Fixed an issue with the Slider web component that was preventing the StepSize property from working if it was set less than 1.
Fixed an issue that was causing memory leak on browsers when using the Collection widget with the Auto-Refresh widget.
Fixed an issue with the List widget where the display field was empty when binding data from the globe session infotable property.
Fixed an issue with the Date Time Picker widget that was causing an error with the date format in Chinese.
Known Issues and Limitations
The following items are known issues and are scheduled to be fixed in a future release.
Tracking Number
Nested infotables that are two or three infotable levels deep return blank values for the selected nested row after upgrading.
If a session property of basetype Number with a value of zero is bound, it returns a JSON instead of null or zero.
In High Availability mode only, when ThingWorx is configured to work with SCIM and there are only nested groups, it may be possible that some groups will not contain all members.
The number primitive supports positive and negative infinity along with NaN as legitimate number values. ThingWorx does not prevent the persisting of these values; however when running one of the Query Property History APIs on a value stream, a run time exception is generated if an infinity value would meet the query parameters.
A custom service derived from the CreateEquipment service sometimes fails to create value streams for newly-created assets.
After PLCs are disconnected for an extended period of time, and then reconnected, a race condition can result. The race condition effects a binding failure with Kepserver which causes the Quality Property Tag values to lose referential integrity and become stale.
Tracking Number
Data Shape fields are not being created when creating a Data Shape using the remote service binding interface in Composer.
Mashup Builder
Tracking Number
The data export widget does not work in run time for Android and iOS.
The configure bindings screen for events shows all event bindings, even if they were not set, instead of the actual bindings.
There is an issue with Composer which causes the Collection widget to fail when attempting to use an infotable as a mashup parameter.
Was this helpful?