First Quarter of 2023
Release Date: March 31, 2023
This topic provides a list of product changes released for this module on this date.
| Description | Tracking ID |
|---|---|
| To facilitate the upgrade process, when your APM system is upgraded, a log message is added indicating the APM product version at which the upgrade took place. In addition, when you delete upgrade logs, a similar action is performed. | US576960 |
| To optimize performance, the execution history details (that is, node-level execution results) will no longer be retained indefinitely. Now, execution history details will be retained for the period configured in the Policy Designer application settings. However, if an indefinite retention period is specified, the execution history details will be retained for six months from the date of the policy execution. Note: There is no change to the retention policy for the execution summary. | US575810 |
| To enhance the upgrade process, when your APM system is upgraded, any policies containing a create entity node or an edit entity node are upgraded, such that references to Policy GUID field on a Policy Instance family are changed to Policy Key. Similarly, any references to Policy Instance GUID field on a Policy Event family are changed to Policy Instance Key. If a value is assigned to one of these fields and has the field ID of CONTENT_GUID, those are also upgraded to ENTY_KEY. | US572648 |
| Description | Tracking ID |
|---|---|
| Previously, if you accessed the upgrade log of a policy directly (that is, using a URL), an error occurred. This issue has been resolved. | DE197833 |
| Previously, in the upgrade log of a sub policy, some messages referenced the Delete Entity node when the affected node was a Create Relationship or a Delete Relationship node. This issue has been resolved. For more information, refer to KBA 000068295. | DE197203 |
| Previously, when an active, scheduled policy was saved, it got triggered immediately and the defined schedule resumed from the next expected date and time. This issue has been resolved. Now, the policy is triggered only when the policy schedule or status is modified. | DE197194 |
| Previously, when a session timed out, the policy was not executed. This issue has been resolved. Now, when a session times out, the policy execution is retried. | DE194998 |
| Previously, when you executed a policy that called a sub policy that contained a Create Entity node, if the entity was not created due to an error on another node, the execution details in the Create Entity node were incorrect. This issue has been resolved. | DE196496 |
| Previously, in a policy using a Predix Time Series input node, if you copied the input values from an instance to the ad hoc validation pane and then validated the policy, an error occurred in the validation result for the Predix Time Series node. This issue has been resolved. |
DE181639 |
| Previously, you were able to create a Policy with a name with leading spaces. This issue has been resolved. Now, any leading spaces will be removed from the name when you save the Policy. As a result of this change, if your system contains Policies whose names differ only by leading spaces, you must enter new names. | DE75965 |