|
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.
For important recommendations about the use and update of third-party software, see technical support article CS320194.
|
|
Bug Fix Description
|
Reference #
|
|---|---|
|
Analytics Server and Analytics Builder: Model building fails with Confidence Model enabled
Resolved an issue that was causing the model building to fail with the Confidence Model enabled. The issue had appeared when you applied a filter flag=training on your data, enabled the Confidence Model with level = 80%, and tried to build the model.
|
TA-8231
|
|
Analytics Builder: Max Field limits are ignored during predictive model creation
If the Redundancy Filter is enabled during predictive model creation, features are ranked according to the information gain they provide. The value in Max Fields limits the model to a specific number of fields during training. This Max Fields value is being ignored. This issue has been resolved so that the limits on the number of features included during training are observed.
|
TA-7788
|
|
Anomaly Alert: Returns an inaccurate error message during modification
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. A work around was provided earlier to the users as follows: change the Alert Type to something other than Anomaly, make the desired modification, and then switch the Alert Type back to Anomaly.
This issue has been resolved now.
|
TA-8292
|
|
Analytics Manager: Issue with the event processing
Resolved an issue with the incorrect events processing in the Analytics Manager.
|
TA-7758
|
|
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
|
|
Analytics Server: A large dataset can slow the display performance of model results
When a model is created using a large dataset (1 GB or more), the display of the model results can be slow. To avoid a timeout failure, change the timeout settings as follows:
1. In your ThingWorx installation directory, navigate to the ThingworxPlatform/platform-settings.json file and open it. In the BasicSettings section, add a new ScriptTimeout parameter as follows:
"PlatformSettingsConfig": {
"BasicSettings": { "ScriptTimeout": "3000" }, 2. Restart your ThingWorx server.
3. Log into ThingWorx Composer and navigate to > > > > . Change the value to 3000.
Changing the timeout settings will not resolve the slow performance but it will prevent a timeout failure. This issue will be resolved in a future release.
|
TA-6766
|
|
Analytics Manager: Empty analysis replay instance created
When an analysis replay is created and it does not include data for the specified time frame, an error is generated. However, an empty analysis replay instance is still created containing no records. The empty instance must be deleted before another replay can be created for the same time frame. This issue will be resolved in a future release.
|
TA-7619
|
|
Confidence Model Scoring for Boolean and Categorical Goals
|
|---|
|
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.
|