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 note: beginning with the Pega Platform 8.7.4 Patch, the Resolved Issues have moved to the Support Center.

SR-A101069 · Issue 270616

Fixed dropdown issues when using Google Chrome

Resolved in Pega Version 7.2.2

The following issues were noted when using the Google Chrome browser: when selecting values from drop down in collapsible header, the section did not refresh according to selection; when the drop down was expanded, it loaded in front of collapsible header; when trying to select values which were within a collapsible header, the header became collapsed. These issues were due to the function expandHeader not being called in Google Chrome, and the function will now be called accordingly.

SR-A101069 · Issue 269981

Fixed dropdown issues when using Google Chrome

Resolved in Pega Version 7.2.2

The following issues were noted when using the Google Chrome browser: when selecting values from drop down in collapsible header, the section did not refresh according to selection; when the drop down was expanded, it loaded in front of collapsible header; when trying to select values which were within a collapsible header, the header became collapsed. These issues were due to the function expandHeader not being called in Google Chrome, and the function will now be called accordingly.

SR-A101069 · Issue 270595

Fixed dropdown issues when using Google Chrome

Resolved in Pega Version 7.2.2

The following issues were noted when using the Google Chrome browser: when selecting values from drop down in collapsible header, the section did not refresh according to selection; when the drop down was expanded, it loaded in front of collapsible header; when trying to select values which were within a collapsible header, the header became collapsed. These issues were due to the function expandHeader not being called in Google Chrome, and the function will now be called accordingly.

SR-A92057 · Issue 259453

OneTimeUse cache file generation disabled for SAML2

Resolved in Pega Version 7.2.2

Whenever SAML2 Token contained a "OneTimeUse" caching condition there were thousands of unwanted files generated. This caching has been disabled in the assertion validation code of SAMLv2ResponseProtocolValidator.java, so even if SAML2 token contains that OneTimeUse condition these files will not be generated.

SR-A76677 · Issue 253493

IDP SAML 2.0 schema validation error resolved

Resolved in Pega Version 7.2.2

When generating the Pega SP metadata after importing the Shibboleth IDP metadata, the error "The metadata does not pass the SAML 2.0 schema validation" appeared. This has been resolved by modifying the pzDownloadSPMetadata activity to generate a unique secure random ID prefixed with an underscore.

SR-A77173 · Issue 254080

IsWindowStealFocusInIEAllowed allows 'when' value

Resolved in Pega Version 7.2.2

In order to run legacy and Pega applications in parallel, a site configured the system to create a case in the Pega application as soon as a case was created in the legacy application. The intent was to have the case created in Pega to be in the background, but performing any DC actions shifted focus to the Pega app window when using Microsoft Internet Explorer . In order to have the configuration work as desired, the pyIsWindowStealFocusInMicrosoft Internet Explorer Allowed when rule must be set to false (default is true). Support for a conditional window focus configuration is now available, based on pyIsWindowStealFocusInMicrosoft Internet Explorer Allowed 'when' rule value.

SR-A100816 · Issue 268476

MinimumAgeForProcessing honored when requeuing Broken-Process

Resolved in Pega Version 7.2.2

When using the Requeue feature from SMA, queue items were not honoring the existing (previously used) value of pyMinimumAgeForProcessing, instead setting the value as -1 so, all attempts were happening immediately. This was an issue with the Repair API in QueueManagerImpl not honoring minimumAgeForProcessing if MinimumDateForProcessing already existed in the queue item, and has been fixed.

SR-A100367 · Issue 270660

Page copy works when previewing a rule

Resolved in Pega Version 7.2.2

The option to copy an existing page was not working when previewing a rule. This was caused by the page type and page name parameters not being included in the pyTempWorkPage used to create the request URL for the preview; this has been corrected.

SR-A76381 · Issue 252860

Customizable when added for PegaPULSE delete button

Resolved in Pega Version 7.2.2

In order to support more customization, an enhancement has been added to hide the delete link on PegaPULSE entries based on conditional circumstances (i.e. entry is older than x hours). The overridable when rule 'pyCanDeletePost' has been provided and is referenced in the pzISCurrentUser when rule with AND condition to the existing condition.

SR-A76381 · Issue 252811

Customizable when added for PegaPULSE delete button

Resolved in Pega Version 7.2.2

In order to support more customization, an enhancement has been added to hide the delete link on PegaPULSE entries based on conditional circumstances (i.e. entry is older than x hours). The overridable when rule 'pyCanDeletePost' has been provided and is referenced in the pzISCurrentUser when rule with AND condition to the existing condition.

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