Fourth Quarter of 2018

Analytics

This topic provides a list of product changes released for this module on the dates listed below.

Release Date: December 14, 2018

Table 1. Enhancements and New Features
Description	Tracking ID
To enhance the performance during orchestration deployment, Application Analytics now caches data between orchestration steps.	F37992
To enhance the usability in accessing relevant deployments, you can now: Filter the deployment results using the deployment name or Analytic Template name in the keyword search. Search and retrieve related deployments by assets or entity ID. If the asset ID matches one or more of the filter criteria defined in an asset filter that was used in deployments, then all related deployments are listed for that asset ID.	F36287
To enhance the modifications to orchestration deployments, you can now define overrides for asset applicability at the input level during deployment. Note: This is not available for all runtimes.	F36279
To enhance the usability in the deployment creation and modification process, in the I/O Mapping step during deployment, you can now expand and collapse the ASSET(S) and Data Flow panes. Additionally, you can now: Access tags and attributes at the asset level. Map tags and attributes that are not common to all assets. Access the list of steps and iterations as a tree view in the Data Flow pane.	F36275 F36274
To enhance the I/O Mapping step during deployment, you can now configure an Analytic Template to allow mapping inputs to aggregate tags or multiple assets. This also provides the ability to write back to tags defined at any asset hierarchy level. Note: This feature is limited to the Spark runtime.	F36259 F18099
To enhance the asset applicability during deployment, you can now configure asset filters with Custom Attributes from non-asset entities. Note: This enhancement is limited to AIR and SOAR runtimes only.	F33365
To enhance the retrieval of inputs and storage of outputs during deployments, you can now connect to the following data stores: APM Time Series APM Asset Attributes Blob Store	F26075
To enhance the usability, you can now define data points for analytic inputs during analytic or orchestration deployment.	F26069
To enhance the ability to configure the Analytic Template, you can now make constants optional in the Analytic Template definition.	F17879
To enhance configuration in the Analytic Template, you can now define the unit of measure conversion for an analytic input or output. You can then pass that conversion formula to the respective runtime during deployment.	F10674
To enhance the ability to assign and control Analytics access permissions, you can now define permission sets using multiple features and permissions instead of one large permission set.	F2568
To enhance deployment modifications, you can now modify the version of the Analytic Template in deployment. If the Analytic Template has multiple versions of the analytic artifact uploaded to the catalog, the user can select which version to apply during deployment.	US231988
To enhance usability in the Analytic Template creation process, you can now see a customized form with only relevant fields and boxes specific to the selected runtime. Other options not relevant to the runtime are hidden.	US112770

Table 2. Resolved Issues
Description	Tracking ID
Previously, when using the .csv file, the Format Value column did not appear and you could only define values for the Mapping Value Type field in the Analytics Templates page. This issue has been resolved. Now, you can use the .csv upload template to define values for the Data Format field as expected.	DE78361
Previously, after tenant creation, the default asset filters and filter field data were unavailable for the new tenant that was set up in QA2 environment. This issue has been resolved.	DE63501
Previously, an Analytic Template failed to deploy or run if the Sampling Interval for interpolated data was set to `0 minutes` or `0 seconds` even though the deployment was saved. This issue has been resolved.	DE62748
Previously, for analytics that were deployed and executed in the Predix Analytic runtime, if you redeployed the analytics with a newer version of that Analytic Template that had been uploaded to the catalog, the deployment failed, the deployment status was set to `Not Deployed`, and the following error occurred: `invalid service task name <task id>`. This issue has been resolved. Now, if you redeploy a previously executed analytic with a newer version of the Analytic Template that had been uploaded to the catalog, the Deployment completes as expected.	DE62740

Table 3. Known Issues
Description	Tracking ID
If a deployment uses more than 1000 assets but does not have all outputs explicitly mapped, then the error `ConcurrentModificationException` occurs and the deployment fails. If you notice this error, make sure to map all outputs before scheduling the deployment.	DE97332
If you make modifications to an Analytic Template configuration after it has already been used in a deployment, the deployment status in the Deployments page is expected to display `Updates Not Deployed`. Sometimes, the status does not automatically refresh. If you notice this behavior, simply refresh the page for the status to display correctly.	DE95790
Only on dedicated tenants, administrators cannot access the audit logs for Analytics using the Audit Log Management page. Administrators should contact support to access these logs via the backend. This is not an issue on shared tenants.	DE94501
Sometimes, even though there are no current deployments associated with the version of the analytic templates that you want to delete, an error occurs indicating that you must first delete any associated deployments before you can delete the version of the analytic artifact in the template.	DE77551

Limitations

Application Analytics does not support cross-tenancy; therefore, you will not be able to access assets from a different tenant.