Release Notes > Version 8.4 Release Notes > ThingWorx Analytics 8.4.5 Release Notes
ThingWorx Analytics 8.4.5 Release Notes
The following sections describe the bug fixes, and known issues in ThingWorx Analytics 8.4.5.
Bug Fixes
Bug Fix Description
Reference #
Analytics Extension: Unable to import into ThingWorx when PTC Navigate is present
Both the Analytics Manager and the PTC Navigate extensions embed the same third-party GSON library but with different versions. This mismatch prevents Analytics Manager and Navigate from running against the same ThingWorx instance. To resolve the issue, Analytics Manager has upgraded to use the 2.8.1 version of the GSON library, which matches the version that Navigate uses.
TA-3333
ThingWorx Analytics: Security Improvements
In this release, security was improved by closing several vulnerabilities. As a result of one security improvement, the Java requirement for ThingWorx Analytics has been increased to JDK 8u141 (64–bit). Earlier versions of ThingWorx Analytics can continue to use any JDK 8.x version.
TA-3852
TW-63169
Known Issues
Known Issue Description
Reference #
ThingWorx Analytics Server: Two-at-a-time Signals request does not return MI for all field combinations
When running a request for Signals, and specifying maxAtATime = 2, Mutual Information (MI), in relation to the goal, is not returned for all field combinations as expected. Instead, individual (one-at-a-time) MI scores are returned for all fields and then are filtered down to the top 25% most relevant fields. Two-at-a-time signals are calculated only for those fields. There is currently no way to modify this filtering behavior.
TA-729
Analytics Manager: An existing simulation event fails if it is triggered after server restart
Analysis agents must be restarted after a ThingWorx server restart. Without restart of the agent, any new simulation jobs will fail to execute.
Analytics Manager: Time window event does not work for non-time series models
When a non-time series model is uploaded using the Analytics Server Connector, and all of the properties, including the key field are mapped, a time window event does not work.
AM-1289
Analytics Manager: The Replay progress bar does not update as expected
When a replay event is executed, the on-screen progress bar does not update as the replay event progresses. The issue is related only to the user interface (UI), and the actual execution of the replay is not affected. As a work around, refresh the browser or navigate to another tab and then return to the Replay tab. The progress bar will update. This UI issue will be resolved in a future release.
TA-1345
Analytics Builder: Filtering on list pages does not work as expected
When filtering is applied to a list page with multiple pages (such as the Models list page), the filtered results are not aggregated for display on a single page. Instead, the filtered results remain on their original pages and multiple pages must be clicked through to find all the filtered results.
To improve handling of list page displays, a configurable parameter has been added to set the number of table items that can be displayed per page. A more permanent resolution for the filtering with pagination issue will be provided in a future release.
TA-1596
TA-1618
TA-1928
ThingWorx Analytics Server: Some datasets with a large number of columns fail to upload
There are currently some limitations on the size and number of columns a dataset can contain. These limitations depend on the mix of data types your data includes. For specific information, see the Data section of Prepare Data and Metadata.
When trying to upload a dataset with a large number of columns, if the upload fails and an error message is generated, try the following workarounds:
Where possible, use optimal data types, for example, convert INTEGER data to STRING and use DOUBLE for numeric data.
Reduce the number of columns.
TA-2599
ThingWorx Analytics Server: When dataset or metadata field names begin with a number, server queries fail
When a field that begins with a number is included in a dataset or in metadata, most Analytics Server jobs can run successfully, such as training a model, running or scoring. However, when a server query is executed, such as a BinnedDistribution, the query fails. As a work around, avoid using field names that begin with a number.
This issue will be resolved in a future release so that field names can begin with numbers.
TA-2795
TA-2799
ThingWorx Analytics Server Installer: Silent mode installation error
The Analytics Server installer should not allow installation of Analytics Extension without Analytics Server. In both graphical and text mode installations, a warning message is displayed when the Analytics Extension component is selected for installation but Analytics Server is deselected. The installer will not continue unless Analytics Server is also selected. However, in the silent install mode, no such warning is displayed and the installer completes successfully with only the Analytics Extension installed. Of course the Extension cannot run without the Analytics Server so it is not usable.
This issue will be resolved in a future release.
TA-3231
End of Life Information
ThingWatcher
ThingWatcher was discontinued as a standalone SDK in 8.3. However, ThingWatcher functionality is available in the Anomaly Detection features native to the ThingWorx platform. For more information, see Anomaly Detection.
ThingPredictor
ThingPredictor software media is no longer available for download as of 8.3. However, support will continue for 8.x users until the next major release. To replace ThingPredictor capabilities, an improved set of predictive services is being introduced in 8.3. For more information, see How Predictive Scoring Using the Analytics Server Connector Works.
DataConnect / Data Analytics Definition
DataConnect and the Data Analytics Definition are not available as of 8.3. Replacement functionality will be introduced in a future release.
Was this helpful?