Skip to main content

Resolved Issues

View the resolved issues for a specific Platform release.

Go to download resolved issues by patch release.

Browse release notes for a selected Pega Version.

NOTE: Enter just the Case ID number (SR or INC) in order to find the associated Support Request.

Please update your bookmarks. This site will be discontinued in Dec 2024.

Pega Platform Resolved Issues for 8.1 and newer are now available on the Support Center.

SR-C3006 · Issue 344948

Fixed Advanced Agent runtime determinations

Resolved in Pega Version 7.4

While implementing the use case of running an Agent 24 hours apart in only one node in the cluster, using the improved Advanced agent control https://pdn.pega.com/improved-control-running-advanced-agents/improved-control-running-advanced-agents was not working as expected. Intermittently, the agent would not run in any of the nodes in a day, but the very next day it would run on two nodes in the cluster. This was caused by a calculation error in determining the difference between the last run start time and next run start time, and has been fixed.

SR-C3261 · Issue 348477

PRNode enhancement

Resolved in Pega Version 7.4

Changes have been made in PRNode to expose the getSystemName API.

SR-C3261 · Issue 348473

PRNode enhancement

Resolved in Pega Version 7.4

Changes have been made in PRNode to expose the getSystemName API.

SR-C3261 · Issue 348401

Tracer API performance improvements

Resolved in Pega Version 7.4

Performance improvements have been made to Tracer API.

SR-C3261 · Issue 348619

SynchClipboardPage API performance improvements

Resolved in Pega Version 7.4

Performance improvements have been made to the SynchClipboardPage API.

SR-C3261 · Issue 349048

StringUtils.isInteger performance improvements

Resolved in Pega Version 7.4

Performance improvements have been made in StringUtils.isInteger.

SR-C3300 · Issue 347485

Fixed circumstanced section render fail

Resolved in Pega Version 7.4

A circumstanced section was failing during FUA and could not be rendered. This was traced to the FUA encountering duplicate variable declaration in the generated java, and has been fixed by adding scope parentheses to avoid the same variable declaration in the same scope.

SR-C4390 · Issue 351249

Clipboard page fixed for evaluating Rule-Access-When condition

Resolved in Pega Version 7.4

After logging into the application and accessing the work objects from the worklist, a sporadic error would appear when evaluating Rule-Access-When conditions even though the required page being evaluated against has the data populated. Evaluation showed the execution of the Rule-Access-When condition was failing because the incoming primary page was null, and this was traced to an incorrect clipboard page name in AccessEvaluatior.java. This has been fixed.

SR-C445 · Issue 338352

cluster rule watch lock expires on crash

Resolved in Pega Version 7.4

If the cluster rule watch was in progress and the browser / system crashed, the rule watch became locked until the system (cluster) was restarted. In this case, the disconnect command from Req1 has an encrypted requestor ID because it is an unauthenticated requestor, leading to all String-matches failing. A hook to delete all entries in the distributed rule watch map for a given requestor during its clean up has now been added to resolve this.

SR-C4531 · Issue 347039

JSON key sort performance improvements

Resolved in Pega Version 7.4

Sorting the keys in the JSON output was causing a synchronization bottleneck. The acquisition of the Collator object was synchronized in JDK code when it did not need to be, and the call to Collator.getInstance() has now been replaced with a call to Collator.getInstance(Locale.getDefault()) in order to improve performance.

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