| 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 configured a Case node or Is Null node to pass a time stamp value to an Add Value to Health Indicator node, the validation and execution of the Add Value to Health Indicator node failed, and an error message appeared in the Execution Details window indicating that the date is not in Coordinated Universal Time (UTC). This issue has been resolved. | DE98447 |
| 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, if you executed a policy that contained an Edit Entity node from another APM module, an incorrect value was updated in the record mapped to the node. This issue occurred if your user account was configured with Metric Unit of Measure (UOM) preferences, and the base UOM configured for the field updated by the policy was not a Metric unit. This issue has been resolved. | DE98240 |
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 APM 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 APM 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 APM Catalog. For more information on configuring the alternative query, contact Global Support Services. | DE95004 |
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. |
|
| 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, when you attempted to access an imported policy that contained a Create Entity node for a family that did not exist in the APM database, the policy did not load. This issue has been resolved. Now, the policy loads regardless of the family is specified for the Create Entity node. | DE92631 |
| 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 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, 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, 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, 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 |
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 |
