Fourth Quarter of 2023
Release Date: December 13, 2023
This topic provides a list of product changes released for this module on this date.
| Description | Tracking ID |
|---|---|
To improve usability, the following enhancements have been made in the Reference Document generated through Email Contact node with attachment:
| US593664 |
| To improve usability, the policy execution history background clean up job has been improved. To facilitate this enhancement, additional options have been added to control the job start time, end time, and selection of time zone. | US541496 |
| Description | Tracking ID |
|---|---|
|
Previously, instances upgraded from V4 Policy with Time Series node input failed to send email node when entity key was null. This issue has been fixed | DE209593 |
| Previously, when you selected the Revert to Baseline button, the cache for the family policies was not cleared. Instead, the cache was cleared when you manually made any changes to the policy and saved the policy. This issue has been resolved. | DE207963 |
| Previously, is Null node converted the input string value to an unreadable date format. This issue has been resolved. | DE207778 |
| Previously, when JSON Parser node configured with more than one Name and JSON path value then in return value node will have only one value available. This issue has been resolved. | DE207345 |
| Previously, State Transition node execution log messages and execution history was showing Family Id instead of Entity Key. This issue has been resolved. | DE207344 |
| Previously, with State Transition Mode option, when a Record was already in the target state, Policy execution was showing success for state transition. This issue has been resolved. | DE206836 |
Release Date: October 6, 2023
This topic provides a list of product changes released for this module on this date.
| Description | Tracking ID |
|---|---|
| The Predix Time Series node has been renamed to Time Series node. | US596038 |
| To enhance usability, when you view policy execution results in the design canvas, the node ID is now displayed in the node execution details window. | US595444 |
| To enhance usability, the policy model can now be started from a Query node. Hence, the Query node is now consistent with the other Input nodes. | US495730 |
| To enhance usability, the Convert Type node can now be configured to convert a column of values in a collection (for example, a query result), to a different data type. | US476079 |
| To enhance usability, a new node named Query Entity has been introduced, which enables you to retrieve all fields of a record by providing the entity key and family ID of the record. This removes the requirement to create a catalog query to retrieve a record that is not specified in the Policy Instance. | US255674 |
| Description | Tracking ID |
|---|---|
| Previously, when you deleted a policy with a large number of instances, many of the Policy Instance References Cleanup scheduled tasks remained In Progress until you canceled them. In some cases, the policy execution was interrupted. This issue has been resolved. | DE206613 |
| Previously, when you attempted to create or edit a recommendation linked to an EAM system notification using a policy, an error occurred. This issue has been resolved | DE204690 |
| Previously, if you were assigned to the Policy Viewer security group, you were unable to view Policy Events. This issue has been resolved. | DE204293 |
| Previously, if you scheduled a policy with a large number of instances, not all instances were executed every time. This issue has been resolved. | DE203646 |
| Previously, when you closed the Policy Admin page, even if you did not make any changes to the settings, a message appeared, stating that your changes would be unsaved. This issue has been resolved. | DE197820 |