Fourth Quarter of 2018

Policy Designer

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

Release Date: December 14, 2018

Table 1. Resolved Issues
DescriptionTracking ID
Previously, when you executed a policy that contained a Create Relationship node and a Create Entity node configured to create multiple records, the subsequent relationships were not created after the creation of the relationship between the first combination of records. This issue occurred if you specified one of the following inputs for the Create Relationship node:
  • Duplicate predecessor entity keys and the output of the Create Entity node as the successor entity key.
  • The collection output of a Create Entity node as the predecessor or successor entity key.
This issue has been resolved.
  • DE94996
  • DE94795
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, 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 APM user account instead of the policy time zone. This issue has been resolved.DE91644
Previously, if you executed a policy containing a Create Alert node, the following issues occurred even though the policy was successfully executed:
  • The execution result did not appear in the Execution Details window for the Create Alert node.
  • The execution summary of the policy indicated that the policy was successfully executed but did not trigger any actions.
These issues have been resolved.		DE90675

Release Date: November 16, 2018

Table 2. Resolved Issues
NoteTracking ID
Previously, if a policy was executed by a family-level rule or another APM 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, 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

Release Date: November 16, 2018

Table 3. Enhancements and New Features
NoteTracking ID(s)
The Asset UUID field in the Properties window for the Create Alert and Query Alerts nodes has been renamed Asset Unique ID.
  • DE90491
  • DE90280
Table 4. Resolved Issues
DescriptionTracking ID
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 you mapped the output of a Health Indicator node to a Comparison node, and then mapped the logical result of the Comparison node to an And or Or node, validation and execution of the policy failed. This issue has been resolved.DE90937
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, in the Properties window for the Create Alert node, if you mapped the value in the Unique ID box of an Equipment or a Functional Location record to the Asset UUID box, and then executed the policy, the Create Alert node did not create any alerts. This issue has been resolved.DE90491
Previously, in the Properties window for the Query Alerts node, if you mapped the value in the Unique ID box of an Equipment or a Functional Location record to the Asset UUID box, and then executed the policy, the Query Alerts node did not retrieve any alerts. This issue has been resolved.DE90280
Previously, in the Properties window for the Create Relationship node, if you specified duplicate predecessor or successor entity keys to create multiple one-to-one relationships, and then validated or executed the policy, a validation error occurred for the node. This issue has been resolved.DE89330

Release Date: October 12, 2018

Table 5. Resolved Issues
DescriptionTracking ID
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, if you mapped the output of a Health Indicator node to a Comparison node, and then mapped the logical result of the Comparison node to an And or Or node, validation and execution of the policy failed. This issue has been resolved.DE90785