Predix Essentials Release Notes for the Second Quarter of 2019

Activate Licenses

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

Release Date: June 7, 2019

Table 1. Resolved Issues

The following issues that existed in one or more previous versions have been resolved.

DescriptionTracking ID
Previously, when you activated a license, you had to manually switch the data source to which you applied the license to offline, and then to online. Now, you do not have to perform this action. After activating the license, you must log off from Predix Essentials and log in again.DE109678

Alerts

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

Release Date: June 28, 2019

Table 2. Enhancements and New Features

The following enhancements and new features have been added.

DescriptionTracking ID
To optimize the analysis of an issue with an asset, in the alerts grid and alerts inbox, you can now select the asset and thereby, only the alerts associated with the asset appear.F44283
Table 3. Resolved Issues

The following issues that existed in one or more previous versions have been resolved.

DescriptionTracking ID
Previously, a few of the alerts were missing from the alerts grid. However, you could access the details of the alerts using the URL of the alert. This issue has been resolved.DE109706
Previously, even though no filter was applied, only consumable alerts appeared in the alerts grid. This issue has been resolved. Now, if no filter is applied, all the alerts appear in the alerts grid.DE109443
Previously, two users could claim the same alert. If one of the users updates the alert, it overwrites the data of the alert that was updated by the other user. This issue has been resolved.DE101223

Release Date: April 22, 2019

Table 4. Enhancements and New Features

The following enhancements and new features have been added.

DescriptionTracking ID
The Asset Customer Name column is now available for grouping in an alerts grid. DE105263
Table 5. Resolved Issues

The following issues that existed in one or more previous versions have been resolved.

DescriptionTracking ID
Previously, for SmartSignal and latched alerts, when you attempted to sort or filter the First Occurrence and Last Occurrence columns in an alerts grid, the columns were not sorted or filtered based on the criteria specified. This issue has been resolved. DE79592

Analysis

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

Release Date: June 28, 2019

Table 6. Enhancements and New Features

The following enhancements and new features have been added.

DescriptionTracking ID
You can now plot up to 60 tags on a single SmartSignal card in the analysis view.F45091
You can now view the diagnostics markers on the residual charts if only the residual chart is plotted for a tag, and the actual and estimates charts are not plotted for the tag.F43839
In the Analysis view, in addition to the name, alias, and description of the contributing or noncontributing tag, you can now view the name of the asset and the name of the alert associated with the tag.F43838
For SmartSignal charts, you can now configure your preferred mode of visualization of data plotting as either date and time mode or points mode. To facilitate this enhancement, in the SmartSignal Chart and Marker Settings section of the My Preferences page, the Plotting Preferences section has been added.F43836
You can now plot a Time-Series (Scatter) chart in Analysis templates. This new chart type has the same functionality as that of the Time-Series (Line) chart.F43750
You can now view the name of the parent asset in addition to the name of the asset in context when you access the analysis information related to an Alert. If the asset belongs to a complex hierarchy, you can also open the Context Browser in the view mode.F43740
You can now define the diagnostics markers in your SmartSignal Analytics and show them on the Analysis charts when you view the data associated with the analytics tags. You can also point to the diagnostics markers in the charts to view the details of the diagnostics events. F43723
The performance in loading Analysis templates from Alerts and Cases has now been improved.F43722
You can now use infinite scrolling instead of pagination in the data table view in an Analysis template.F42051
You can now zoom in on the bar charts in an EBQ Analysis template.F42051
You can now set the y-axis limits on Parallel Axis and Spider charts.F42051
You can now search for an element in any drop-down list box of an Analysis that has more than 10 elements.F42051
You can now add an asset to the analysis view from an Alert to allow you to use the data from additional assets in your analysis of the Alert.F42051
You can now view SmartSignal Cycle Watch Events in an Analysis and plot analytics tags based on Event Frames.F41913
Table 7. Resolved Issues

The following issues, which existed in one or more previous versions, have been resolved.

DescriptionTracking ID
Previously, with the cross-hair mode enabled on an Analysis template, if you added a new chart to the Analysis template, the cross-hair information did not appear on the new chart, and the cross-hair markers did not appear on the existing charts. This issue has been resolved.DE99126
Table 8. Known Issues and Limitations

The following issues have not been resolved in this release.

DescriptionTracking ID
If you point to a diagnostic marker on a SmartSignal chart, no information appears. To exit the mode and view the information about the marker, refresh the charts.DE101633
When you have multiple y-axes enabled on a Time-Series chart, Y zoom and XY zoom provide an inconsistent user experience because all the axes do not scale correctly to reflect the zoomed-in state.DE104375
When you delete tags on a Time-Series chart after you have plotted pin markers, the deleted tags appear in the marker data table. To prevent this issue, delete the tags, and then set the pins on the charts. DE95436
While modifying the Time-Series chart in multiple y-axes mode, if you select Apply, your changes are neither applied nor visible in the chart settings. To prevent this issue, select Cancel, and then create the template for an ad hoc view. Alternatively, you can save the template, and then modify the existing template as needed. DE93811
You must now use Google Chrome to add multiple charts to a SmartSignal card.
Note: Other browsers, including Internet Explorer, do not support adding multiple charts to a single SmartSignal card.
None

Analytics

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

Release Date: June 28, 2019

Table 9. Enhancements and New Features

The following enhancements and new features have been added.

DescriptionTracking ID
Using the common analytics framework, you can now generate multiple alerts at the same time to analytics that are deployed on the Predix Insights and Predix Framework runtime environments. You can also associate one or more alert templates with an analytic using the Output Events section.
Note: To associate an alert template with an analytic and to generate multiple alerts, you must enable the template in the I/O Mapping page.
US355437

Release Date: June 7, 2019

Table 10. Resolved Issues

The following issues that existed in one or more previous versions have been resolved.

DescriptionTracking ID
Previously, you could not access Asset Filters through the module navigation menu if you selected a navigation profile from the Module Navigation section under Tenant Preferences. This issue has been resolved.DE109144

APM Connect

This topic provides a list of product changes included in this patch.

Release Date: June 28, 2019

Table 11. Enhancements and New Features

The following enhancements and new features have been added.

DescriptionTracking ID
APM Connect now supports UDLP V2.6.1. The data loader framework in UDLP V2.6.1 is compatible with GE Digital APM V4.3.0.7.5.US354669
The automatic data loaders are now supported in APM Now. Using these data loaders, you can automatically import data into Predix Essentials.US354406
The SAP Equipment and Functional Location technical characteristics are now supported for multiple language data extraction. US351143
Table 12. Resolved Issues

The following issues that existed in one or more previous versions have been resolved.

DescriptionTracking ID
Previously, when using automatic data loaders, if multiple records were imported at the same time, sometimes, a few records were skipped. This issue has been resolved.DE111514
Previously, Apache Karaf crashed in the cloud environment because of the way the APM Connect data loader job handled the conversion of the .xlsx file to a .csv file. This issue has been resolved. Now, the .xlsx file is converted to a .csv file before it is sent to Apache Karaf. DE111512
Previously, when using automatic data loaders, an error message appeared although the records were imported successfully. This issue has been resolved. DE111339
Previously, the Planned Work and Work Management Interface integration did not allow filtering by Maintenance Plant. This has been resolved. You can now use Maintenance Plant as a filter for Planned Work and Work Management Interface.DE110851

Release Date: June 7, 2019

Table 13. Resolved Issues

The following issues that existed in one or more previous versions have been resolved.

DescriptionTracking ID
Previously, Site records created using the Unified Asset Ingestion Data Loader did not synchronize with the Meridium database for the entire system if you did not refresh the Intermediate Repository database. Now, the Unified Asset Ingestion Data Loader synchronizes with the Meridium database correctly even if you do not refresh the Intermediate Repository database.DE109166

Asset Hierarchy

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

Release Date: April 18, 2019

Table 14. Resolved Issues

The following issues that existed in one or more previous versions have been resolved.

DescriptionTracking ID
Previously, in the Group section of the Asset Finder window, when you attempted to add a group of assets, an error occurred. This issue has been resolved.DE107347

Cases

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

Release Date: June 28, 2019

Table 15. Enhancements and New Features

The following enhancements and new features have been added.

DescriptionTracking ID
For collaborative analysis of a case, you can now easily share the case with other users or user groups by sending an email notification with the link to the case. To facilitate this enhancement, the Notify User button () has been added to the details section of a case.F44281
For a better analysis of a case, you can now add an analysis template to the case so that you can save it as one of the data points.F44077
Table 16. Resolved Issues

The following issues that existed in one or more previous versions have been resolved.

DescriptionTracking ID
Previously, in a cases grid, when you attempted to change the cases filter set, the loading symbol appeared, however, the list of cases for the selected filter set did not appear in the grid. This issue has been resolved.DE109676
Previously, when you filtered the cases grid by a case, the filtered list contained duplicate records. This issue has been resolved.DE108723
Previously, in a cases grid, the grouped column selection persisted until a first-time user grouped the columns in a cases grid for one of the cases filters set. This issue has been resolved.DE107402
Previously, for a first-time user, the cases did not appear in the cases grid even though the Predix Essentials application indicated that the cases were being loaded. This issue has been resolved.DE107396
Previously, if a note was added to a case, the Timeline view of the case did not contain any information about the note being added to the case. This issue has been resolved.DE103410
Previously, in a cases grid, the Asset Alias column appeared blank. This issue has been resolved.DE100785

Release Date: April 22, 2019

Table 17. Enhancements and New Features

The following enhancements and new features have been added.

DescriptionTracking ID
You can now group columns in a cases grid to organize data for easy access.F34245
Table 18. Limitations

The following limitations exist in this release.

DescriptionTracking ID
For security reasons, you cannot share a case report from the GovCloud environment. US337829
You cannot sort grouped columns in a cases grid.NA

Catalog

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

Release Date: April 18, 2019

Table 19. Resolved Issues

The following issues that existed in one or more previous versions have been resolved.

DescriptionTracking ID
Previously, after you upgraded an Oracle data source, certain custom folders did not appear in the catalog under Public > Meridium. This issue has been resolved.DE106796

Data Loaders UDLP V2.7.0

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

Release Date: June 7, 2019

Table 20. Resolved Issues

The following issues that existed in one or more previous versions have been resolved.

DescriptionTracking ID
Previously, in a cloud environment, when you tried to load a .zip file containing .csv files using the Data Loader interface, the load intermittently failed with the message access denied. Now, the files load without errors.DE109151

Family Policies

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

Release Date: June 28, 2019

Table 21. Resolved Issues

The following issues that existed in one or more previous versions have been resolved.

DescriptionTracking ID
Previously, in the Properties window for a Create Entity node, if you specified values for more than two fields of the new entity, and then saved the policy, when you reloaded the policy, sometimes the values of only the first two fields were retained. This issue has been resolved.DE111238
Previously, when you attempted to modify a record that triggered an After Update family policy containing a Baseline Rule node, and if the baseline rule configured for the Baseline Rule node updated the same record that triggered the policy, a time-out error occurred and the record was not modified. This issue has been resolved.DE110458
Previously, when a vector output of an R Script returned only one value during the execution or validation of a policy, an error occurred. This issue has been resolved.DE110279

Release Date: June 7, 2019

Table 22. Enhancements and New Features

The following enhancements and new features have been added.

DescriptionTracking ID
The messages written in the server logs by the Policy Execution Service and Policy Trigger Service are now more specific to the logging levels.US347947
Table 23. Resolved Issues

The following issues that existed in one or more previous versions have been resolved.

DescriptionTracking ID
Previously, when the job configured to delete the execution history logs ran, the following issues intermittently occurred:
  • The old Execution History records were not deleted.
  • The policy execution transactions were reverted because the Execution History table of the database was locked by the job. This resulted in the execution failure of policies while the job was in progress.
These issues have been resolved.
  • DE106869
  • DE101822

Release Date: April 18, 2019

Table 24. Resolved Issues

The following issues that existed in one or more previous versions have been resolved.

DescriptionTracking ID
Previously, when you started the Policy Execution Service or Policy Trigger Service, if the Microsoft Message Queuing (MSMQ) stopped responding or could not be accessed, the service failed to start. This issue has been resolved.US341549
Previously, in the Properties window for a Math node, when you specified the names of some variables, an error message appeared in the notification bar, indicating a conflict between variable names, even when there was no apparent conflict in the specified names. This issue occurred when two variable names contained the same string and one of them contained an underscore or numeric value after the string. This issue has been resolved. Now, in these scenarios, the following events occur:
  • If one of the variable names contains an underscore after the string, no notification appears in the notification bar.
  • If one of the variable names contains a numeric value after the string and if there is a possibility of conflict between the variable names during the execution of the policy, a warning appears in the notification bar.
DE107317
Previously, in the Properties window for a Create Recommendation node, in the Create Work Request section, if you selected Yes, the execution of the policy failed, and no work request was created in the configured Enterprise Asset Management (EAM) system for the new Policy Recommendation record. This issue has been resolved.DE99104

Foundation

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

Release Date: May 10, 2019

Table 25. Enhancements and New Features

The following enhancements and new features have been added.

DescriptionTracking ID
You can now continue to work on a module even if a message stating that your session has expired appears erroneously. To facilitate this enhancement, the Cancel button has been added to the window that contains the message so that you can close the window.US346689

GE Dashboards

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

Release Date: June 28, 2019

Table 26. Enhancements and New Features

The following enhancements and new features have been added.

DescriptionTracking ID
The following enhancements have been made to the Generic Graph Widget:
  • You can now navigate from the source dashboard to the destination dashboard within the same section. To facilitate this enhancement, a new destination, Dashboard Internal, has been added to the Navigation section.
  • You can now navigate from a widget to a dashboard that does not have any asset context. This enhancement facilitates passing the name of the source dashboard and the asset context to the destination dashboard.
F45365

Release Date: May 23, 2019

Table 27. Enhancements and New Features

The following enhancements and new features have been added.

DescriptionTracking ID
The Save As New Dashboard feature enables you to make a complete copy of a dashboard, including the cards, widgets, tags, tag expressions, availability, and metadata of the original dashboard. Only the permissions are not copied; the copy is created with default permissions. Use the copy as the basis for modifications that provide new dashboard capabilities. You can create a copy of any dashboard (with the exception of General Dashboards), even those you do not have permission to modify.US321194

Graphs

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

Release Date: April 18, 2019

Table 28. Resolved Issues

The following issues that existed in one or more previous versions have been resolved.

DescriptionTracking ID
Previously, hyperlinks in a heat map did not work as expected. This issue has been resolved.DE106778

Policy Designer

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

Release Date: June 28, 2019

Table 29. Resolved Issues

The following issues that existed in one or more previous versions have been resolved.

DescriptionTracking ID
Previously, in the Properties window for a Create Entity node, if you specified values for more than two fields of the new entity, and then saved the policy, when you reloaded the policy, sometimes the values of only the first two fields were retained. This issue has been resolved.DE111238
Previously, when a vector output of an R Script returned only one value during the execution or validation of a policy, an error occurred. This issue has been resolved.DE110279

Release Date: June 28, 2019

Table 30. Enhancements and New Features

The following enhancements and new features have been added.

DescriptionTracking ID
The messages written in the server logs by the Policy Execution Service and Policy Trigger Service are now more specific to the logging levels.US347947
Table 31. Resolved Issues

The following issues that existed in one or more previous versions have been resolved.

DescriptionTracking ID
Previously, if you copied and renamed an Input node of the policy model, and then saved the policy, the following issues occurred until you reloaded the policy:
  • The renamed node did not appear in the instances associated with the policy.
  • All instances associated with the policy were deactivated due to which the policy was not executed.
  • The validation of the policy failed with an error message, indicating that you had not specified any record for the new Input node.
These issues have been resolved.
DE109329
Previously, when the job configured to delete the execution history logs ran, the following issues intermittently occurred:
  • The old Execution History records were not deleted.
  • The policy execution transactions were reverted because the Execution History table of the database was locked by the job. This resulted in the execution failure of policies while the job was in progress.
These issues have been resolved.
  • DE106869
  • DE101822

Release Date: April 18, 2019

Table 32. Resolved Issues

The following issues that existed in one or more previous versions have been resolved.

DescriptionTracking ID
Previously, when you started the Policy Execution Service or Policy Trigger Service, if the Microsoft Message Queuing (MSMQ) stopped responding or could not be accessed, the service failed to start. This issue has been resolved.US341549
Previously, in the Properties window for a Math node, when you specified the names of some variables, an error message appeared in the notification bar, indicating a conflict between variable names, even when there was no apparent conflict in the specified names. This issue occurred when two variable names contained the same string and one of them contained an underscore or numeric value after the string. This issue has been resolved. Now, in these scenarios, the following events occur:
  • If one of the variable names contains an underscore after the string, no notification appears in the notification bar.
  • If one of the variable names contains a numeric value after the string and if there is a possibility of conflict between the variable names during the execution of the policy, a warning appears in the notification bar.
DE107317
Previously, in the Properties window for a Create Recommendation node, in the Create Work Request section, if you selected Yes, the execution of the policy failed, and no work request was created in the configured Enterprise Asset Management (EAM) system for the new Policy Recommendation record. This issue has been resolved.DE99104

SAP and SAP PI UDLP V2.7.0

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

Release Date: June 28, 2019

Table 33. Resolved Issues
DescriptionTracking ID
Previously, Predix Essentials created placeholder records for assets that did not exist when a Work History record was loaded. Now, the system does not create the placeholder records, but logs such records as 'Work History records need to be reprocessed'.US347758
Previously, Maintenance Plan records without Task Lists or Operation Objects were not discontinued by the Work Management Adapter. Now, the adapter correctly discontinues the Maintenance Plan records.DE105578
Previously, Inspection Task records with long text that exceeded 1,000 characters created long text in SAP with invalid characters in the format field. Now, the format field contains valid characters.DE105547
Previously, the system incorrectly mapped MI_REC_TARGE_COMPL_DATE_DT entity to Target Completion Date in SAP. This resulted in failed creation of Notification records. Now, the system maps the MI_REC_TARGE_COMPL_DATE_DT entity to the correct date, resulting in the successful creation of a Notification record.DE105459
Previously, SAP PI source files were not deleted from the shared folder. Now, the system deletes these files.DE79645

Schedule Logs

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

Release Date: April 18, 2019

Table 34. Resolved Issues

The following issues that existed in one or more previous versions have been resolved.

DescriptionTracking ID
Previously, a policy was not executed as per schedule until you updated the policy, if the following changes had been made to the Predix Essentials database that contained the policy:
  • The Predix Essentials database had been restored and connected to another data source.
  • The Predix Essentials server associated with the Predix Essentials database had been restarted.
This issue has been resolved.
DE102150

Time Series Data

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

Release Date: June 28, 2019

Table 35. Enhancements and New Features

The following enhancements and new features have been added.

DescriptionTracking ID
Queries now support up to 100 tags in the Time Series Data Retrieval Service v4 and v5 APIs and the v2/time_series/delete endpoint. Previously, the maximum number of tags in a single query was 40.
Note: The Time Series Data Retrieval Service v2 and v3 APIs still support a maximum of only 40 tags.
US341163