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-A14359 · Issue 232227

Context-aware paths for SMA jmxclient.css and global.js files

Resolved in Pega Version 7.2.1

In some cases the jmxclient.css and global.js files were not found when running SMA due to the use of relative path names. The path names have now been made context-aware.

SR-A14361 · Issue 227993

Errant "Found spec for PegaRULES (V5.x) configuration" message removed

Resolved in Pega Version 7.2.1

After upgrade, starting JBoss using externalized prconfig.xml logged the error message "Found spec for PegaRULES (V5.x) configuration using System property: D:\jboss\server1\configuration\prconfig.xml". This non-operational message was caused by a out of date code fragment which has now been removed.

SR-A14386 · Issue 230949

Fixed issue with CSS incorrectly overriding skin rule

Resolved in Pega Version 7.2.1

The skin rule settings "Error Border" and "Error Background" were not having any effect on a text control which contained a validation error. This was an issue with the ErrorShade element being overridden my more specific CSS even though the HTML that used that CSS was never produced at run time. This has been corrected.

SR-A14386 · Issue 230504

Fixed issue with CSS incorrectly overriding skin rule

Resolved in Pega Version 7.2.1

The skin rule settings "Error Border" and "Error Background" were not having any effect on a text control which contained a validation error. This was an issue with the ErrorShade element being overridden by more specific CSS even though the HTML that used that CSS was never produced at run time. This has been corrected.

SR-A14403 · Issue 230497

Confirmation Message no longer appearing twice in confirm harness

Resolved in Pega Version 7.2.1

When the out-of-the-box pyWorkConfirmMessage section is included in an application and displayed in one of the steps while running the application, the pyWorkConfirmMessage section will display pyConfirmationNote property value of the work object present in pyWorkPage and will also display the pyConfirmationNote value defined at assignment level present in pxFlow page. This was traced to an additional call step in the function, and the handling has been modified to produce the expected results.

SR-A14412 · Issue 229299

Corrected SLA comparisons involving daylight savings

Resolved in Pega Version 7.2.1

A calendar using the "Sao_Paulo" timezone was eliminating the user-entered close dates when calculating SLA times between that calendar and one using "America/NewYork". This was an issue with the parse API not honoring Daylight Saving for some time zones, and handling for that has been added.

SR-A14464 · Issue 228529

Enhancements to SystemCleaner and SystemPulse

Resolved in Pega Version 7.2.1

Insufficient allocated space for passivation data in a shared filesystem can lead to passivated requestors not being properly cleaned up and possible OOM issues. In order to provide better support, SystemCleaner has been enhanced to better diagnose issues related to insufficient allocation, and any resulting information can be found in deleteExpiredDir in com.pega.pegarules.session.internal.mgmt.base.FilesystemStorage . In addition, when the system pulse is disabled via pxSystemNodeStatus set to Unknown, it would silently run in SMA and no log messages were generated. Since critical agents should provide a more visible indication that the processes are not running as expected, both System Pulse and SystemCleaner have been modified to stop the server startup and report when the server status is unknown.

SR-A14493 · Issue 227902

Clipboard viewing on SMA fixed

Resolved in Pega Version 7.2.1

Any user having Manager as the default portal was having difficulty viewing the clipboard pages. This was due to the XML being generated incorrectly for the clipboard of requestors with more than one thread open in them. This has been fixed.

SR-A14562 · Issue 231191

Enhanced logging to debug Composite Portal Menu rendering errors

Resolved in Pega Version 7.2.1

In order to better diagnose exceptions generated when trying to render a Section from Composite Portal Menu, more debug logs have been added when DatabaseImpl.open is called on any particular instance. The debug logs will print the authorization related information - the ruleset list, the current thread, current access group etc.

SR-A14584 · Issue 230941

Timing changed on rapid row deletion to resolve value shifts

Resolved in Pega Version 7.2.1

When editing a decision table, rapidly deleting rows and then clicking to the first row sometimes resulted in the first row's value being altered to the value of a different row. This was due to overlapping calls. To avoid this, the "DELETEROW-BUTTON" will be disabled after click until the deletion of the current row is complete.

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