Predix Essentials Release Notes for the Third Quarter of 2019

Action Management

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

Release Date: September 27, 2019

Table 1. Enhancements and New Features

The following enhancements and new features have been added.

DescriptionTracking ID
You can now implement one or more strategy actions by creating a Proof Test Task or linking the actions to existing Proof Test Tasks.US352739
In the RBI Admin Preferences page, if the Implement Recommended Actions to Tasks in ASM check box is cleared, the Apply Updates (), Unlink Implementation (), Send to ASI Package (), and Implement buttons are now disabled in the Strategy Actions section of the Action Management page. This is applicable for actions sourced from the Risk Based Inspection or Compliance Management modules.US352738
The performance of the Strategy Actions query has been improved.US338510
Table 2. Resolved Issues

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

DescriptionTracking ID
Previously, in the Recommended Actions section, when you entered the search criteria in a filter box, the row containing the filter boxes disappeared from the grid. This issue has been resolved.DE115075
Previously, in the Recommended Actions pane, if you selected a Recommended Action and attempted to create an EAM Notification from a General Recommendation and it failed, an incorrect message appeared.DE105557
Previously, in the Strategy Actions section of the Action Management page, an irrelevant button, Send to ASI Package () was available. This issue has been resolved.DE105294
Previously, even though the Meridium Core license was activated, the following options appeared in the Implement drop-down list box of the Strategy Actions section:
  • EAM Work Request
  • EAM Maintenance Plan
This issue has been resolved. Now, in this scenario, the options do not appear in the Implement drop-down list box.
DE102170
Previously, in the expanded view of the Recommended Actions pane, the search function worked only on the RECOMMENDATION HEADLINE column. This issue has been resolved. Now, the search function works on all the columns in the Recommended Actions section.DE79684

Release Date: September 6, 2019

Table 3. Resolved Issues

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

DescriptionTracking ID
Previously, in the General Recommendation datasheet, when the Alert Assignee When Due check box was selected for a record, alert email messages were not sent. This issue has been resolved. DE116027

Alerts

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

Release Date: September 27, 2019

Table 4. Enhancements and New Features

The following enhancements and new features have been added.

DescriptionTracking ID
The following enhancements have been made to the Alerts OData service:
  • Filter Alerts based on the Asset permissions.
  • Filter Alerts based on limited visibility filtering permissions.
  • FieldValue and AuditLog for ALERTS_ODATA entities added.
F47045
Cross-tenant support for queries has been added to the Alerts OData service.F47044
You can now view the Event Time and the Received Time of an alert in the alert email message.F46532
The email message on Alerts now includes a list of all the scan group data associated with an alert.
Note: If the scan group data is not available, the email message contains the message None.
F46530
The following enhancements have been made to the Alerts page:
  • When you expand or collapse the Asset Context Browser, the Alerts grid view now adjusts itself to fit into the Alerts page.
  • The Asset Context Browser now appears by default.
F46329
You can now view the custom attributes of the asset in the details page of the associated alert. To facilitate this enhancement, the ASSET INFORMATION section has been added to the page. In addition, you can export the attributes to a PDF file.F44710
An email notification that you receive for an alert now contains the severity of the alert. This helps you prioritize and act on the alert based on the severity.F44707

Release Date: August 13, 2019

Table 5. Resolved Issues

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

DescriptionTracking ID
Previously, you could not assign the Alert that was owned by a different user to yourself. This issue has been resolved.DE116111

Release Date: July 12, 2019

Table 6. Enhancements and New Features

The following enhancements and new features have been added.

DescriptionTracking ID
Previously, you received an email message each time the severity of the alert that you had claimed changed, thereby increasing the number of emails for the same alert. To avoid this issue, the feature is now disabled.DE114663

Analysis

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

Release Date: September 27, 2019

Table 7. Enhancements and New Features

The following enhancements and new features have been added.

DescriptionTracking ID
You can now set the permissions on Analysis templates to share the template across all the enterprises.
Note: To enable this functionality, you must have the Create Tenant Level Template permission. This permission, when enabled, allows the user to set the visibility of any analysis class template to be accessible for any newly added enterprises after the template creation.
US360472
You can now create public analysis templates that are available to all the users in a tenant. To enable this functionality, you must have the required permissions. F46552
You can now configure all the parameters in an Analysis template before you load a saved template. This allows you to load the data in the format that you want. F46551
You can now configure the SmartSignal chart series settings and other settings at a card level. This allows you to configure the series that you want to enable for the tags in each of the charts in the card. You can also set other settings for the cards such as enabling automatic thresholds on the charts and filtering the data on the charts by using mode thresholds. F46364
  • You can now view the asset name along with the tag name in the tag register for normal charts.
  • You can now add a loading indicator to all the charts when the charts are waiting for data.
  • You can now scale the actual or estimate charts based on the data instead of the thresholds on the charts.
F44252
You can now add a SmartSignal tag or a group of tags anywhere in the SmartSignal Card. F43749
You can now view an evidence that is attached to a case up to the current time. This allows you to see the change that has occurred since the time the evidence was saved to the case. F41107
Table 8. Known Issues

The following issues are unresolved in this release.

DescriptionTracking ID
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
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
If you enable the cross-hair mode in an analysis and then add new charts to the template, the cross-hair information is not reflected on the new charts, and the cross-hair markers are no longer visible on the existing charts. To prevent this, disable cross-hair mode, add the charts, and then enable the cross-hair mode again.DE99126
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 use Google Chrome to add multiple charts to a SmartSignal card.
Note: Other browsers, including Internet Explorer, are not supported when adding multiple charts to a single SmartSignal card.
None

APM Connect

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

Release Date: September 27, 2019

Table 9. Enhancements and New Features

The following enhancements and new features have been added.

DescriptionTracking ID
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
To enhance the performance of data loading processes, the default severity level for logging events has been changed from DEBUG to ERROR.F42056

APM Mobile Application

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

Release Date: September 27, 2019

Table 11. Resolved Issues

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

DescriptionTracking ID
Previously, when you attempted to sync a route, the readings were not loaded. In addition, the route was marked done, thus preventing you to unlock the route and load the readings again. This issue has been resolved.US363216

Asset Criticality Analysis

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

Release Date: September 27, 2019

Table 12. Enhancements and New Features

The following enhancements and new features have been added.

DescriptionTracking ID
If the SAP Criticality Assessment license is active, criticality values from an assessment are automatically updated in SAP after you move the associated analysis to the Approved state. US364277
To improve performance, the SQL join clauses corresponding to the Asset Group families have been removed from the following catalog queries:
  • Public\Meridium\Modules\Asset Criticality Analysis\Queries\ACA Analysis Assets
  • Public\Meridium\Modules\Asset Criticality Analysis\Queries\ACA Analysis Criticality
US354330
To improve usability, the risk assessment window has been modified as follows:
  • The size and positioning of the Basis of Assessment box have been adjusted.
  • The expand feature has been added to the Basis of Assessment box.
US345815
In the ACA Overview page, the performance when loading the tile counts has been improved.US342276
To improve usability, the Description column has been removed from the ACA Analyses query.US322347
You can now access the reference documents for an ACA Analysis by selecting the Reference Documents tab from the Asset Criticality Analysis page.US318203
To enhance usability in the Assessment workspace, functionality to export an analysis assessed using a Criticality Checklist has been added.US316934
To enhance usability in the Asset Criticality Overview page, functionality to export analyses assessed using a Criticality Checklist has been added.US316933
Table 13. Resolved Issues

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

DescriptionTracking ID
Previously, when you attempted to update SAP from the Analysis View, incorrect error logs were created. This issue has been resolved. Now, in this scenario, the correct error logs are created.DE115040
Previously, when you attempted to access an assessment that contained double quotes in the Basis for Assessment field, an error occurred, and the assessment did not load. This issue has been resolved.DE108039
Previously, in the Risk section of the Analysis Summary page, if you accessed an analysis whose associated Risk Matrix record had the Use Aliases? check box selected, the Total Risk value on the risk assessment appeared as a numeric value instead of an alias value.DE105758
Previously, while using the ACA data loaders, the logs sometimes did not capture the data that was successfully loaded. This issue has been resolved.DE104003
Previously, column headings and fields were not properly localized in the following locations:
  • The ACA Overview page
  • The Analyses workspace
  • The Assets workspace
  • The Assessment workspace
DE101533
Previously, regardless of your culture settings, the values in the State column were displayed in English. This issue has been resolved. Now, the values in the State column are displayed in the language that is based on your culture settings.DE99458
Previously, if a field in a checklist was updated by a policy, the corresponding entity was not updated with the latest field value. This issue has been resolved. US358409
Previously, in the ACA Admin page, if you locked the Probability, Consequence, or Protection Level fields for an ACA System Criticality Analysis, and then accessed the Risk Matrix for that analysis, the fields were not locked. This issue has been resolved.US334389
Table 14. Obsolete Features

As of this release, the following items are no longer available.

DescriptionTracking ID
For the Asset Criticality Analysis and Asset Criticality Analysis System families, the following fields are no longer available:
  • Import Date
  • Import Status
  • Imported By
US274720

Asset Hierarchy

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

Release Date: September 27, 2019

Table 15. Enhancements and New Features

The following enhancements and new features have been added.

DescriptionTracking ID
You can now view the number of alerts created for an asset when you access the module-specific data for the asset. To facilitate this enhancement, a new row, Predictive Analytics Life Cycle, has been added in the Reliability section of the <Asset Name> workspace.US361533

Release Date: September 6, 2019

Table 16. Resolved Issues

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

DescriptionTracking ID
Previously, in the Hierarchy section of the Asset Finder window, the Add icon () was intermittently disabled due to which you could not add an asset to an analysis. This issue has been resolved.DE110477

Cases

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

Release Date: September 27, 2019

Table 17. Enhancements and New Features

The following enhancements and new features have been added.

DescriptionTracking ID
The following enhancements have been made to the Cases OData service:
  • Filter Cases based on the Asset permissions.
  • Filter Cases based on limited visibility filtering permissions.
  • FieldValue and AuditLog for CASES_ODATA entities added.
F47045
Cross-tenant support for queries has been added to the Cases OData service.F47044
While linking alerts to a case, you can now search for the alerts using asset and alert details. Additionally, you can now remove the linked alerts from the case details page.F46499
If you export cases that contain Analysis or Evidence charts to a PDF file, the charts now appear in the exported PDF.F44080

Release Date: August 13, 2019

Table 18. Resolved Issues

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

DescriptionTracking ID
Previously, when you closed a case, the alerts related to the case were not marked Processed. This issue has been resolved.DE116756

Release Date: July 26, 2019

Table 19. Resolved Issues

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

DescriptionTracking ID
Previously, if your preferred time zone was not Coordinated Universal Time (UTC) or Site Local, when you attempted to download the PDF report of a case, an error occurred intermittently. This issue has been resolved.DE114375
Previously, if you had added an analysis template to a case, and then saved the analysis template as an evidence, the Evidence section of the PDF report for the case did not contain the analysis chart. This issue has been resolved.DE114374

Catalog

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

Release Date: September 27, 2019

Table 20. Enhancements and New Features

The following enhancements and new features have been added.

DescriptionTracking ID
If you log in to Predix Essentials as a Super User, you can now perform the following operations in the Catalog page:
  • Copy or move a Catalog folder or Catalog item between Personal folders.
  • Copy or move a Catalog folder or Catalog item between Public folders.
  • Copy or move a Catalog item between Personal and Public folders. However, you cannot copy or move a Catalog folder between Personal and Public folders.
US201765
Table 21. Resolved Issues

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

DescriptionTracking ID
Previously, after you renamed a folder within the Public folder using the Catalog Folder Properties window, if you attempted to rename the folder consecutively, an error message appeared. This issue has been resolved.DE50686

Data Loaders

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

Release Date: September 27, 2019

Table 22. Resolved Issues

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

DescriptionTracking ID
Previously, when you imported a data loader workbook that contained a date, the corresponding date field in Predix Essentials was not updated according to the Predix Essentials time zone (that is, Coordinated Universal Time (UTC)). This issue has been resolved.DE116147
Previously, when you attempted to import large analyses using the following data loaders, the operation exceeded the timeout period, causing the import process to fail.
  • Reliability Centered Maintenance (RCM)
  • Failure Modes and Effects Analysis (FMEA)
This issue has been resolved.
DE113578

Family Management

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

Release Date: September 27, 2019

Table 23. Enhancements and New Features

The following enhancements and new features have been added.

DescriptionTracking ID
The following enhancements have been made to the Behavior section of the <Field Name> workspace:
  • You can now use the YYYY-MM-DD date format in a datasheet. To facilitate this enhancement, in the Format behavior, the Custom option has been added to the Format Value drop-down list box.
  • You can now validate if the current user is assigned to a Security Group. In addition, you can compare a field value or the current user ID with a query result for complex field-level security for the Disabled and Required behavior types. To facilitate these enhancements, the Security Group and Security Group Query options have been added to the Condition drop-down list box.
  • You can now add and combine multiple behavior statements for a field behavior using the If then Else conditional logic. To facilitate this enhancement, the Add button has been added in the If and Else sections.
  • You can now validate if an entity is new or not for the Disabled, Required, and Hidden behavior types. To facilitate this enhancement, Is New and Is Not New options have been added to the Condition drop-down list box.
  • You can now create a dynamic picklist using a catalog query. To facilitate this enhancement, in the Picklist behavior, the QueryList option has been added to the Operator drop-down list box.
  • You can now use the current time stamp in a date field. To facilitate this enhancement, the default behavior of the date fields has been changed.
  • The following enhancements have been made to the Picklist behavior:
    • You can now select a system code dynamically from a value in a field.
    • You can now select a query from the catalog and then use the query to populate the picklist.
    • You can now select a query with prompts set from one or more field values and then use the query to populate the picklist.
F44331
In an offline form, if you enter a value in a field, the values in the subsequent fields are now populated based on the value you entered. To facilitate this enhancement, the drop-down list boxes are now dynamically populated with values from the system code table that references values from the related family field.US343642
Table 24. Resolved Issues

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

DescriptionTracking ID
Previously, when creating a family field, if you selected the Always Required option, the Spread to SubFamily check box was automatically selected. This issue has been resolved. DE106515
Previously, when you changed the field length for a character field using Family Management, the change did not reflect in the physical table of the data source. This issue has been resolved.DE102614
Previously, you could create a family that contained invalid data (Microsoft SQL Server reserved keywords) as the family caption even though an error message appeared. This issue has been resolved.DE97431
Previously, while executing a query in the State Configuration field in the RBI Recommendation family, the field value returned by the query was not formatted correctly, although the Formatted check box had been selected. This issue has been resolved. DE77356

Family Policies

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

Release Date: September 27, 2019

Table 25. Enhancements and New Features

The following enhancements and new features have been added.

DescriptionTracking ID
You can now use a reserved parsing keyword, such as the name of a function or a mathematical constant, as an input variable name in a Math node.US359538
When you update the execution schedule of a policy other than in the Details workspace, the Policy Trigger Job is now configured according to the updated schedule.US339892
You can now validate and execute a policy that contains a Collection Filter node with an empty collection. However, a warning message appears in the Node Execution Details window for the node, indicating that the collection is empty.US334152
To enhance the usability of the model canvas in the Design workspace, the following enhancements have been made:
  • You can now use a grid to accurately align the nodes with the other nodes in the model canvas. To facilitate this enhancement, the Enable Grid button () has been added to the canvas.
  • You no longer need to select specific connection points on nodes. To facilitate this enhancement, the button now appears when you select a node.
  • You can now bend a connector between nodes.
  • The button now appears when you point to a connector. This button enables you to define the logic path of the connector.
  • You can now select a point on the model canvas and then drag the pointer to select all nodes and connectors within a rectangular region.
  • US330552
  • US284834
  • US237250
You can now create a recurring alert using the Create Alert node.US328484
To improve the performance of policy execution, a node whose output is not used by any node of the policy model is no longer executed during the execution of the policy. This enhancement has been made to the following nodes:
  • Math
  • Query
  • Query Alerts
  • Predix Time Series
US327421
In the Properties window for a node, when you specify a family ID, the name of the family associated with the family ID is now added to the default name of the node. However, if you modify the default name of the node before specifying the family ID, the modified name of the node is not updated with the name of the family. This enhancement has been made to ensure consistent behavior of the following nodes:US325425
You can now download the image of a policy model to your local drive. To facilitate this enhancement, the Download button () has been added to the model canvas in the Design workspace.US325413
To enhance the usability of the Design workspace, the following enhancements have been made:
  • The Policy section has been removed from the toolbar.
  • The Save button now contains the text Save instead of the icon.
US321474
You can now refresh the metadata used by a policy and its nodes without refreshing the policy. To facilitate this enhancement, the Refresh Policy Metadata button () has been added to the following elements of the Design workspace:
  • The Edit section of the toolbar.
  • The Properties window for the nodes that use external metadata.
US315588
You can now retrieve the latest readings for a given time period in a Predix Time Series node. To facilitate this enhancement, the Start Time input has been made optional.US246548
You can now revert the transaction that triggers a family policy. To facilitate this enhancement, the Cancel Transaction node has been added to the Actions section of the toolbar in the Design workspace.US236247
Table 26. Resolved Issues

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

DescriptionTracking ID
Previously, in the Validation section, if you copied the null value of an instance to use it as an ad hoc test value for validation, the validation results of the policy were incorrect. This issue has been resolved.US306739
Previously, when you added the Create Alert node to a policy, only 20 values were displayed in the Alert Name drop-down list box even if more than 20 Alert Templates were defined in Predix Essentials. In addition, if you selected an Alert Name, saved the policy, and then added additional Alert Templates, when you reloaded the policy, the Alert Name setting may have been lost. These issues have been resolved. Now, up to 1000 Alert Names can be displayed.
Note: The capability to display unlimited Alert Names will be enabled in a future release.
DE117905
Previously, if you configured a Query Alerts node to retrieve alerts for a Functional Location representing a Site, Segment, or Enterprise, no alerts were returned. Also, if you configured a Create Alert node to create an alert for a Functional Location representing a Site, Segment, or Enterprise, no alert was created. These issues have been resolved.DE117298
Previously, the Query Alert node retrieved a maximum of 100 alerts regardless of the number available within the requested time range, and there was no indication that the result was truncated. This issue has been resolved. Now, the Query Alert node retrieves up to 1,000 alerts, and if the result is truncated, a notification appears in the execution history details.DE117288
Previously, if you configured the Policy input of a Sub Policy node, then copied and pasted the node, the copy of the Sub Policy node did not display the input fields for the specified Policy. This issue has been resolved.DE116740
Previously, if you attempted to access a policy containing an Entity, Create Entity, or Edit Entity node referencing an entity family that did not exist in Predix Essentials, the policy failed to load. This issue has been resolved.DE113400
Previously, if you entered a value in the Value section of a Text node that could be interpreted as a date or time span (for example, Sunday or 30d), the value was converted to the standard display format for a date or time span prior to being inserted into the Text Pattern. This issue has been resolved. Now, the Text node treats these values as strings.
Note: This change may affect the behavior of the pre-existing policies. Before you upgrade, you must review the policy designs to ensure that the Text node is configured so that the date and time and the time span values are mapped from the Constant node.
DE113062
Previously, if a sub policy contained multiple Return Value nodes with the same name, when you mapped the results from the sub policy to a successor node, the successor node input value list displayed the Return Value name multiple times, even though a single value was returned from the sub policy. This issue has been resolved. Now, the Return Value name is displayed only once in the input value list.DE113041
Previously, if you specified an input value in a Constant node that could be interpreted as a date or a time span (for example, today or 700D) and specified string as the data type for the node, the input value was converted to a date or time span. This issue has been resolved.
Note: This change may affect the behavior of the pre-existing policies. Before you upgrade, you must review the policy designs to ensure that the correct data type is specified in all the Constant nodes.
DE112424
Previously, in the Properties window for an Edit Entity node, in the Auto-map field values section, if you selected Yes, the Entity Key Column box was enabled as a required field. This issue has been resolved. Now, in this scenario, the Entity Key Column box is enabled as an optional field, and a warning message appears in the notification bar, indicating that you have not specified any value in the Entity Key Column box.DE107430
Table 27. Known Issues

The following issues are unresolved in this release.

DescriptionTracking ID
When you export a policy from Predix Essentials V4.3.1.0.0, and then access the exported policy in an older version of Predix Essentials, the connectors in the policy model do not appear even though you can successfully validate and execute the policy. The workaround for this is to manually redraw the connectors between the nodes before making any modifications to the policy.DE116734
Table 28. Obsolete Features

As of this release, the following items are no longer available.

DescriptionTracking ID
The Close Event node has been removed from Family Policies.
Note: The functionality of the Close Event node depends on the Policy Events associated with a policy instance. As family policies do not contain any policy instances, the Close Event node did not function as expected.
DE114843

General Dashboards

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

Release Date: September 27, 2019

Table 29. Resolved Issues

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

DescriptionTracking ID
Previously, if the catalog path for a query or a graph is used in a dashboard and if it contained an ampersand (&), the widget failed to load. This issue has been resolved.DE118708
Previously, in the edit mode of the Dashboard page, you could not drag a Graph widget that did not contain a name to another location in the canvas. This issue has been resolved.DE105211

Graphs

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

Release Date: September 27, 2019

Table 30. Enhancements and New Features

The following enhancements and new features have been added.

DescriptionTracking ID
In the Settings pane, in the Series section, in the Color column, the colors have been updated.
Note: The colors in the existing graphs remain unchanged.
US313324
Table 31. Resolved Issues

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

DescriptionTracking ID
Previously, on a Stock Chart Graph with multiple lines, the tooltip labels were incorrect. This issue has been resolved.DE113773
Previously, the results displayed in a graph were incorrect if the associated query included the same family as both a predecessor and a successor to a JOIN clause, and if the query result contained the same field from each instance of the family. This issue has been resolved. DE106005
Previously, if you accessed a graph from the Catalog folder for which you had the permission to view, but if you did not have the permission to view the Catalog folder where the data source query of the graph was stored, an incorrect error message appeared. This issue has been resolved. Now, a correct error message appears, indicating that you do not have the permission to view the query result used by the graph.DE101164

Policy Designer

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

Release Date: September 27, 2019

Table 32. Enhancements and New Features

The following enhancements and new features have been added.

DescriptionTracking ID
You can now execute any one or all the active instances associated with a Policy on demand without modifying the existing execution settings configured for the policy. To facilitate this enhancement:
  • A new button, Execute Now, has been added to the Details workspace.
  • A new button, , has been added to the Instances section of the Design workspace.
US359689
You can now use a reserved parsing keyword, such as the name of a function or a mathematical constant, as an input variable name in a Math node.US359538
You can now configure a policy to create an execution history log record for all the executions or only the executions that result in an error.US345229
To prevent disruptions of the Policy Execution Service by policies that take too long to execute, a time limit of 15 minutes has been introduced for executing a policy instance.US344236
When you update the execution schedule of a policy other than in the Details workspace, the Policy Trigger Job is now configured according to the updated schedule.US339892
You can now validate and execute a policy that contains a Collection Filter node with a blank collection. However, a warning message appears in the Node Execution Details window for the node, indicating that the collection is blank.US334152
To enhance the usability of the model canvas in the Design workspace, the following enhancements have been made:
  • You can now use a grid to accurately align the nodes with the other nodes in the model canvas. To facilitate this enhancement, the Enable Grid button () has been added to the canvas.
  • You no longer need to select specific connection points on nodes. To facilitate this enhancement, the button now appears when you select a node.
  • You can now bend a connector between nodes.
  • The button now appears when you point to a connector. This button enables you to define the logic path of the connector.
  • You can now select a point on the model canvas and then drag the pointer to select all nodes and connectors within a rectangular region.
  • US330552
  • US284834
  • US237250
You can now create a recurring alert using the Create Alert node.US328484
To improve the performance of policy execution, a node whose output is not used by any node of the policy model is no longer executed during the execution of the policy. This enhancement has been made to the following nodes:
  • Entity
  • Math
  • Query
  • Query Alerts
  • Predix Time Series
US327421
In the Properties window for a node, when you specify a family ID, the name of the family associated with the family ID is now added to the default name of the node. However, if you modify the default name of the node before specifying the family ID, the modified name of the node is not updated with the name of the family. This enhancement has been made to ensure consistent behavior of the following nodes:
  • Entity
US325425
You can now download the image of a policy model to your local drive. To facilitate this enhancement, the Download button () has been added to the model canvas in the Design workspace.US325413
To enhance the usability of the Design workspace, the following enhancements have been made:
  • The Policy section has been removed from the toolbar.
  • The Save button now contains the text Save instead of the icon.
US321474
You can now refresh the metadata used by a policy and its nodes without refreshing the policy. To facilitate this enhancement, the Refresh Policy Metadata button () has been added to the following elements of the Design workspace:
  • The Edit section of the toolbar.
  • The Properties window for the nodes that use external metadata.
US315588
When you define the execution settings for a policy that does not contain an active instance, a warning message now appears in the notification bar, indicating that the policy does not contain any active instance to execute.US311955
You can now retrieve the latest readings for a given time period in a Predix Time Series node. To facilitate this enhancement, the Start Time input has been made optional. US246548
Table 33. Resolved Issues

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

DescriptionTracking ID
Previously, if an entity that was specified as a trigger for automatic policy execution was modified more than once within a short time span (that is, less than one second), only one policy execution was triggered. This feature, which was implemented to prevent unintended duplicate policy executions, resulted in some intended policy executions being skipped. This issue has been resolved. Now, policy execution is triggered each time an entity is modified, except for policies that are triggered by new Readings added to a Measurement Location.
Note: For policies that are triggered by new Readings added to a Measurement Location, duplicate policy executions are still prevented because the insertion of new Readings using the Rounds Data Collection module results in multiple entity updates.
US324385
Previously, in the Validation section, if you copied the null value of an instance to use it as an ad hoc test value for validation, the validation results of the policy were incorrect. This issue has been resolved.US306739
Previously, when you added the Create Alert node to a policy, only 20 values were displayed in the Alert Name drop-down list box even if more than 20 Alert Templates were defined in Predix Essentials. In addition, if you selected an Alert Name, saved the policy, and then added additional Alert Templates, when you reloaded the policy, the Alert Name setting may have been lost. These issues have been resolved. Now, up to 1000 Alert Names can be displayed.
Note: The capability to display unlimited Alert Names will be enabled in a future release.
DE117905
Previously, while accessing Predix Essentials using Internet Explorer 11, when you accessed a policy that contained a Health Indicator node, the policy did not load or took a long time to load. This issue has been resolved.DE117337
Previously, if you configured a Query Alerts node to retrieve alerts for a Functional Location representing a Site, Segment, or Enterprise, no alerts were returned. Also, if you configured a Create Alert node to create an alert for a Functional Location representing a Site, Segment, or Enterprise, no alert was created. These issues have been resolved.DE117298
Previously, the Query Alert node retrieved a maximum of 100 alerts regardless of the number available within the requested time range, and there was no indication that the result was truncated. This issue has been resolved. Now, the Query Alert node retrieves up to 1,000 alerts, and if the result is truncated, a notification appears in the execution history details.DE117288
Previously, if you configured the Policy input of a Sub Policy node, then copied and pasted the node, the copy of the Sub Policy node did not display the input fields for the specified Policy. This issue has been resolved.DE116740
Previously, if you attempted to access a policy containing an Entity, Create Entity, or Edit Entity node referencing an entity family that did not exist in Predix Essentials, the policy failed to load. This issue has been resolved.DE113400
Previously, if you entered a value in the Value section of a Text node that could be interpreted as a date or time span (for example, Sunday or 30d), the value was converted to the standard display format for a date or time span prior to being inserted into the Text Pattern. This issue has been resolved. Now, the Text node treats these values as strings.
Note: This change may affect the behavior of the pre-existing policies. Before you upgrade, you must review the policy designs to ensure that the Text node is configured so that the date and time and the time span values are mapped from the Constant node.
DE113062
Previously, if a sub policy contained multiple Return Value nodes with the same name, when you mapped the results from the sub policy to a successor node, the successor node input value list displayed the Return Value name multiple times, even though a single value was returned from the sub policy. This issue has been resolved. Now, the Return Value name is displayed only once in the input value list.DE113041
Previously, if you specified an input value in a policy instance for a Point Value node or specified a value in a Constant node that could be interpreted as a date or a time span (for example, today or 700D), and if you specified string as the data type for the node, the input value was converted to a date or time span. This issue has been resolved.
Note: This change may affect the behavior of the pre-existing policies. Before you upgrade, you must review the policy designs to ensure that the correct data type is specified in all the Constant and Point Value nodes.
DE112424
Previously, when you accessed a policy, the following issues may have occurred:
  • The mappings between the output fields of the predecessor nodes and the input fields of the successor nodes were not retained.
  • Incorrect error messages appeared in the notification bar.
These issues have been resolved.
DE110027
Previously, in the Properties window for an Edit Entity node, in the Auto-map field values section, if you selected Yes, the Entity Key Column box was enabled as a required field. This issue has been resolved. Now, in this scenario, the Entity Key Column box is enabled as an optional field, and a warning message appears in the notification bar, indicating that you have not specified any value in the Entity Key Column box.DE107430
Previously, in the Instances section of a policy that contained a Predix Time Series node, if you specified a functional location record representing an enterprise, site, or segment in the asset hierarchy as the primary record of the policy, an error occurred and no input suggestions appeared for the Predix Time Series node. This issue has been resolved.DE105465
Previously, if the Predix Essentials database contained an active policy configured for automatic execution, and if you added the database as a new data source on the Predix Essentials server, the policy was not executed as per the execution schedule until you updated the policy. This issue has been resolved.DE53608
Table 34. Known Issues

The following issues are unresolved in this release.

DescriptionTracking ID
When you export a policy from Predix Essentials V4.3.1.0.0, and then access the exported policy in an older version of Predix Essentials, the connectors in the policy model do not appear even though you can successfully validate and execute the policy. The workaround for this is to manually redraw the connectors between the nodes before making any modifications to the policy.DE116734

Release Date: September 6, 2019

Table 35. Resolved Issues

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

DescriptionTracking ID
Previously, a policy that was configured to be triggered when an Entity was created or modified was intermittently not triggered when the trigger event occurred. This issue has been resolved.
  • DE116926
  • DE114823
Previously, an error message stating that the session had expired appeared periodically in the policy execution results. This issue has been resolved.DE113039

Queries

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

Release Date: September 27, 2019

Table 36. Enhancements and New Features

The following enhancements and new features have been added.

DescriptionTracking ID
You can now use the general form of the CASE expression to create a Meta-SQL conditional query.

Example: Use of the general form of the CASE expression in a query

CASE
WHEN [MI_ACTION].[MI_ACTION_DESCRIPTION_T] LIKE '%lubricant%' THEN
'Lubrication Action'
ELSE
'Other'
END
US311695
To make large queries easier to understand and maintain, you can now define multiple CTE query definitions in a single query.US304986
Table 37. Resolved Issues

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

DescriptionTracking ID
Previously, the Number/Mathematical Functions MOD and % did not function and returned an error message. Due to this, you could not determine the remainder from a division operation. This issue has been resolved. Now, the Modulus Meta-SQL function has been introduced for determining the remainder from a division operation.DE113169
Previously, if you selected a null date from the query parameter window, an error message appeared in an Oracle database. This issue has been resolved. Now, null dates are excluded from the query parameter values.DE107985
Previously, when you ran an aggregate query that performed a calculation on the results column of a stored query that contained both TOP and ORDER BY clauses, the aggregate query returned an incorrect value. This issue has been resolved.DE104815
Previously, in the Conditions section of the Design workspace, when you scrolled down in the grid using the scroll bar, you could not scroll up using the scroll bar. This issue has been resolved.DE104612
Previously, in an Oracle database, when you ran a query that contained the TOP clause but no ORDER BY clause in formatted mode, the records that appeared in the Results workspace were different from the records that appeared when you ran the same query in unformatted mode. This issue has been resolved.DE104520
Previously, when you ran a query with the Limit Results to Top condition, if the number of records that were returned was less than the value specified in the Limit Results to Top box, this value appeared as the record count in the Results workspace, instead of the actual record count. This issue has been resolved. DE104519
Previously, for a query other than the SELECT query, in the View Query column of the Query page, when you selected a link to access the results-only view of the query, an incorrect error message appeared. This issue has been resolved.DE103993
Previously, in the Condition section of the Design workspace, when you accessed a simple expression in the Criteria or Or cell, the expression appeared in the Advanced section instead of the Simple section of the Expression Builder window, and the Simple tab was disabled. This issue has been resolved.DE103971
Previously, in an Oracle database, when you ran a query that contained the MI_DatePart function, incorrect values appeared in certain columns containing the parts of the date in the query results. This issue has been resolved.DE102611
Previously, when you attempted to run a formatted query containing multivalue fields, an error message appeared, and no results were returned. This issue has been resolved.
Note: For limitations in running queries containing multivalue fields in an Oracle data source, refer to: Known Issue KBA V4 – Error message appears when you run a query with multivalue fields.
DE102144
Previously, in the Design workspace, when you saved a query for which the Show Totals check box was selected, in the Conditions section, the column that contained the value Group By in the Total row and a value in the Criteria row was duplicated. This issue has been resolved.DE101176
Previously, you could access a query that contained the EXISTS condition for the SELECT subquery in the Design workspace.
Note: The Meta-SQL code cannot be represented in the Design workspace because the EXISTS condition does not have an associated column. Therefore, it should not be accessible from the Design workspace.

This issue has been resolved. Now, when you attempt to access the query from the Design workspace, a message appears, stating that the query cannot be displayed in the Design workspace.

DE100395
Previously, when you accessed a query in the Design workspace and cleared the Include check box for a column, the code related to the column was deleted from the SQL workspace when the query was saved. This issue has been resolved.DE97437
Previously, in the Design workspace, in the Conditions section, when you selected the Show Totals check box, and then selected the value Count in the Total cell for a field that contained an expression, the COUNT function was not added to the SQL code in the SQL workspace. In addition, when you cleared the Show Totals check box for a query that contained the COUNT function in the SQL code in the SQL workspace, the COUNT function was not deleted from the SQL code. These issues have been resolved.DE93645
Previously, when you ran a query that contained a prompt, the following issues existed in the Enter Parameter Values window:
  • You could not select a value from any other drop-down list box.
  • If the underlying query for a parameter value was invalid, an error message appeared as selectable values within the corresponding drop-down list box in the window.

These issues have been resolved.

DE50924
Table 38. Obsolete Features

As of this release, the following items are no longer available.

DescriptionTracking ID
The fields that appeared when the Include check box was cleared no longer appear in the Entity Key drop-down list box in the Specify Parameters section of the URL Builder window. This change has been made because when you selected a field when the Include check box was cleared, an invalid link was created.US313866

Release Date: July 26, 2019

Table 39. Resolved Issues

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

DescriptionTracking ID
Previously, if conditions were defined for a query, and if you attempted to add a condition in the Or row of the Conditions section, an error occurred. This issue has been resolved.DE112501

Record Manager

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

Release Date: September 27, 2019

Table 40. Resolved Issues

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

DescriptionTracking ID
Previously, if you had accessed Predix Essentials using Internet Explorer, the horizontal scroll bar in the bulk data form did not operate as expected. This issue has been resolved.DE90472
Table 41. Obsolete Features

As of this release, the following items are no longer available.

DescriptionTracking ID
You can no longer create a site reference record by selecting the Create New Record button () and entering a value in the Name box in the Site Reference datasheet. Site reference records can be created only using the Unified Asset Ingestion Data Loader.US348948

Results Grid

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

Release Date: September 27, 2019

Table 42. Enhancements and New Features

The following enhancements and new features have been added.

DescriptionTracking ID
The user interface of the Results Grid feature has been enhanced with a new look and feel. Additionally, the performance of the Results Grid feature has been improved.
Note: The images for the following modules in the GE Digital help system have been updated. Images for the remaining modules will be updated in a future release.
  • Asset Health Manager
  • Analytics
  • eLog
  • GAA Wind
  • General Dashboard
  • Policy Designer
  • Production Loss Analysis
  • Queries
  • RScript
F44103
Table 43. Known Issues

The following issues are unresolved in this release.

DescriptionTracking ID
With the Web accessibility feature enabled in Chrome, performance degradation is observed in filtering and sorting of Data grids which have configured multiple selection of rows. By default the Web accessibility flag is off, in case you see degradation, you can check the status of the flag and disable it.

To disable the flag and check the status, enter chrome://accessibility/ in your chrome browser and clear the option Web accessibility.

DE118458

Risk Matrix

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

Release Date: September 27, 2019

Table 44. Enhancements and New Features

The following enhancements and new features have been added.

DescriptionTracking ID
In the default risk matrix, the colors associated with risk thresholds have been modified to improve contrast.US335434
Table 45. Resolved Issues

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

DescriptionTracking ID
Previously, in the financial risk control, you could not calculate the financial consequence if the following fields did not contain a value:
  • Production Loss
  • Maintenance Cost

This issue has been resolved. Now, you can calculate the financial consequence if any one of the fields contain a value.

US333940

Schedule Logs

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

Release Date: September 27, 2019

Table 46. Enhancements and New Features

The following enhancements and new features have been added.

DescriptionTracking ID
You can now delete the historical Schedule Logs entries.US337522

Search

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

Release Date: September 27, 2019

Table 47. Resolved Issues

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

DescriptionTracking ID
Previously, when you performed an advanced search by defining a numeric field condition where the numeric field had a UOM associated with it, the records returned by the search did not contain a UOM. This issue has been resolved.DE98915

ServiceMax UDLP

This topic contains a list of product changes released for this adapter.

Release Date: September 27, 2019

Table 48. Known Issues

The following issues are unresolved in this release.

DescriptionTracking ID
The synchronization of data from Predix Essentials to ServiceMax is not functional.DE119075

System Requirements

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

Release Date: September 27, 2019

Table 49. Enhancements and New Features

The following enhancements and new features have been added.

DescriptionTracking ID
APM Mobile is now compatible with Zebra TC-75X touch computer and utilizes both the integrated barcode scanning and the NFC RFID tag scanning. US351912

Tenant Preferences

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

Release Date: September 27, 2019

Table 50. Enhancements and New Features

The following enhancements and new features have been added.

DescriptionTracking ID
You can now access Route Manager from the Tenant Preferences page.F46374

Time Series Data

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

Release Date: September 27, 2019

Table 51. Resolved Issues

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

DescriptionTracking ID
Previously, when you attempted to delete time series data, even though you had the Delete Timeseries permission, an error occurred. This issue has been resolved.DE119509

Release Date: August 13, 2019

Table 52. Enhancements and New Features

The following enhancements and new features have been added.

DescriptionTracking ID
To enhance the usability when retrieving time series data from the OSM data source, queries now run asynchronously. Asynchronous queries enable applications to continually poll the Time Series Data service to obtain the query results.
Note: This is applicable only for OSM data sources that can support the asynchronous query method.
F39400

Units of Measure Conversions

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

Release Date: September 27, 2019

Table 53. Resolved Issues

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

DescriptionTracking ID
Previously, when you converted the original UOM value to a new UOM value, the calculation was based on the last value instead of the original value. This issue has been resolved. Now, when you convert a UOM using the Unit of Measure Converter window, the calculation is based on the original value.DE96069

Release Date: July 26, 2019

Table 54. Resolved Issues

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

DescriptionTracking ID
Previously, in the UoM field, when you searched for a converted value, the search was applied on the original UoM data instead of the converted value in a query result. In addition, the issue data was not filtered correctly. This issue has been resolved. Now, the search on the UoM field works according to the User conversion set.DE113353

Users and Permissions

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

Release Date: September 6, 2019

Table 55. Resolved Issues

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

DescriptionTracking ID
Previously, you could access a Map query in the Maps tool only if you had one of the following privileges:
  • You were assigned to MI Configuration Role Security Group.
  • You were a Super User.

This issue has been resolved. Now, all the Predix Essentials users can access the Map queries in the Maps tool.

DE115905