Pega Autonomic Event Services hotfixes
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:
- On My Support Portal, log in to your account.
- Click , and from the Request Type list, click Existing Hotfix Request.
- Complete the required fields.
- Click .
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 number | Available since | Observed behavior | Additional notes |
|---|---|---|---|
| HFix-59331 | Jan 7, 2020 | New tenants are unable to process REST service requests. | This hotfix is required for the correct functioning of Pega Autonomic Event Services. |
| HFix-65024 | Nov 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 . |
| HFix-68119 | Dec 29, 2020 | User is wrongly allowed to configure conditional “Notify when” AES Notification on edit. | To install this hotfix, you need to click . |
| HFix-69298 | Dec 29, 2020 | Adobe 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 . |
Pega Autonomic Event Services 7.3
| Hotfix number | Available since | Observed behavior | Additional notes |
|---|---|---|---|
| HFix-39121 | December 6, 2017 | The perfdatamode property in the cluster record is reset, although a monitored Pega Platform instance is configured to use push mode. | |
| HFix-39225 | December 6, 2017 | Managers cannot restrict system visibility by using the Manage Operator Systems flow. | |
| HFix-39044 | December 6, 2017 | When a user views a rule instance cache, an error in an activity causes a misleading error message. | |
| HFix-39086 | December 6, 2017 | In Internet Explorer 11, Total Alerts by Node, Alerts by Category, and Exceptions by PCF reports might be incorrectly displayed. | |
| HFix-39267 | December 6, 2017 | On the Agents tab and the tab, for a cluster with multiple nodes, Pega Autonomic Event Services displays data for one node only. | |
| HFix-44436 | July 3, 2018 | The AES 7.3 user interface is not rendered correctly when running on Pega Platform 7.4. | |
| HFix-46747 | September 27, 2018 | The 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-46796 | October 4, 2018 | For a system with multiple active nodes, on the landing page Summary tab, Pega Autonomic Event Services displays data for one node only. | |
| HFix-47290 | October 4, 2018 | For a system with multiple nodes, on the Enterprise landing page Requestorstab, Pega Autonomic Event Services displays duplicates of requestors. | |
| HFix-47600 | October 4, 2018 | Data about newly added nodes is not available, because the D_ReachableNodes data page is not refreshed. | |
| HFix-47601 | October 12, 2018 | In the Agents tab, the Enabled column displays information incorrectly. | |
| HFix-48448 | November 2, 2018 | The ExecuteGetActivityData activity always returns the same message, regardless of the result of the node reachability test. | |
| HFix-48132 | November 5, 2018 | In the Recent Alerts report, clicking an alert does not open the corresponding case. | |
| HFix-49975 | January 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-50178 | January 31, 2019 | Data that is displayed on the is two days old. | This hotfix does not contain a readme file. Use the Import wizard to import the HFix-50178.zip file. |
Previous topic Managing Pega Autonomic Event Services operator records Next topic Enhanced PegaAESRemote ruleset to support the latest Pega Autonomic Event Services features