Release Notes > Version 8.4 Release Notes > ThingWorx Analytics 8.4.4 Release Notes
ThingWorx Analytics 8.4.4 Release Notes
The following sections describe the enhancements, bug fixes, and known issues in ThingWorx Analytics 8.4.4.
Enhancement Description
Reference #
Provide a script to handle updates of encrypted keys and passwords
This release provides a new script that automates much of the update procedure for encrypted ThingWorx AppKeys, ThingWorx Analytics API Keys, and RabbitMQ passwords. The new script eliminates the manual work of copying randomly generated Key Store directory and file names and plugging them into a complex Java encryption command. The new encryption script is stored in the install bin directory and is launched with a simple command that requires two parameters.
For more information, see Updating Encrypted Keys and Passwords in the Analytics Help Center.
Optional persistence for Property Transforms
Persistence for transformed properties in ThingWorx is now optional. Previously, when defining a transformed property, the persistence aspect was required. In this release, that option can now be turned off so that non-persistent property transforms can be created.
Property Transform calculation service to compute range
A new Range service has been added to Property Transform functionality. Essentially, the Range calculation returns the difference between the maximum and the minimum values for a specific set of streaming data. Range is available for use as a new Calculation Type when defining a transformed property. Adding a Range property transform to a Thing is a simple way to automate range calculations which can then be used in support of other process control monitoring.
Descriptive Analytics calculation service to compute range
A new Range service has been added to Descriptive Analytics functionality. Essentially, the Range calculation returns the difference between the maximum and the minimum values for a specific set of batch data. For Descriptive Analytics, Range is available as a new batch service in the library of statistical calculation services. In ThingWorx, Range is available for use as part of the StatisticalCalculation Thing Template. When the Range calculation service is called, the automatically calculated range values can be used in support of other process control monitoring.
Bug Fixes
Bug Fix Description
Reference #
Platform Analytics Installer: Error occurs during upgrade
Typically, when upgrading to a new version of Platform Analytics, all of the services are stopped and then restarted when the upgrade is complete. Periodically, when upgrading from 8.4 0 or 8.4.1 to a newer version, the RabbitMQ service does not stop. In both Linux and Windows environments, the running service can cause an error that prevents the upgrade from completing. This issue cannot be completely resolved. When it occurs, an error message is displayed with instructions for a work around – the RabbitMQ service must be stopped manually and the upgrade process relaunched.
For specific instructions on stopping the RabbitMQ service manually, see one of the following troubleshooting procedures:
Linux – See the procedure called Work Around to Stop RabbitMQ for a Platform Analytics Upgrade. It’s the final section of Troubleshooting.
Windows – See the procedure called Work Around to Stop RabbitMQ for a Platform Analytics Upgrade. It’s the final section of Troubleshooting.
Platform Analytics Installer: Incorrect value used in the thingworx.isSecure property
When Platform Analytics is installed with SSL enabled, the Platform Analytics Things are not created successfully in ThingWorx. The cause of the issue has been identified as incorrect values (1/0) being written to the thingworx.isSecure property. The issue has been resolved so that the correct values (true/false) are written to the property.
Analytics Builder and Analytics Manager: Sizing of pop-up windows is distorted
When the Analytics Extension is deployed on ThingWorx platform, the display of some pop-up windows might appear compressed in Analytics Builder and Analytics Manager.
This issue has been resolved.
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.
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.
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.
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.
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.
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.
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.
End of Life Information
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 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?