| 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 |