|
Enhancement Description
|
Reference #
|
|---|---|
|
ThingWorx Analytics: security improvements
• 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.
• See thistechnical support article for important recommendations regarding the use and update of third-party software for ThingWorx.
|
|
Bug Fix Description
|
Reference #
|
|---|---|
|
Analytics Builder: Storing a large number of datasets can slow performance of certain screens
When Analytics Builder contains more than 500 datasets, the Settings page and the New Predictive Model dialog box might not display properly. To resolve the issue, the code for retrieving dataset information from the server has been refactored. Loading performance of these screens has been improved.
|
TA-6812
|
|
Analytics Server: Categorical data can create problems for clustering and scoring
In some edge cases, when a clustering job is submitted for a dataset with categorical data, the resulting PMML model could be created with too many input fields to allow scoring without errors. This issue has been resolved so that models with categorical data can be clustered and scored successfully.
|
TA-6857
|
|
Analytics Server and Analytics Builder: Storing a large number of models can slow performance of certain screens
When Analytics Server contains more than 500 models, the Models list page might not display properly. To resolve the issue, the code for retrieving the list of models from the server has been refactored. Loading performance of the list page has been improved.
|
TA-6897
|
|
Known Issue Description
|
Reference #
|
|---|---|
|
Analytics Builder: Scoring records from a REST request are not displayed correctly
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
|
|
Analytics Builder: Signal job results not cleared in Chrome browser
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
|