First Quarter of 2023

Release Date: March 31, 2023

This topic provides a list of product changes released for this module on this date.

Table 1. Enhancements and New Features

The following enhancements and new features have been added.

DescriptionTracking 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
To enhance traceability of Family Policy actions, when the Cancel Transaction node is executed, a policy execution history record is now created.US525851
Table 2. Resolved Issues

The following issues, which existed in one or more previous versions, have been resolved.

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