Skip to main content


         This documentation site is for previous versions. Visit our new documentation site for current releases.      
 

This content has been archived and is no longer being updated.

Links may not function; however, this content may be relevant to outdated versions of the product.

Pega Autonomic Event Services hotfixes

Updated on September 10, 2021

Review the hotfixes that are required by the Pega Autonomic Event Services™ application, and request them from the Pega My Support Portal.

To request a hotfix:

  1. On My Support Portal, log in to your account.
  2. Click Create, and from the Request Type list, click Existing Hotfix Request.
  3. Complete the required fields.
  4. Click Submit.

Import hotfixes in the following order:

  • Apply Pega Platform™ hotfixes immediately after a Pega Platform installation or upgrade.
  • Apply Pega Autonomic Event Services hotfixes right after you complete the application bundle import.
  • Apply monitored systems hotfixes right after you configure a system for monitoring with Pega Autonomic Event Services.

For information about the hotfix installation, see the readme file that is included with the hotfix.

Pega Autonomic Event Services 8.3

Hotfix numberAvailable sinceObserved behaviorAdditional notes
HFix-59331Jan 7, 2020New tenants are unable to process REST service requests.

This hotfix is required for the correct functioning of Pega Autonomic Event Services.

HFix-65024Nov 25, 2020

The node count on the Enterprise tab is incorrect and increases after every refresh.

If a system name includes special characters, the Enterprise tab displays the unexpected character errors.  

This hotfix is required for the correct functioning of Pega Autonomic Event Services.

To install this hotfix, you need to click Dev Studio > Application > Distribution > Import.

HFix-68119Dec 29, 2020User is wrongly allowed to configure conditional “Notify when” AES Notification on edit.To install this hotfix, you need to click Dev Studio > Application > Distribution > Import.
HFix-69298Dec 29, 2020Adobe Flash Player is no longer supported as of December 2020 and Flash based charts can not be rendered.

This hotfix changes the render method for all existing Flash based charts to use Report Definition rules.

To install this hotfix, you need to click Dev Studio > Application > Distribution > Import.

Pega Autonomic Event Services 7.3

Hotfix numberAvailable sinceObserved behaviorAdditional notes
HFix-39121December 6, 2017The perfdatamode property in the cluster record is reset, although a monitored Pega Platform instance is configured to use push mode. 
HFix-39225December 6, 2017Managers cannot restrict system visibility by using the Manage Operator Systems flow. 
HFix-39044December 6, 2017

When a user views a rule instance cache, an error in an activity causes a misleading error message.

 
HFix-39086December 6, 2017

In Internet Explorer 11, Total Alerts by Node, Alerts by Category, and Exceptions by PCF reports might be incorrectly displayed.

 
HFix-39267December 6, 2017On the Agents tab and the Requestors tab, for a cluster with multiple nodes, Pega Autonomic Event Services displays data for one node only. 
HFix-44436July 3, 2018The AES 7.3 user interface is not rendered correctly when running on Pega Platform 7.4. 
HFix-46747September 27, 2018The nightly purge process deletes entries only from the PegaAES-Work-Exception and PegaAES-Work-Action class tables. As a result, unneeded entries in the PEGAAM_ACTION_INDEX table cause performance issues. 
HFix-46796October 4, 2018For a system with multiple active nodes, on the Enterprise landing page Summary tab, Pega Autonomic Event Services displays data for one node only. 
HFix-47290October 4, 2018For a system with multiple nodes, on the Enterprise landing page Requestorstab, Pega Autonomic Event Services displays duplicates of requestors. 
HFix-47600October 4, 2018Data about newly added nodes is not available, because the D_ReachableNodes data page is not refreshed. 
HFix-47601October 12, 2018In the Agents tab, the Enabled column displays information incorrectly. 
HFix-48448November 2, 2018The ExecuteGetActivityData activity always returns the same message, regardless of the result of the node reachability test. 
HFix-48132November 5, 2018In the Recent Alerts report, clicking an alert does not open the corresponding case. 
HFix-49975January 14, 2019

In the Action Item Reports section, the Exception Items - By Exception Class and Alerts - By Category reports run for all systems by default, because they do not use the current system as a filter condition.

This hotfix does not contain a readme file. Use the Import wizard to import the HFix-49975.zip file.
HFix-50178January 31, 2019Data that is displayed on the Dashboard is two days old.This hotfix does not contain a readme file. Use the Import wizard to import the HFix-50178.zip file.
You can use Pega Autonomic Event Services 7.3 to monitor PRPC 5.4, 5.5, 6.1, 6.2, and 6.3, and Pega Platform 7.1, 7.2, 7.3, 7.4, and 8.1.
  • Previous topic Managing Pega Autonomic Event Services operator records
  • Next topic Enhanced PegaAESRemote ruleset to support the latest Pega Autonomic Event Services features

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us