• 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.

• 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 with the GetJSON service that was causing it to fail.

• Fixed an issue that was causing an upgrade script failure when upgrading from 8.2 to 8.3.

• 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.

• 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 Date Time Picker widget that was causing an error with the date format in Chinese.

• Fixed an issue that was causing services to display in the Data tab that did not reflect the services connected to the mashup.

• Nested infotables that are two or three infotable levels deep return blank values for the selected nested row after upgrading.

• 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.

• When running a High Availability (active passive) configuration, the log files are not visible in Composer.

• 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 causes a binding failure with Kepserver that interrupts updating of tag quality and value.

• Data Shape fields are not being created when creating a Data Shape using the remote service binding interface in Composer.

• The data export widget does not work in run time for Android and iOS.