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.

For important recommendations about the use and update of third-party software, see technical support article CS320194.

New validation has been added to Anomaly Alert processing. When creating an anomaly alert, the new validation confirms that the Analytics Gateway is configured properly and connected. Appropriate error messages are displayed so that issues can be resolved in a timely fashion.

TA-7734

In ThingWorx, if the Alert Processing Subsystem is not configured to point to the Analytics Server, anomaly alerts cannot be created. Previously, when an anomaly alert was created on a Thing, this connection was not validated during the alert creation. The anomaly alert still went through the calibration stage and then failed on training with an unclear message.

With this release, validation has been added so that proper configuration of the Alert Processing Subsystem is confirmed. Anomaly alerts will not be created if the configuration is invalid. Clear error messages have been added to the process.

This validation has been added for Anomaly Detection in the standalone mode only. It will be added for ThingWorx cluster mode in the next release.

TA-6973

TA-6976

When running discrete analysis events, where a new job is created for every event trigger, performance issues are occurring. Either the data sent from ThingWorx to the agent is not processed in a timely manner, or the agent appears to stop working. The faster data is scheduled for processing, the faster the agent fails. This issue has been resolved.

TA-7374

TA-7375

When a distribution statistics query or a synchronous scoring job is executed on a Linux server, the system cannot write to /tmp directory that is mounted with noexec permissions. This issue has been resolved.

TA-7709

When creating a model in Analytics Builder, the Filter Detail area remains empty. It does not display the detailed information about row counts and percentage of the dataset. This issue has been resolved so that filter details are displayed as expected.

TA-7930

When a predictive scoring job is submitted via a REST API request, the information displayed on the Model list page in Analytics Builder is incorrect. The Number of Records Scored column should reflect the number of data rows submitted in the REST request. Instead, it displays a value of 0.

This issue will be resolved in a future release.

TA-4715

When a filter is applied to the Signals list page and results in no matching jobs, the list is not cleared properly in a Chrome browser and previous results are displayed. This issue will be resolved in a future release.

TA-4972

When modifying an existing anomaly alert on a Thing in ThingWorx Composer, an inaccurate error message displays saying that the selected Analytics Gateway does not exist. As a work around, change the Alert Type to something other than Anomaly, make the desired modification, and then switch the Alert Type back to Anomaly. This issue will be resolved in a future maintenance release.

TA-8012

In ThingWorx Analytics Server 8.5, confidence models for Boolean and categorical goals could be created during training. When these confidence models are scored, the scoring output includes confidence interval information along with the prediction results. In a future release, the confidence interval information will no longer be returned as part of the scoring results for confidence models created in Analytics Server 8.5 with Boolean or categorical goals. In preparation for future upgrades, you should update any application code that is related to scoring these types of models. Ensure that your application code does not rely on the confidence interval results.