Second Quarter of 2020
Release Date: June 19, 2020
This topic provides a list of product changes released for this module on this date.
| Description | Tracking ID |
|---|---|
| Previously, if an error occurred during the execution of a sub-policy that is called by another sub-policy, the View Execution Details link did not appear in the Node Execution Details window of the sub-policy. This issue has been resolved. | DE134906 |
Release Date: May 8, 2020
This topic provides a list of product changes released for this module on this date.
| Description | Tracking ID |
|---|---|
To improve performance, the Policy Designer Overview page is no longer updated automatically when you return to the previously opened tab. You can now select Refresh ( ) to update the page. | US396407 |
|
Configuration settings for the Policy Trigger and Policy Execution Services have been modified:
Note: For more information, refer to the Policy Designer deployment documentation.
|
|
| |
| You can now view the end time for policy executions in the Execution History pane of the Design workspace. | US383244 |
|
You can now access the query specified in a Query node directly from the node. To facilitate this enhancement, the Open in New Window button ( | US374240 |
| You can now configure different policy execution history retention duration settings for executions which result in Errors, Warnings (Action Taken), Warnings (No Action Taken), Success (Action Taken), or Success (No Action Taken). When the Predix Essentials database is upgraded, if an overall policy execution history retention duration setting was previously configured, this setting will be applied for all execution results. | US330806 |
| To improve the performance of the Query node, the result set of the node is now restricted to the first 10,000 rows of the query result. | DE117522 |
) has been added to the | Description | Tracking ID |
|---|---|
| In APM V4.3.1.x, when you modified a policy containing multiple Create Event and/or Close Event nodes configured to use the same Event name, the policy model was corrupted, and the policy did not execute as expected. This issue has been resolved. Note: Policies that were corrupted continue to execute incorrectly. For assistance to correct affected policies, contact GE Digital Support. | DE131111 |
| Previously, when you mapped the output from a Last, Max, or Min node operating on the result set from a Query Alert node into a successor node and saved the policy, and then reloaded the policy, the mapping to the successor node was lost. This issue has been resolved. | DE129953 |
|
Previously, on the Policy Designer Overview page, the Overdue Recommendations list did not display the correct State Assignee user. This issue has been resolved. Note: To facilitate this change, the query used by the Overdue Policy Recommendations list has been updated. If you have previously customized this query, copy the new query from the baseline folder to the public folder and apply the customizations again.
| DE128404 |
| Previously, on the Policy Designer Overview page, the tiles did not display any results, and the My Policy Recommendations list did not display any results for users other than super users. This issue has been resolved. | DE126120 |
| Previously, in the Math node, an error occurred when you modified an equation containing an indexed variable name conflicting with an input variable name. This issue has been resolved. | DE125923 |
| Previously, if you added a new family, or added a field to an existing family, then used the family or field in an Entity node, an error indicating that the node was inactive occurred during execution of the policy. This issue has been resolved. | DE122975 |
| Previously, if you assigned multiple users to a policy, the number of instances associated with the policy appeared incorrectly in the Policies section of the Policy Designer Overview page. This issue has been resolved. | DE119853 |
| Previously, if the execution or validation of an Email node in a sub policy resulted in an error, no execution details were displayed for the node, and the policy execution history did not indicate that an error had occurred. This issue has been resolved. | DE117263 |
| Previously, if you added a field to a family, and then added the same field to a query that is represented by a Query node, the execution of the Query node failed. This issue has been resolved. | DE115326 |