First Quarter of 2021

Release Date: March 26, 2021

This topic provides a list of product changes released for this module on this date.

Table 1. Enhancements and New FeaturesThe following issues, which existed in one or more previous versions, have been resolved.
DescriptionTracking ID
You will now be able to choose to get Interpolated data in the Predix Time Series node. To facilitate this enhancement, Use Interpolated Data option has been added in the Predix Time Series node properties window. When this option is selected, you must select the interpolation method and enter the interpolation interval in seconds.US469390
Table 2. Resolved IssuesThe following issues, which existed in one or more previous versions, have been resolved.
DescriptionTracking ID
Previously, the policy execution service user permissions may have been intermittently invalid, resulting in:
  • No data was retrieved when you executed a policy using Predix Time Series nodes.
  • When you executed a policy using Create Alert or Query Alerts nodes an error occurred.

These issues have been resolved.

DE156299

Release Date: March 27, 2020

This topic provides a list of product changes released for this module on this date.

Table 3. Enhancements and New Features

The following enhancements and new features have been added.

DescriptionTracking ID
You must now specify the family ID or family Keys(s) for entities that you want to create in a relationship node. To facilitate this enhancement, the Predecessor Family ID, Predecessor Family Key(s), Successor Family ID, Successor Family Key(s) sections are added in the Create Relationship node properties window of Policy Designer.
Note: When you upgrade the APM database to v4.6.0.0.0, policies containing the Create Relationship node will be upgraded only where the entity keys and the family of the entities to be created can be determined automatically.
US454314
You can now configure the catalog path input of the Query node to accept the output from a predecessor node. To facilitate this enhancement, select the switch to field input button () under query path to choose an input from another node.
Note: When the query path is sourced from a predecessor node, the results collection output from the query node can be used only when you do not need to select a specific column in the collection.
US414721
You can now set the time or number of occurrences by when a scheduled execution should end in a policy. To facilitate this enhancement, the End Repeat option is added to the Scheduled Execution section of the Details workspace in the Policy Designer page.US402265
You must now specify the family for entities that you want to delete in a policy. To facilitate this enhancement, the Family Key(s) section is added in the Delete Entity node properties window of Policy Designer. For more information, refer to Upgrade Policy Designer.
Note: When you upgrade the APM database to v4.6.0.0.0, policies containing the Delete Entity nodes will be upgraded only where the entity keys and the family of the entities to be deleted can be determined automatically.
US397521 and US452099
You can now configure the maxSubPolicyDepth. This setting limits the number of levels of sub policy calls and ensures that recursive policy executions cannot occur. The default maximum sub policy depth is set to 10.US374957
Table 4. Resolved Issues

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

DescriptionTracking ID
Previously, when you attempted to delete a policy instance with large number of execution history records, an error occurred. This issue has been resolved.US459366
Previously, when you executed a policy with two or more levels of sub-policies, and the second or lower level of sub-policies had an error, the execution status of the policy did not indicate that an error had occurred. This issue has been resolved.DE143955
Table 5. Known Issues and Limitations

The following known issues and limitations exist.

DescriptionTracking ID
Table 6. Obsolete Features

The following features are no longer available.

DescriptionTracking ID
The Content GUID output has been removed from all nodes in family policies. You must use the Entity Key output instead. Any existing family policies which include the use of Content GUID output from any nodes will now be upgraded to use the Entity Key output.US460179 and US424533