When saving a model, the SaveResult service times out. When saving Signals or Profiles results, the SaveResult service generates an error. This issue has been resolved.

TA-182

When a dataset file with a space in the filename is uploaded to Analytics Builder, the page freezes and the file cannot be uploaded. To resolve this issue, updates have been made so that spaces are now acceptable in dataset filenames.

TA-1504

The error message has been clarified to state that prescriptive scoring is not supported for categorical goals or for goals that do not have a numeric representation.

TA-1513

During real-time predictive scoring, a NullPointerException message is returned when the data shape used to build the datasetRef infotable contains extra fields that are not included in the dataset. A more descriptive message has been added to indicate where in the dataset the mismatch has occurred.

TA-1615

When uploading a PMML file from the root of the AnalyticsUploadStorage repository, an error occurs when the file path is not preceded by a forward slash (/). This issue has been resolved by updating to accept file paths at the root with or without a leading slash.

TA-1630

On the Settings tab in Analytics Builder, the Items Per Page field controls the number of rows that will be displayed on list pages, including Models, Profiles, Signals, Scoring, and Datasets. Previously, this field was configurable only by an Administrator. Now, this field can be configured by each individual user.

TA-1680

When signals is run on a field that has a unique value for every row, the grid display did not refresh completely. This issue has been resolved.

TA-1756

When a training job is launched in new Composer, the job fails with a null error. This issue has been resolved.

TA-1758

During validation on models with a continuous goal field, the goal’s range is divided into 10 equally-sized bins. Within each bin, Pearson correlation and RMSE are calculated and a record count is returned. The record count reflects the number of records where the goal value fell into a specific bin. For time series models, the record count was not being calculated, and was always returned as 0. This issue has been resolved.

TA-1783

When creating a new predictive model via the ThingWorx Analytics Server APIs, there is no upper limit to the upsampling factor. But in Analytics Builder, the upper limit is a 100. The upsampling behavior in Builder has been updated to accept a maximum factor of 1000.

TA-1791

When an Analytics Server Linux installation has been completed successfully on an Ubuntu 16.04 server, the ZooKeeper component will sometimes not start when the other microservices do. Previously, a work around was available to verify whether ZooKeeper was running and to start it if necessary. In this release, the issue has been fully resolved and the work around is no longer necessary.

To verify that ZooKeeper is running, use the twas.sh script to check the status of the installed services. For example: /opt/ThingWorxAnalytics/ThingWorxAnalyticsServer/bin/twas.sh status.

TA-1797

When a predictive scoring job is run with a dataset that contains non-Latin characters, and the results are viewed in a text editor (or any a tool that renders UTF-8), the resulting file is not encoded properly. This issue has been resolved.

TA-1802

When a Signals job is run on a field that is exactly correlated to the goal field, the Pearson Correlation result should equal 1 or -1. However, in some cases, an IllegalArgumentException is produced. This issue has been resolved.

TA-1803

In previous releases, a manual procedure was necessary, post-installation, to run the Configuration service. This configuration is now handled automatically and the service no longer needs to be run manually. For earlier releases, the manual procedure is still required.

TA-1842

Jobs appeared to remain in Queued status, despite being completed, because the status was not properly updated. This issue has been resolved.

TA-1870

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

Analysis agents must be restarted after a ThingWorx server restart. Without restart of the agent, any new simulation jobs will fail to execute.

—

AM-1289

The Version Info service currently returns a version number that indicates both the external version and the internal build version, but not a path release version. Possible changes in version information are under consideration for a future enhancement.

TA-1217

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

The View Datasets and View Models screens do not load properly in the IE 11 browser for the support Windows operating systems. This issue will be resolved in a future release. To avoid the issue, use another browser, such as Chrome, Firefox, or Safari.

TW-31953

When the Analytics Extension is deployed on the 8.3.1 version of ThingWorx platform, the display of some pop-up windows might look compressed in Analytics Builder and Analytics Manager. In some cases, scroll bars will allow you to view truncated fields. However, the best work around for the issue is to maximize your browser view so that the pop-up windows can display fully. This issue will be resolved in a future release.

TW-38342

ThingWatcher has been 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 and the Data Analytics Definition are not available as of 8.3. Replacement functionality will be introduced in a future release.