Fourth Quarter of 2020
Release Date: November 20, 2020
This topic provides a list of product changes released for this module on this date.
| Description | Tracking ID |
|---|---|
| Previously, when using an aggregate function in a query running in Oracle, the data types were not returned correctly, this resulted in validation errors in the calculate and comparison nodes. This issue has been resolved. | DE144642 |
Release Date: October 16, 2020
This topic provides a list of product changes released for this module on this date.
| Description | Tracking ID |
|---|---|
| Previously, if the baseline rule called by a Baseline Rule node in a Family Policy modified the current entity, infinite recursion occurred even if the logic designed to prevent recursion was included in the baseline rule. This issue has been resolved. | DE144245 |
Release Date: October 2, 2020
This topic provides a list of product changes released for this module on this date.
| Description | Tracking ID |
|---|---|
| You can now choose to save either the details of the execution or only summary in the Execution History Records. To facilitate this enhancement, the Execution History Log Setting section has been added with the Normal, Errors Only, and Summary Only options in the Details workspace of the Family Policy page. | US351322 |
| Description | Tracking ID |
|---|---|
| Previously, output of a Math node configured to operate on a mathematical expression containing logical operators did not always conform to generally accepted math principles. This issue has been resolved. For example, a Math node configured with the mathematical expression A|B&C will now be evaluated as A|(B&C), whereas it was previously evaluated as (A|B)&C. Note: This may cause unexpected results in existing policies. | US412813 |
| Previously, if you configured a policy with nodes as successors to an email node, the successor nodes were not executed. This issue has been resolved. | DE142388 |
| Previously, if a family policy was configured to allow recursion, recursive executions continued until IIS crashed on the APM server. This issue has been resolved. Note: The number of recursions are limited now. | DE141238 |
| Previously, if execution of a Sub Policy node was in progress, execution of the policy did not time out even if it exceeded the time limit configured for the Policy Execution Service. This issue has been resolved. | DE139233 |
| Previously, if the execution of an action node resulted in an error, a null reference error appeared in the execution results of any successor action node. This issue has been resolved. | DE139232 |
| Previously, if you configured a policy with a Baseline Rule node for a family that did not have a defined GE Digital APM baseline rule, an error occurred during execution of the policy. This issue has been resolved. | DE138904 |
| Previously, if a family policy was configured to send an email, the URLs included automatically in the email text were incorrect. This issue has been resolved. | DE137689 |
| Previously, the timeout feature of a Math node was disabled. This issue has been resolved. Now, if the time taken by a Math node to perform a calculation exceeds the configured time limit, execution of the policy that contains the node is cancelled. | DE133382 |
| Previously, in the Execution History pane, regardless of the page size you selected, only the first 50 rows of each page of execution results were displayed. This issue has been resolved. | DE124582 |