Predix Essentials Release Notes for the First Quarter of 2019

Action Management

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

Release Date: March 29, 2019

Table 1. Enhancements and New Features

The following enhancements and new features have been added.

DescriptionTracking ID
To enhance usability, in the Recommended Actions section, the email address value entered in the From field in the Email Settings page is now used when you configure a Recommended Action to send an alert.US296242
To maintain consistency, in the Recommendations pane, State Management is now controlled by the same functionality as other Predix Essentials modules.US283474
Table 2. Resolved Issues

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

DescriptionTracking ID
Previously, when you accessed Predix Essentials, if you attempted to navigate to Action Management, the Enter Parameter Values window appeared. This issue has been resolved.DE98575
Previously, if your culture setting had a culture other than English, and you accessed the Recommendation Filters window, the States were not translated to the language based on your culture setting. This issue has been resolved.DE96432
Previously, if your database contained a large number of actions, and you navigated to the Strategy Actions workspace, the process sometimes timed out. This issue has been resolved.DE93594
Previously, in the Recommended Actions tab, if you selected the Filter button (), the list of possible options was not properly localized. This issue has been resolved.DE93359
Previously, in the Recommended Actions pane, the state of Recommended Actions was not properly localized. This issue has been resolved.DE89662

Alerts

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

Release Date: March 29, 2019

Table 3. Enhancements and New Features

The following enhancements and new features have been added.

DescriptionTracking ID
You can now perform maintenance of SmartSignal analytics from alerts and change the status of the alerts to In Process Maintenance to indicate the analytics maintenance activity.F42107
Alert escalation and de-escalation have been introduced on latched alerts. They help you prioritize the alert for processing.F27584
You can now group columns in an alerts grid to organize data for easy access. F18466
Table 4. Resolved Issues

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

DescriptionTracking ID
Previously, in an alert email notification that you received, the link to access the alert details in the Predix Essentials application did not work. This issue has been resolved.DE98905
Previously, if an asset contained an associated alert and the name of the asset was changed, the alert still contained the old name of the asset instead of the new name. This issue has been resolved.DE98778
Previously, in an alerts grid, when you sorted the Density column in descending order, all the records did not appear. This issue has been resolved. DE94960
Previously, when you released a claimed alert, the alert did not appear in the list of unclaimed alerts. This issue has been resolved.DE94631
Previously, in the Create an Alert window, even though an inactive alert template was selected, the Create Alert button was available for selection. This issue has been resolved.DE94173
Previously, if you modified the Alert Received Time or Event Time values of a filter, and applied the changes, the changes were not saved. This issue has been resolved. DE91869
Previously, when you accessed an alert that contained recommendations and work order data, the Recommendations and Work History sections failed to load, and an error message appeared in these sections. This issue has been resolved.
Note: This issue is not applicable to legacy Predix APM.
DE87602
Table 5. Known Issues

The following issues are unresolved in this release.

DescriptionTracking ID
You cannot sort grouped columns in an alerts grid.NA

Release Date: February 08, 2019

Table 6. Enhancements and New Features

The following enhancements and new features have been added.

DescriptionTracking ID
The charts in the Analysis and Evidence sections of an alert now appear as images in the generated PDF report.
  • US285452
  • US285451
Table 7. Known Issues

The following issues are unresolved in this release.

DescriptionTracking ID
Only a PDF file of size up to 5 MB will be generated for an alert.DE101558
A generated PDF report for an alert can contain up to eight charts of an analysis or evidence.DE101488
If an analysis or evidence of an alert contains multiple cards, only the charts of the first card appear in the generated PDF report.DE100856
Export of alert details to a PDF file may take up to five minutes.NA

Release Date: January 23, 2019

Table 8. Resolved Issues

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

DescriptionTracking ID
Previously, if you had selected an asset name from the Asset Hierarchy and then applied the Asset Id or Asset Site Name filter criteria, alerts were not displayed in the Alert Inbox or Grid view. This issue has been resolved.DE98602
Previously, when you attempted to delete two evidences of an alert consecutively, an error occurred. This issue has been resolved.DE98276
Previously, for an alert that belonged to another tenant, when you selected the Asset ID or name of the asset to access the Asset Instance page, an error occurred. This issue has been resolved.DE97583
Previously, if you had selected an asset name from the Asset Hierarchy, the asset name did not appear in the Alert Inbox or Grid view. This issue has been resolved. DE96218
Previously, the internal link did not appear in the Alert Details page of the subscriber tenant even though the template that was used to create the alert had an internal link. This issue has been resolved. DE95378
Previously, if you had accessed a linked alert from a case, you could not mark the alert as processed and release the claim for the alert. This issue has been resolved.DE91357

Analysis

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

Release Date: March 29, 2019

Table 9. Enhancements and New Features

The following enhancements and new features have been added.

DescriptionTracking ID
You can enable the Y-axis ranges for SmartSignal, allowing you to view a tag's Y Min and Y Max values.F42602
You can enable point mode for SmartSignal cards, allowing the X-axis to display the number of data points selected instead of a date-time range.F42537
Analysis views from an alert now include both contributing and non-contributing tags displayed on the charts.F41386
You can filter the tag data on a SmartSignal chart by threshold.F41139
You can view the analytic tags that are On Monitor.F40892
You can select a system of measure for analysis cards.F40891
You can resize the tag panel, allowing you to view the full tag names shown in the expanded form of the tag browser. F40890
You can plot up to 40 SmartSignal tags singly or in groups.F40889
  • You can expand and collapse a residual chart for specified charts to display the delta between expected and actual values.
  • You can display the formulas associated with calculated tags on a SmartSignal Chart.
  • You can enable or disable the visibility of SmartSignal markers on SmartSignal charts.
  • You can display the configuration settings for SmartSignal Marker Visibility.
F39094
You can add one or more reference lines to a SmartSignal chart.F33718
You can display one or more Alerts for an asset or group of assets along with the contributing and non-contributing tags associated with the generated Alerts from the Tag Browser. The listed alerts for an asset display the alert's severity and color categorization.F33508; F41116
Table 10. Known Issues

The following enhancements and new features have been added.

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 click on a diagnostic marker on a SmartSignal chart, the hover information on the markers does not appear. In order to get out of the mode, you can refresh the charts and the hover information reappears.DE101633
If you enable the cross-hair mode in an analysis and then added 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 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. The workaround for this is to delete the tags, and then set the pins on the charts.DE95436
When making changes to the time series chart in multiple Y-axes mode, select Cancel, not Apply. If you select Apply, the changes are not applied nor are they visible in chart settings. The workaround for this is to select Cancel and to create the template for an ad-hoc view. Or, save the template, and then make your changes for an existing template.DE93811
Table 11. Limitations

The following enhancements and new features have been added.

DescriptionTracking ID
You must use Google Chrome to add multiple charts to a SmartSignal card. Other browsers, including Internet Explorer, are not supported when adding multiple charts to a single SmartSignal card.N/A

Analytics

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

Release Date: March 29, 2019

Table 12. Enhancements and New Features

The following enhancements and new features have been added.

DescriptionTracking ID
To enhance the usability in analytic template and deployments, you can now download a .zip file of logs containing all analytic deployments for the current version of the Analytic Template.F42079
To enhance the usability in analytic deployments, you can now configure your tenant to connect to an instance of PostgreSQL that has been previously configured on Spark runtime as one of the input data source.
  • F42077
  • F42078
To enhance the usability in analytic orchestrations, you can now schedule analytic orchestrations to run in a recurring mode for Spark runtime.F42076
To enhance the asset applicability during deployment, the asset applicability can now be derived from existing deployments and asset filters associated with each deployment. Newly commissioned assets that fit the filter criterion are automatically available for selection during deployment.F42074
To enhance the I/O Mapping step during deployment, you can now configure the Entity Type for inputs, outputs, and constants in the analytics template. During the I/O mapping step in deployment, the Entity Type tells Application Analytics to retrieve the tags and attributes of all assets and their children starting at the defined level.
Note: This is not available for all runtimes.
F42072
To enhance the usability in the analytic template creation, you can now associate a Machine Learning (ML)/Artificial Intelligence (AI) model to an analytic or blue print. This is only available for the PowerDataFabric runtime.F42071
To enhance the Scheduling step during deployment, you can now trigger an analytic to run when a specific alert event happens.
Note: This is not available for all runtimes.
F18922
Table 13. Resolved Issues

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

DescriptionTracking ID
Previously, when a deployment used more than 1000 assets but did not have all outputs explicitly mapped, then the error ConcurrentModificationException occurred and the deployment failed. This issue has been resolved.DE97332
Previously, on dedicated tenants, administrators could not access the audit logs for Analytics using the Audit Log Management. This issue has been resolved.DE94501
Previously, sometimes, even though there were no current deployments associated with the version of the analytic templates you were trying to delete, an error occurred asking you to first delete any associated deployments before you can delete the version of the analytic artifact in the template. This issue has been resolved. You can now delete analytic templates which have no current deployments.DE77551
Previously, when you modified an Analytic Template configuration after it had already been used in a deployment, the deployment status in the Deployments page was expected to display Updates Not Deployed. Sometimes, the status did not automatically refresh. This issue has been resolved.DE63501
Table 14. Known Issues
DescriptionTracking ID
If a deployment uses more than 250 assets that generate alerts at frequent intervals of less than one hour, you may not be able to access these alerts. There are some known limitations when using a combination of high-volume and high-frequency alerts generated by analytics.

If you have a need to deploy analytics that are expected to produce alerts at high frequencies and for large volume of assets (over 250), please contact the Analytics Support Team prior to deploying such analytics.

This limitation is limited to the Predix runtime environment.

A future enhancement for rendering high-frequency, high-volume analytics alerts is scheduled for a future release. At that time, all existing deployments must be re-deployed to benefit from the enhancement.

DE105943

Limitations

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

APM Connect

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

Important: To prevent processing failures, you must upgrade your on-premises, client-side jobs within two months of a Predix Essentials release to the most current version of the APM Connect client jobs. The current versions of the jobs are UDLP 2.5.0 or V2.5.1 and V2.6.0. For additional information, see UDLP Versions.

Release Date: March 29, 2019

Table 15. Enhancements

The following enhancements and new features have been added.

DescriptionTracking ID
The Automatic Data Loader now provides a way to change the processing order of the directories.US312179
Table 16. Resolved Issues

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

DescriptionTracking ID
Previously, EAM or data loader jobs would occasionally end without updating the status correctly. This issue has been resolved.
  • DE97417
  • US318351

Asset Criticality Analysis

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

Release Date: March 29, 2019

Table 17. Enhancements and New Features

The following enhancements and new features have been added.

DescriptionTracking ID
To maintain consistency in the <Asset Name> page, Asset Criticality Analysis has been moved to the Strategy section.US325270
To enhance usability in the Assessment workspace, the Assess button () has been updated to .US318204
To enhance usability when loading checklist records, the Asset Criticality Analysis (ACA Checklist) Data Loader has been added.US316936
To enhance usability, in the Assessment workspace, you can select multiple assets contained within a single analysis for assessment.US316803
To enhance usability, a new relationship family, Asset Criticality Analysis Has Assets, has been added.US310611
To enhance usability, in the Assessment workspace, an Add Asset button has been added.US310611
To enhance usability, a new column, Criticality, has been added to the Analyses section of the Asset Criticality Overview page.US309200
To enhance usability in the Assessment workspace, functionality to export an analysis has been added.US302496
From the ACA Overview page, you can now link assets to a new or existing ACA Analysis, Asset Strategy, FMEA Analysis, RBI Asset View, RCM Analysis, or System Strategy. To facilitate this enhancement, a Send To button has been added in the Assets section.
  • US301725
  • US299992
To enhance usability, the performance of the Asset Criticality Analysis (ACA) Data Loader has been improved.US300817
To enhance usability in the Analysis Details section, functionality to access Reference Documents has been added.US300551
To enhance usability in the Assessment workspace, you can now simultaneously assess multiple assets in an analysis.
  • US300471
  • US316803
To enhance usability, in the Assessment workspace, you can now add assets to and unlink assets from an analysis.US300392
To enhance usability in the Analysis Details page, the Assessment section now contains a table that displays all assets associated with the selected analysis.US300152
To enhance usability, in the Analysis Details page, in the Assessment section, the Asset Criticality Distribution chart has been added.US300151
To aid in efficiency, the State Configuration workflow that is defined for the ACA family has been simplified.US300148
To enhance usability, in the Asset Criticality Overview page, the Analyses section has been redesigned.US300143
To enhance usability, in the Asset Criticality Overview page, the new Assets section replaces the My Analyses section, which has been deprecated.US299979
To enhance usability, a new chart, Assets Assessed, has been added to the Overview page. The Assets Assessed chart displays a breakdown of the numbers of pieces of equipment that are ranked based on criticality.
  • US299973
  • US317769
To enhance usability in the Analysis Details page, the maximum Criticality value is now displayed in the page header.US299694
To enhance usability, AMS Asset integration has been added to populate the Assessment field in Criticality records.US294959
Table 18. Resolved Issues

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

DescriptionTracking ID
Previously, if you attempted to update the criticality indicator values in SAP to reflect the criticality value that you determined in Predix Essentials and the connection failed, the incorrect error message appeared. This issue has been resolved.DE89715
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.DE89669
Table 19. Obsolete Features

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

DescriptionTracking ID
All administrative Asset Criticality Analysis functions, previously accessed via the Application Settings page, have been deprecated.US300819
AMS Asset integration is no longer supported by the Risk Assessment family, as it is now used by the Criticality family.US294959

Asset Hierarchy

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

Release Date: March 29, 2019

Table 20. Enhancements and New Features

The following enhancements and new features have been added.

DescriptionTracking ID
In the Hierarchy section, for the following scenarios, a message appears at the bottom of the hierarchy, indicating that there are too many records available in the hierarchy, and you can use the search or filter option to find the required equipment or functional location.
  • If more than or equal to 500 top-level records are available in the hierarchy.
  • If more than or equal to 500 child equipment or functional locations are available for a parent functional location.
  • If you search for an equipment or a functional location, and the search results contain 500 or more equipment or functional locations.
US322281
Table 21. Resolved Issues

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

DescriptionTracking ID
Previously, while accessing the data for an asset in the <Asset Name> workspace, if you navigated away from the workspace and then attempted to access the data for the asset, an error occurred. This issue has been resolved. DE92693
Previously, if you specified filter criteria and selected an asset to view the data in the <Asset Name> workspace, when you navigated away from the workspace, and then attempted to access the data in the <Asset Name> workspace, the filter criteria that you specified was cleared. This issue has been resolved.DE92877

Asset

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

Release Date: March 29, 2019

Table 22. Enhancements and New Features

The following enhancements and new features have been added.

DescriptionTracking ID
When using the <attributeName> modifier while searching for a tag instance, results appear for both custom and reserved attributes. F680
Table 23. Known Issues

The following issues are unresolved in this release.

DescriptionTracking ID
IE 11 experiences a long-running script error when attempting to navigate to the details of an object in APM (Asset, Site, Segment, or Enterprise).DE95900
Associate/Disassociate actions are logged as Create/Delete in the Audit Logs.DE44416
Table 24. Limitations

Describe a limiting rule or circumstance related to functionality in this release.

DescriptionTracking ID

In Predix Essentials, adding or modifying assets using the Predix Essentials user interface, APIs, or Asset Ingestion Service, or bypassing the Unified Asset Ingestion Data Loader, causes the asset databases to become out-of-sync.

In Predix Essentials:
In Predix Essentials:
  • You can add, modify, or delete assets in the user interface, using APIs, or using the Asset Ingestion Service.
  • You can add tags to assets in the user interface, using APIs, or using the Asset Ingestion Service.
N/A
Table 25. Resolved Issues

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

DescriptionTracking ID
Previously, in the Select Context window, when you attempted to search for an asset, sometimes, the asset did not appear in the search results. This issue occurred because the search results displayed only the first 10 records in a sequence that matched the search string you specified, and the asset that you attempted to search did not match any of these records. Search results appear as expected.DE102986
Select and Cancel were not visible upon resize. The Context Browser resizes to show the options to 'Select' or 'Cancel' when a user resizes the browser window.DE96140
The GET call from /sites was returning all the attributes, including the deleted ones, because of the cache. This has been moved to the GEDA backlog.DE94480
When you passed anything other than the allowed parent entity CCOM Class, the task status failed. This has been moved to the GEDA backlog.DE83773
You were unable to ingest a tag with tagType as computed or sensor. Ingestion for a tagType as computed or sensor works as expected.DE76027
If a network was part of a sub-network, then it was not searchable. This feature is being deprecated in April 2019.DE75564
The Reserved Attributes Advanced search was not working when system had large volumes of reserved attributes. The Reserved Attributes Advanced search works as expected when the system has large volumes of reserved attributes.DE75378
You were intermittently unable to see ingestion logs in IE. Ingestion logs in IE are displayed as expected.DE73709
An internal server error displayed if the user sent a request with a Malformed URL. The correct error message now displays if the user sends a request with a Malformed URL.DE68896
A newly created alert (count) was not seen immediately without refreshing the page; the Date picker was not reflecting the current time. A newly created alert (count) is now reflected in the alert count.DE61811
The Timestamp was incorrect if the time zone in user preferences is set to UTC + 14(Kiritimati). The Timestamp now displays correctly in the asset faceplate.DE57601

Release Date: January 17, 2019

Table 26. Enhancements and New Features

The following enhancements and new features have been added.

DescriptionTracking ID
The asset hierarchy component (context browser) has been replaced for use with legacy Predix APM modules.F38575
You can now search for tag instances from an asset instance.F680
You can now add and delete groups for classifications using the user interface. F443
You can now remove members of a group using the user interface.F443
You can now select and add classifications to an existing group.F443
Table 27. Known Issues

The following issues are unresolved in this release.

DescriptionTracking ID
Select and Cancel are not visible upon resize of the browser page to a smaller size.DE96140
The GET call from /sites is returning all the attributes, including the deleted ones, because of the cache.DE94480
When you pass anything other than the allowed parent entity CCOM Class, the task status fails.DE83773
You are unable to ingest a tag with tagType as computed or sensor.DE76027
If a network is part of a sub-network, then it is not searchable.DE75564
The Reserved Attributes Advanced search is not working when system has large volumes of reserved attributes.DE75378
You are intermittently unable to see ingestion logs in IE (in the unified tenant).DE73709
Associate/Disassociate actions are logged as Create/Delete in the Audit Logs.DE44416
An internal server error displays if the user sends a request with a Malformed URL.DE68896
A newly created alert (count) is not seen immediately without refreshing the page; the Date picker is not reflecting the current time.DE61811
The Timestamp is incorrect if the time zone in the user preferences is set to UTC + 14(Kiritimati).DE57601
Table 28. Limitations

Describe a limiting rule or circumstance related to functionality in this release.

DescriptionTracking ID
On the Tags tab of the asset details page, users cannot search for tags using reserved attributes.N/A
Table 29. Resolved Issues

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

DescriptionTracking ID
The Asset page loads properly when Tags are from Site or Segment.DE36446

Cases

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

Release Date: March 29, 2019

Table 30. Enhancements and New Features

The following enhancements and new features have been added.

DescriptionTracking ID
You can now refresh the cases inbox, cases grid, and case details to view the latest information.F41109
You can now release the claim from a case that you own. The case can belong to the same tenant or another tenant.F38744
Table 31. Resolved Issues

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

DescriptionTracking ID
Previously, in a cases grid, the Asset Alias column was blank. This issue has been resolved. DE100785
Previously, if your user name was modified, when you updated the Notes or Evidence section of a case, the user details in these sections still contained your previous user name. This issue has been resolved.DE94606
Previously, you could not change the state of a case that belonged to another tenant. This issue has been resolved.DE94595
Previously, you could assign cases to an administrator of another tenant even though the administrator did not have the permission to access cases. This issue has been resolved.DE94443
Previously, if you ingested cases from an external source, the Created On field for each case contained the date when the case was ingested instead of the date on which the case was created. This issue has been resolved.DE92236
Table 32. Known Issues

The following issues are unresolved in this release.

DescriptionTracking ID
The comments that are added to the Recommendations section of a case are not saved.
Note: This issue is not applicable to legacy Predix APM.
DE44506

Release Date: February 08, 2019

Table 33. Enhancements and New Features

The following enhancements and new features have been added.

DescriptionTracking ID
The generated PDF report for a case now contains the Notes section of the case.US312894
The charts in the Analysis and Evidence sections of a case now appear as images in the generated PDF report.US275488
Table 34. Known Issues

The following issues are unresolved in this release.

DescriptionTracking ID
If an analysis or evidence of a case contains multiple cards, only the charts of the first card appear in the generated PDF report.DE100856
Export of case details to a PDF file may take may take up to five minutes.NA
When you export the details of multiple cases to a PDF file using the Bulk Actions menu, analysis charts in the Analysis and Evidence sections of a case does not appear in the generated PDF report.NA

Release Date: January 23, 2019

Table 35. Resolved Issues

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

DescriptionTracking ID
Previously, if a Closure Code or Status was available in the case configuration file of your tenant, but the code or status was not available in the case configuration file of another tenant, when you attempted to select the Closure Code or Status for a case that belonged to the other tenant, an error occurred. This issue has been resolved. DE96086

APM Data Extraction

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

Release Date: March 29, 2019

Table 36. Enhancements and New Features

The following enhancements and new features have been added.

DescriptionTracking ID
APM Data Extraction service has been introduced in this release. This service has been implemented based on OData v4.01 specification. Using this service, you can expose your APM database, enabling entities to be accessed using an Open Data interface. Reporting and Business Intelligence tools using OData requests can read this exposed data with the help of simple queries, enabling you to visualize and analyze the data.F40154
Table 37. Known Issues

The following issues are unresolved in this release.

DescriptionTracking ID
Data filters are not supported in Unit of Measurement (UOM) fields.DE103033
Data formatting options such as time zone conversions, currency formats, and number formats are not supported.DE102126

Data Loaders UDLP V2.6.0

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

Release Date: March 29, 2019

Table 38. Resolved Issues

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

DescriptionTracking ID
Previously, when a request from a data loader job running in the database timed out, the job status incorrectly appeared as Dataloader Enqueued. Now, the job status correctly appears as Cancelled.DE91700

Data Permissions

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

Release Date: March 29, 2019

Table 39. Enhancements and New Features

The following enhancements and new features have been added.

DescriptionTracking ID
In the Assign Users window, you can now search for a Security User using the User ID of the Security User.US291131
Table 40. Resolved Issues

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

DescriptionTracking ID
Previously, when you attempted to search for a family, the search results displayed only the families whose names started with the exact string that you specified in the search criteria. This issue has been resolved. Now, you can search for all the families whose names contain the string that you specify in the search criteria.DE87016

Family Management

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

Release Date: March 29, 2019

Table 41. Enhancements and New Features

The following enhancements and new features have been added.

DescriptionTracking ID
When you attempt to update the existing records for a given family with the modified record ID, now, a new job, UpdateTemplateIDJob, is created in the Schedule Logs page to update the existing records. This enhancement significantly improves the performance of the system while updating the records in bulk.US299142
The first report that you associate with a family becomes the default report for the family.US293868
You can now hide a datasheet belonging to a family that you do not want to appear for the corresponding records. To facilitate this functionality, the Hide check box has been added to the Datasheet Information window of the Datasheet Builder page.US290738
Table 42. Resolved Issues

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

DescriptionTracking ID
Previously, if a newly created field had been added to a datasheet belonging to the Checklist Findings family, and you attempted to access a checklist category for an inspection belonging to a checklist inspection family, an error message appeared, indicating that the datasheet failed to load. This issue has been resolved.DE101578
Previously, in the Manage ID Template window, while entering a delimiter for a field in the Delimiter box, if you entered a space, the space did not appear in the New ID Template value in the following scenarios:
  • Space is the only character in the entered value.
  • Space is the first or last character in the entered value.
This issue has been resolved.
DE92913

Family Policies

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

Release Date: March 29, 2019

Table 43. Enhancements and New Features

The following enhancements and new features have been added.

DescriptionTracking ID
To improve the performance of the Predix Time Series node, the default number of readings that the Predix Time Series node retrieves from a Time Series data source has been reduced from 500000 to 10000.US327520
The minimum time interval that you can configure to run a job that deletes the execution history logs from the database is now increased to one hour.
Note: If you had specified the time interval value for the job in minutes, the specified value is rounded up to the nearest value in hours, and the updated value appears in the Execution History Settings workspace. However, the job will continue to run at the time intervals that you had specified until you save the modified settings for the job.
US311726
You can now access the execution details of a sub policy from the calling policy. To facilitate this enhancement, the View Execution Details link, which can be used to view the policy model and execution details of the sub policy in a separate window, has been added to the Node Execution Details window for the Sub Policy node.US306756
You can now convert the output value of a node to another data type. To facilitate this enhancement, the Convert Type node has been added to the Calculations section of the toolbar in the Design workspace.US297271
While configuring the properties of a Create Alert node, you can now select the following values for the Boolean attributes:
  • Yes: Sets the attribute value to True.
  • No: Sets the attribute value to False.
To facilitate this enhancement, the Value text box corresponding to the Boolean attributes has been replaced with the Yes and No options.
DE97664
In the Properties window for the Create Alert and Query Alerts nodes, the Asset UUID field has been renamed Asset Unique ID.
  • DE90491
  • DE90280
Table 44. Resolved Issues

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

DescriptionTracking ID
Previously, if Microsoft Message Queuing (MSMQ) stopped responding or could not be accessed, the Policy Trigger Service and Policy Execution Service failed to automatically reconnect with MSMQ even after it became available again. This issue has been resolved.US307302
Previously, if the Time Series data contained a non-numeric value, the Predix Time Series node could not retrieve the data, and the execution of the policy failed. Now, in this scenario, the Predix Time Series node can retrieve both numeric and non-numeric values from the Time Series data source.DE104977
Previously, the collection of values returned by a sub policy was incorrectly mapped to the columns of the collection output of the corresponding Sub Policy node in the calling policy. This issue has been resolved.DE102425
Previously, in a policy that contained a Predix Time Series node and a primary node configured to represent an asset, if an error occurred when you specified a Time Series tag for an instance, an error message appeared every time you added or deleted any node from the policy model. This issue has been resolved. Now, in this scenario, the error message appears only when you add or delete an Input node from the policy model.DE101979
Previously, if you mapped the collection output of a node to a Last node that was not its immediate successor node in the policy model, and then mapped the output of the Last node to an Is Null node, the input mappings of the Is Null node were not retained. This issue occurred when you saved and then reloaded the policy. This issue has been resolved.DE101761
Previously, if you validated or executed a policy that contained a Math node with an invalid mathematical expression, an incorrect error message appeared, indicating an R Server connection issue. This issue has been resolved.DE98244
Previously, in the Properties window for a Create Alert node, when you specified any value other than true or false for a Boolean attribute, no error message appeared to indicate that the specified values were invalid for the attribute. However, when you executed the policy, the execution failed. This issue has been resolved. Now, the Value box corresponding to the Boolean attributes has been replaced by the Yes and No options so that you cannot specify any invalid value for the attributes.DE97664
Previously, duplicate policies for the same family and trigger could exist in the Predix Essentials database. In this scenario, you could not delete the duplicated policy. This issue has been resolved.DE95827
Previously, if you configured a policy with a Baseline Rule node for a family whose ID contained a space, the validation and execution of the policy failed. This issue has been resolved.DE91542
Previously, if you did not update the memory cache after creating or deleting a family policy, the following issues occurred:
  • The newly created policy was not executed for the associated trigger.
  • The deleted policy was executed for the associated trigger.
These issues have been resolved.
DE91303
Previously, if you executed a policy that was configured to perform an action on a recently added, modified, or deleted family or family field, the execution failed even though you could successfully validate the policy. This issue has been resolved.DE91301
Previously, in the Properties window, if you attempted to map a column of a query result to an input field, the drop-down list box to specify the column of the query result did not appear for the following nodes:
  • Create Relationship
  • Delete Entity
  • Delete Relationship
  • Edit Entity
  • R Script
This issue has been resolved.
DE90835
Previously, irrespective of the display language configured for your user account, the name of the Sub Policy node always appeared in US English. This issue has been resolved.DE89416
Previously, when you attempted to access a policy, the policy did not load if it contained the following nodes:
  • A comparison node without an input value
  • Multiple Sub Policy nodes
This issue has been resolved.
DE88744
Previously, in the toolbar of the Design workspace, nodes configured to be available only for specific licenses were available even if you did not have the corresponding licenses. This issue has been resolved.DE87323
Previously, if you had specified a time zone other than Coordinated Universal Time (UTC) for a policy with a Predix Time Series node, and then executed the policy, the time stamp values provided by the Predix Time Series node to the successor nodes were offset by the time difference between UTC and the policy time zone. This issue has been resolved.DE86461
Table 45. Obsolete Features

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

DescriptionTracking ID
In the Properties window for the Create Alert node, the Recurring option has been removed from the Field drop-down list box.DE91756

GE Dashboards

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

Release Date: March 29, 2019

Table 46. Enhancements and New Features

The following enhancements and new features have been added.

DescriptionTracking ID
Previously, when filtering or searching, the Context Browser listed assets in a flat, non-hierarchical view. With this release, the Context Browser displays the hierarchies of assets in a tree view when filtering or searching.US319710
The following widgets add support for asynchronous queries when the timespan configuration option is set to six months or more:
  • Generic Graph
  • Scatter Chart
  • Spider Web Chart
  • KPI Overview
  • US293074
  • US291737
  • US291734
  • US291731
  • US291730
You can now set the home dashboard from the dashboard browser or dashboard menu.
Note: This feature is not available in Predix Essentials.
US211742

Release Date: February 6, 2019

Table 47. Resolved Issues

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

DescriptionTracking ID
Previously, when a dashboard was created with no asset context and an Unclaimed Alerts widget was subsequently added to the dashboard, the widget did not display the correct number of unclaimed alerts. Now, the Unclaimed Alerts widget performs correctly on dashboards that do not have an asset context.DE98875

General Dashboards

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

Release Date: March 29, 2019

Table 48. Enhancements and New Features

The following enhancements and new features have been added.

DescriptionTracking ID
You can now export the contents of a dashboard to a PDF. When viewing a dashboard, you can now select the More Options button (), and then select Export to PDF.US290439

Graphs

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

Release Date: March 29, 2019

Table 49. Enhancements and New Features

The following enhancements and new features have been added.

DescriptionTracking ID
You can now export a graph to a PDF file. To facilitate this enhancement, the Export to PDF button () has been added to the Graph Result workspace.US297381
You can now define where the legend for a graph should appear in the Graph Result workspace. To facilitate this enhancement, in the graph settings pane, the Show Legend check box is now the Legend drop-down list box, where you can select a location for the legend or hide the legend.US290781
For a numeric value in the tooltip of a graph, commas now appear as the thousands delimiter. To facilitate this enhancement, the format of the numeric value for a tooltip has been changed to match the format of the numeric value in the y-axis of the graph. US283101
Table 50. Resolved Issues

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

DescriptionTracking ID
Previously, for a pie chart with more than two pie slices, if the State management enabled Family for captions or System code table for captions option was selected in the Dimension for Category window, when you removed a row in the Series section of the Settings pane and saved the graph, multiple slices were removed from the graph. This issue has been resolved.DE103948
Previously, for a pie chart with two pie slices, if the State management enabled Family for captions or System code table for captions option was selected in the Dimension for Category window, when you removed a row in the Series section of the Settings pane and saved the graph, an error message appeared. This issue has been resolved.DE103809
Previously, after a database upgrade, when you attempted to access a graph based on a query that contained a family whose state management was enabled for captions, a spinner appeared, and the graph did not load. This issue can be resolved.

For information on how to fix this issue, refer to KBA 6616.

DE101475
Previously, when you accessed a pie chart based on a query that contained family state IDs, the state IDs incorrectly appeared as graph labels. This issue has been resolved.DE100709
Previously, if you created a graph using a Crosstab query and mapped fields containing site data to the vertical axis, the graph legend and tooltips contained values from the first field in the list, regardless of the site to which you are assigned. This issue has been resolved.DE98265

Help System

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

Release Date: February 21, 2019

Table 51. Resolved Issues

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

DescriptionTracking ID
Previously, the Predix Essentials documentation contained information about the GE Digital APM mobile application. However, the functionality of the mobile application relates to GE Digital APM, not Predix Essentials. This issue has been resolved. References to the mobile application have been removed from the Predix Essentials documentation. You can access Predix Essentials on a mobile device using a web browser.US329632

Import and Export

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

Release Date: March 29, 2019

Table 52. Resolved Issues

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

DescriptionTracking ID
Previously, if a policy that was scheduled to be executed was imported, when you updated the policy, a job to execute the policy was created in addition to the existing job that was created while importing the policy. This issue has been resolved. DE98204
Previously, when you attempted to export a family that had a field with a list of valid values associated with an APM Query, and if the APM Query had a prompt configured for it, an error occurred. This issue has been resolved.DE94684
Previously, if no rules were available in a rule library project, and you attempted to export the project, an error occurred and an incorrect message appeared in the error log. This issue has been resolved. Now, an appropriate error message appears in the error log, indicating that the rules are not available in the rule library project. DE89799

Maximo UDLP V2.6.0

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

Release Date: March 29, 2019

Table 53. Enhancements and New Features

The following enhancements and new features have been added.

DescriptionTracking ID
APM Connect now supports customized mappings for Maximo Notification Management.US258012

Policy Designer

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

Release Date: March 29, 2019

Table 54. Enhancements and New Features

The following enhancements and new features have been added.

DescriptionTracking ID
To improve the performance of the Predix Time Series node, the default number of readings that the Predix Time Series node retrieves from a Time Series data source has been reduced from 500000 to 10000.US327520
The following policies are now available as part of the baseline Predix Essentials:
  • DateAdd: To add a time interval value to a time stamp value. This policy is designed to be used as a sub policy, as an alternative for a date add function in a query or R script.
  • DateDiff: To calculate the difference between time stamp values in terms of the following units of time:
    • Years
    • Weeks
    • Days
    • Hours
    • Minutes
    This policy is designed to be used as a sub policy, as an alternative for a date difference function in a query or R script.
  • US314617
  • US314615
The minimum time interval that you can configure to run a job that deletes the execution history logs from the database is now increased to one hour.
Note: If you had specified the time interval value for the job in minutes, the specified value is rounded up to the nearest value in hours, and the updated value appears in the Execution History Settings workspace. However, the job will continue to run at the time intervals that you had specified until you save the modified settings for the job.
US311726
You can now view the execution result of a Sub Policy node in the execution summary of the policy. To facilitate this enhancement, the policy execution summary has been modified to display the number of times the Sub Policy node executed the associated sub policy.US306760
You can now access the execution details of a sub policy from the calling policy. To facilitate this enhancement, the View Execution Details link, which can be used to view the policy model and execution details of the sub policy in a separate window, has been added to the Node Execution Details window for the Sub Policy node.US306756
You can now convert the output value of a node to another data type. To facilitate this enhancement, the Convert Type node has been added to the Calculations section of the toolbar in the Design workspace.US297271
When you deploy Policy Designer for the first time or upgrade to version 4.3.0.7.0, you must configure the Meridium Notification Service to enable the Policy Execution Service. DE103226
While configuring the properties of a Create Alert node, you can now select the following values for the Boolean attributes:
  • Yes: Sets the attribute value to True.
  • No: Sets the attribute value to False.
To facilitate this enhancement, the Value text box corresponding to the Boolean attributes has been replaced with the Yes and No options.
DE97664
In the Properties window for the Create Alert and Query Alerts nodes, the Asset UUID field has been renamed Asset Unique ID.
  • DE90491
  • DE90280
Table 55. Resolved Issues

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

DescriptionTracking ID
Previously, if multiple entities were associated with an entity ID that you specified in the Policy Instance Data Loader, no records associated with the entity ID were mapped to the instance. Now, in this scenario, if one of the records associated with the entity ID is linked to the primary record of the instance, the record that is linked to the primary record is mapped to the instance.US311492
Previously, if Microsoft Message Queuing (MSMQ) stopped responding or could not be accessed, the Policy Trigger Service and Policy Execution Service failed to automatically reconnect with MSMQ even after it became available again. This issue has been resolved.US307302
Previously, if the Time Series data contained a non-numeric value, the Predix Time Series node could not retrieve the data, and the execution of the policy failed. Now, in this scenario, the Predix Time Series node can retrieve both numeric and non-numeric values from the Time Series data source.DE104977
Previously, the collection of values returned by a sub policy was incorrectly mapped to the columns of the collection output of the corresponding Sub Policy node in the calling policy. This issue has been resolved.DE102425
Previously, if you frequently switched between pages, workspaces, windows, or sections while using Policy Designer for a long period of time, the following issues occurred:
  • The Design workspace took a long time to load.
  • Operations in the Design workspace, such as moving a node, took a long time.
  • The internet browser intermittently stopped responding.
These issues have been resolved.
DE102142
Previously, in a policy that contained a Predix Time Series node and a primary node configured to represent an asset, if an error occurred when you specified a Time Series tag for an instance, an error message appeared every time you added or deleted any node from the policy model. This issue has been resolved. Now, in this scenario, the error message appears only when you add or delete an Input node from the policy model.DE101979
Previously, if you mapped the collection output of a node to a Last node that was not its immediate successor node in the policy model, and then mapped the output of the Last node to an Is Null node, the input mappings of the Is Null node were not retained. This issue occurred when you saved and then reloaded the policy. This issue has been resolved.DE101761
Previously, after successfully processing data, the data loader log displayed a record count of 0. Now, the data loader log displays the correct record count.DE100703
Previously, if you deleted the Input node that represented the primary record for an instance and saved the policy, when you specified the primary record for any instance using the Policy Instance Data Loader, the primary record was not mapped to the instance. This issue has been resolved.DE99335
Previously, if you validated or executed a policy that contained a Math node with an invalid mathematical expression, an incorrect error message appeared, indicating an R Server connection issue. This issue has been resolved.DE98244
Previously, when you imported instances for multiple policies using the same Policy Instance Data Loader workbook, the following issues occurred:
  • The data loader was successfully imported without any error message.
  • The imported instances were incorrectly associated with the policies.
These issues have been resolved. Now, in this scenario, the data loader is not imported and an error message appears in the data loader log, indicating that the instances could not be imported.
DE98002
Previously, in the Properties window for a Create Alert node, when you specified any value other than true or false for a Boolean attribute, no error message appeared to indicate that the specified values were invalid for the attribute. However, when you executed the policy, the execution failed. This issue has been resolved. Now, the Value box corresponding to the Boolean attributes has been replaced by the Yes and No options so that you cannot specify any invalid value for the attributes.DE97664
Previously, in the Instances section of a policy, if you specified a Predix Time Series tag for an instance and saved the policy, when you reloaded the policy, the specified tag did not appear in the Predix Time Series box corresponding to the instance. However, the specified tag was correctly mapped to the Predix Time Series node in the Predix Essentials database, and you could successfully validate and execute the instance. This issue occurred if the instance contained a primary record and if the specified tag was not available among the first 25 tags that appeared in the Select a Time Series Tag window for the Predix Time Series box. This issue has been resolved. Now, in this scenario, the specified tag appears in the Predix Time Series box when you reload the policy.DE97202
Previously, if the deletion of an instance failed for any reason, the following issues occurred:
  • The instance was removed from the Instances section of the Design workspace. However, when you reloaded the policy, the instance reappeared in the Instances section.
  • No error message appeared.
These issues have been resolved. Now, when you attempt to delete an instance, the following events occur:
  • If the deletion takes a long time, a spinner appears, indicating that the deletion is in progress.
  • If the instance is successfully deleted, confirmation message appears.
  • If the deletion fails, an appropriate error message appears.
DE96251
Previously, when you accessed the Policy Designer Overview page, the page did not load or took a long time to load. This issue occurred when the Predix Essentials database contained a large number of execution history records. This issue has been resolved.
Note: If the issue persists, configure the Policy Designer Overview page to use the alternative query (Policy Overview – Policies Alternate Query) that has been added to the Predix Essentials Catalog. For more information on configuring the alternative query, contact Global Support Services.
DE95004
Previously, if a policy contained a Math node with a variadic function, and the variables of the variadic function represented the columns of a collection, the validation and execution of the policy failed. This issue has been resolved.DE94085
Previously, when you attempted to access a policy containing a large number of nodes, one of the following issues occurred:
  • The policy took a long time to load.
  • The policy did not load.
This issue has been resolved.
DE93538
Previously, when you attempted to import policy instance data using the Policy Instance Data Loader, the data was not imported and an error message appeared in the data loader log, indicating that the Instance ID value exceeded the maximum character limit. This issue occurred if you assigned the first field sequence number for the Policy Instance family to a field with a maximum character limit less than the number of characters in the Instance ID specified in the data loader. This issue has been resolved. Now, in this scenario, the data is successfully imported.DE93209
Previously, if you mapped the time stamp output of a node to an input field of a successor node, and then executed the policy, in the Execution Details window for the successor node, the time stamp appeared in the time zone specified for your Predix Essentials user account instead of the policy time zone. This issue has been resolved.DE91644
Previously, if you executed a policy that was configured to perform an action on a recently added, modified, or deleted family or family field, the execution failed even though you could successfully validate the policy. This issue has been resolved.DE91301
Previously, if a policy was executed by a family-level rule or another Predix Essentials module multiple times within a short duration, the execution results for the Math and Text nodes were intermittently incorrect after the first execution. This issue has been resolved.DE89726
Previously, irrespective of the display language configured for your user account, the text always appeared in US English for the following items:
  • Name of the Sub Policy node in policies.
  • Name of the policy instance data loader in the Import Data window of the Data Loaders page.
This issue has been resolved.
DE89416
Previously, when you attempted to access a policy, the policy did not load if it contained the following nodes:
  • A comparison node without an input value
  • Multiple Sub Policy nodes
This issue has been resolved.
DE88744
Previously, in the toolbar of the Design workspace, nodes configured to be available only for specific licenses were available even if you did not have the corresponding licenses. This issue has been resolved.DE87323
Previously, if you had specified a time zone other than Coordinated Universal Time (UTC) for a policy with a Predix Time Series node, and then executed the policy, the time stamp values provided by the Predix Time Series node to the successor nodes were offset by the time difference between UTC and the policy time zone. This issue has been resolved.DE86461
Table 56. Obsolete Features

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

DescriptionTracking ID
In the Properties window for the Create Alert node, the Recurring option has been removed from the Field drop-down list box.DE91756

Queries

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

Release Date: March 29, 2019

Table 57. Resolved Issues

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

DescriptionTracking ID
Previously, if your culture setting was anything other than English and you ran a query with a field that was added twice with different aliases, if one of the fields was configured such that it did not appear in the query results, no values were displayed in the query results. This issue has been resolved. DE103503
Previously, when you used the ORDER BY clause to sort a column in a query that contained the UNION operator or a SELECT DISTINCT statement and ran the query, an incorrect column was sorted in the query results. This issue occurred when the ORDER BY clause referenced an expression column by its alias. This issue has been resolved.DE101497
Previously, when you ran a query that used the UNION operator as a formatted query, an error occurred, and the query did not return any results. This issue has been resolved.DE101292
Previously, when you ran a query that used the UNION operator to combine the result set of two SELECT statements containing a WHERE clause, if the WHERE clause did not contain an AND operator, an error occurred, and the query did not return any results. This issue has been resolved.DE100416
Previously, when you ran a formatted query with the limit results to top condition, the query did not return the expected results. This issue has been resolved.DE99794
Previously, in the Conditions section of the Design workspace, when you hovered over a Hyperlink, Criteria or Or cell, a tooltip did not appear. This issue has been resolved.DE94420
Previously, when you attempted to export a query result set to a dataset, only the first 100 records in the query result set were exported. This issue has been resolved. DE93641
Previously, when you ran a query that joined a family to multiple sub-families and the relationship family caption contained a hyphen, an error occurred, and the query did not return any results. This issue has been resolved.DE89510
Previously, when you accessed a Crosstab query in which a Total cell contained an aggregate function, incorrect values appeared in the Field and Alias cells. This issue has been resolved. DE88704
Previously, when you exported the results of a formatted query that contained the ENTY_KEY and FMLY_KEY fields to a dataset, the ENTY_KEY and FMLY_KEY columns in the dataset were blank. This issue has been resolved.DE88523
Previously, when you ran a formatted query where the same family was selected as the source and the related source, and the same field was selected from both sources, the related source field incorrectly displayed the source field value in the query results. This issue has been resolved.DE88332
Previously, when you ran a formatted query to create left joins on two subqueries that pull data from the same family, the query did not return the expected results. This issue has been resolved.DE88141
Previously, after selecting the Limit Results to Top check box and entering a value, if you ran an unformatted query and exported the query results to a Microsoft Excel file, the exported data in the file was different from the actual query results. This issue has been resolved.DE79754

Record Manager

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

Release Date: March 29, 2019

Table 58. Resolved Issues

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

DescriptionTracking ID
Previously, if you had uploaded a reference document that had a file name with Chinese characters and then downloaded the same document using the Internet Explorer browser, the name of the downloaded document was incorrect. This issue has been resolved.DE90473
Previously, while creating or modifying a record, the drop-down list boxes available in the datasheet were not highlighted with red borders, although a value was required for each drop-down list box. This issue has been resolved.DE90469
Previously, if a query had a field displaying date and time, if you used the query as a data source for a record that belonged to the Conditional Alerts family and scheduled the conditional alert, the time for a specific date displayed in the query result did not match the corresponding time displayed in the email that was sent when the conditional alert was executed. This issue has been resolved. DE87509
Previously, when you attempted to upload a reference document that had a file name with Russian characters, an error message appeared, indicating that the file type was not supported. This issue has been resolved. Now, you can upload a reference document with a Russian file name. DE87014
Previously, in the Record Explorer page, when you attempted to access a record that had a large number (approximately 30000) of successor records that are associated with the same family, an error occurred. This issue has been resolved.US316553

Risk Matrix

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

Release Date: March 29, 2019

Table 59. Resolved Issues

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

DescriptionTracking ID
Previously, if the Not Applicable check box was selected for a Risk Matrix category, the overall risk would not update until the Risk Matrix was saved. This issue has been resolved.DE89701

SAP and SAP PI UDLP V2.6.0

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

SAP and SAP PI - Release Date: March 29, 2019

Table 60. Enhancements and New Features

The following enhancements and new features have been added.

DescriptionTracking ID
The SAP Adapter now provides a Planned Work Adapter that enables you to plan maintenance work for assets.US318099
Table 61. Resolved Issues

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

DescriptionTracking ID
Previously, when using the Work Management adapter, after a confirmation record was created for an inspection, the Work Order Number field was not cleared from the Inspection record. Now, the Work Order Number field is cleared correctly.DE105082
Previously, the SAP PI adapter incorrectly populated the Last Date and Next Date fields when the adapter created a Work Order record. Now, the SAP PI adapter no longer populates these fields.DE102158
Previously, the documentation did not provide sufficient information about the ABAP package required to support migrating from V3.6 to V4.3 of Predix Essentials. Now the documentation correctly identifies the V3.6 ABAP package as 0.7, 360_600 Level 10.DE101136
Previously, Work History records associated with Technical Objects displayed incorrect Site data. Now, the Site data displays correctly.
  • DE100582
  • DE100583
When you attempted to save an updated Inspection record, the record failed to save and the following error message was displayed: Failed to save entity: "RFC_GET_STRUCTURE_DEFINITION"DE90036

Schedule Logs

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

Release Date: March 29, 2019

Table 62. Enhancements and New Features
DescriptionTracking ID
In the Description column of the Schedule Logs page, you can now view the ID of a scheduled Strategy Macro.US290782

Search

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

Release Date: March 29, 2019

Table 63. Enhancements and New Features

The following enhancements and new features have been added.

DescriptionTracking ID
Now, when you perform a global search, the records belonging to the Equipment and Functional Location families appear at the top in the search results.US313364
Table 64. Resolved Issues

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

DescriptionTracking ID
Previously, when you logged in to Predix Essentials as a Polish user and performed an advanced search on a family, the IDs that appeared in the Record ID column did not contain links. This issue has been resolved.DE85104

State Management

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

Release Date: March 29, 2019

Table 65. Enhancements and New Features

The following enhancements and new features have been added.

DescriptionTracking ID
In the State Assignments window, the following enhancements have been made:
  • In the Assignee column, the User ID for each Security User is displayed along with the first name and last name of the Security User.
  • You can now search for a Security User using the first name, last name, or User ID of the Security User to assign the user to a state.
US287182

Time Series Data

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

Release Date: March 29, 2019

Table 66. Enhancements and New Features

The following enhancements and new features have been added.

DescriptionTracking ID
To enhance usability when retrieving time series data archived in S3 storage, queries can now run asynchronously. Asynchronous queries enable applications to continually poll the Time Series Data service to obtain the query results. This feature is available only in new Predix Time Series service schema; currently, it is not supported in AWS West.F34716
To enable users to permanently delete time series data, a new DELETE endpoint has been added. The endpoint enables users to free up storage space and reduce storage costs. This feature is available only in new Predix Time Series service schema; currently, it is not supported in AWS West.F20644

Users and Permissions

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

Release Date: March 29, 2019

Table 67. Enhancements and New Features

The following enhancements and new features have been added.

DescriptionTracking ID
If your tenant has multiple identity providers configured, you can now select an identity provider in a drop-down list box when adding users individually or in bulk. When adding a user, the domain of the email address provided must match what is configured for the selected identity provider.US336292
A new window for assigning assets has been implemented. This update provides improvements to overall usability when assigning assets and permissions, including the following:
  • You can now select multiple assets.
  • You can now select either a single asset or the hierarchy of assets below an asset.
  • Assigning permissions to an asset also assigns permissions to the hierarchy of assets below it.
US332524
A tenant can now be configured with multiple identity providers, each restricted by a set of email domains. As a result of this enhancement:
  • A user administrator cannot create a user in the User Account and Authentication (UAA) service with an email domain matching that of an identity provider.
  • Upon attempting to log in, an existing UAA user with a conflicting email domain will be redirected to the associated identity provider.
  • Permissions assigned to an existing UAA user with a conflicting email domain must be assigned to the newly created federated user (the existing UAA user can then be removed).
  • When a user signs in to a tenant configured with multiple identity providers, the UAA discovery page will appear prior to the corresponding identity provider sign-in page.
US332523
In the User Management page, the following permissions have been added for the Mechanical Integrity module. When these permissions are assigned to Security Users, the users are granted privileges to manage the states for inspection recommendations.
  • SC Recommendation Management Implementer: The users can change the status of the Recommendations from the Approved or In Progress state to the Completed state.
  • SC Recommendation Management Reviewer: The users can change the status of the Recommendations from the Pending Approval state to the Pending Review, Approved, Canceled, or Rejected state.
US307829