Release Notes > Version 8.2 Release Notes > Version 8.2.0 Release Notes
Version 8.2.0 Release Notes
The following feature enhancements and bug fixes exist in ThingWorx 8.2.0:
* 
Due to security updates, a minimum version of Apache Tomcat 8.0.47 or 8.5.23 should be used with ThingWorx.
* 
For information about PTC's reaction to the Meltdown and Spectre security vulnerabilities, see
Enhancements
Platform
Included information about opting out of metrics reporting. For more information, see the ThingWorx Metrics Reporting Services Configuration section in the Platform Subsystem help topic.
The Script Error Log has been added to improve error logging for scripts.
Added support to allow mashups to be rendered using jQuery 3.x runtime.
Query service optimization. This includes improved performance for the QueryPropertyHistory and QueryPropertyNamedHistory services. Previously, a database call was made for every logged property. With this improvement, one database call is made for all logged properties, resulting in the following improvements:
A ~20% decrease in memory usage for the QueryPropertyHistory and QueryNamedPropertyHistory service queries if no filters are applied (PostgreSQL and MSSQL).
Decreased time to execute query (~10%) for the QueryPropertyHistory and QueryNamedPropertyHistory services. Depends on latency to the database (PostgreSQL and MSSQL).
Additional decrease in memory, based on the filter supplied during the query for QueryPropertyHistory and QueryNamedPropertyHistory services. (PostgreSQL and MSSQL). If a filter is applied that reduces the record count by 50%, then there is an additional 50% decrease in memory usage on top of the other 50% described in the first point.
A ~20% decrease in memory usage for the QueryPropertyHistory and QueryNamedPropertyHistory service queries if no filters are applied (PostgreSQL and MSSQL).
Decreased time to execute query (~10%) for the QueryPropertyHistory and QueryNamedPropertyHistory services. Depends on latency to the database (PostgreSQL and MSSQL).
Additional decrease in memory, based on the filter supplied during the query for QueryPropertyHistory and QueryNamedPropertyHistory services. (PostgreSQL and MSSQL). If a filter is applied that reduces the record count by 50%, then there is an additional 50% decrease in memory usage on top of the other 50% described in the first point.
This optimization also results in an approximate 10% decrease in memory for single property queries.
The Audit Subsystem has been added. It supports the following capabilities:
Automatically add audit entries to online storage.
Search for audit entries (use the QueryAuditHistory service) stored online.
Archive online audit entries to offline storage (automatically performed daily by default).
Export audit data, using the language selected for the export.
Purge online audit data on the basis of a specified number of days for audit data to remain online and also on the specified number of rows to keep online
Clean up archived audit data automatically, based on a configured schedule.
The security of the PASSWORD base type has been enhanced and is now encrypted.
* 
Previous to ThingWorx 8.2, the Java SDK and Android SDK had the capability to receive passwords and included libraries to decrypt the passwords once the encrypted values hit the Edge. With this change, the encrypted values cannot be received, nor decrypted. If a Password base type value is sent to the edge, it will trigger an error in the Java and Android SDKs when the edge attempts to decrypt the password. See Passwords for more information.
Added the Collection Widget, which allows you to replicate/repeat mashups and content by using infotables to dynamically supply visual content and data.
Additional capability has been added to New Composer . For more information, refer to the ThingWorx Community blog.
The licensing process has been improved. An activation ID is no longer required to obtain a license and a new license file is not required for minor or major release upgrades.
For connected scenarios, activation IDs are no longer required in the platform-settings.json file.
For disconnected scenarios, go to the enhanced PTC Support site pages, select the product, enter a Device ID, and retrieve a license.
You can enable the Application Key Authenticator when SSO is enabled by editing the sso-settings.json configuration. For more information, see Configure the sso-settings.json File.
The CSS Editor was added to Mashup Builder, which allows developers to create modern experiences with responsiveness, animations, and advanced styling and behaviors.
Added support for "Store and Forward" functionality to the interface between KEPServerEX and the ThingWorx platform. KepServerEX can be configured to store updated property data to disk when disconnected from the ThingWorx platform and will send that data gracefully when the connection is re-established.
In mashups, row and column gadget sizes 1 to 8 are now available. TW-25477
Help Center
The Search feature within the Help Center now includes the API Documentation.
Bug Fixes
Platform
Related JIRA
Fixed an issue with Thing Shapes when editing subscriptions twice before canceling or closing in which the second edit was not saved.
TW-28718
Fixed an issue that was causing SQL Server apparent deadlock exceptions.
TW-28208
Added useful log information for troubleshooting LDAP and Active Directory errors.
TW-23873
Fixed an issue with exception handling in DSL Processor in which line numbers were not included in the log.
TW-18042
TW-17255
Fixed an issue in which opening/closing brackets are not highlighted if there were 100 or more lines of code in a JavaScript service.
TW-12740
Mashup Builder
Related JIRA
Service error notification messages were fixed to display on multiple lines based on line breaks in the message.
TW-24738
Fixed an issue in which a master mashup header image was not fully displayed.
PSPT-3365
Extensions
Related JIRA
The Google Maps JavaScript API was updated to prevent the use of the library without an api key. If you are using the Google Map extension in your application, verify that the extension's metadata.xml file is updated with the correct URL (https://maps.google.com/maps/api/js?sensor=false&key=YOUR_API_KEY). Re-zip the extension and reimport into ThingWorx after making this change.