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-B73034 · Issue 320819

Rule design view rendering fixed for Microsoft Internet Explorer 11/Edge4.0

Resolved in Pega Version 7.3.1

Rule design view was not rendering in Microsoft Internet Explorer 11 11.0.44 and Edge 40.x due to CSS and scrollbar coding in Edge 4.0 that was not W3 standards compliant. This has been fixed by updating the Pega CSS to match the syntax used in this scenario.

SR-B73035 · Issue 320810

Rule design view rendering fixed for Microsoft Internet Explorer 11/Edge4.0

Resolved in Pega Version 7.3.1

Rule design view was not rendering in Microsoft Internet Explorer 11 11.0.44 and Edge 40.x due to CSS and scrollbar coding in Edge 4.0 that was not W3 standards compliant. This has been fixed by updating the Pega CSS to match the syntax used in this scenario.

SR-B73036 · Issue 320808

Rule design view rendering fixed for Microsoft Internet Explorer 11/Edge4.0

Resolved in Pega Version 7.3.1

Rule design view was not rendering in Microsoft Internet Explorer 11 11.0.44 and Edge 40.x due to CSS and scrollbar coding in Edge 4.0 that was not W3 standards compliant. This has been fixed by updating the Pega CSS to match the syntax used in this scenario.

SR-B73038 · Issue 320818

Rule design view rendering fixed for Microsoft Internet Explorer 11/Edge4.0

Resolved in Pega Version 7.3.1

Rule design view was not rendering in Microsoft Internet Explorer 11 11.0.44 and Edge 40.x due to CSS and scrollbar coding in Edge 4.0 that was not W3 standards compliant. This has been fixed by updating the Pega CSS to match the syntax used in this scenario.

SR-B73039 · Issue 320817

Rule design view rendering fixed for Microsoft Internet Explorer 11/Edge4.0

Resolved in Pega Version 7.3.1

Rule design view was not rendering in Microsoft Internet Explorer 11 11.0.44 and Edge 40.x due to CSS and scrollbar coding in Edge 4.0 that was not W3 standards compliant. This has been fixed by updating the Pega CSS to match the syntax used in this scenario.

SR-B73040 · Issue 320814

Rule design view rendering fixed for Microsoft Internet Explorer 11/Edge4.0

Resolved in Pega Version 7.3.1

Rule design view was not rendering in Microsoft Internet Explorer 11 11.0.44 and Edge 40.x due to CSS and scrollbar coding in Edge 4.0 that was not W3 standards compliant. This has been fixed by updating the Pega CSS to match the syntax used in this scenario.

SR-B73042 · Issue 320815

Rule design view rendering fixed for Microsoft Internet Explorer 11/Edge4.0

Resolved in Pega Version 7.3.1

Rule design view was not rendering in Microsoft Internet Explorer 11 11.0.44 and Edge 40.x due to CSS and scrollbar coding in Edge 4.0 that was not W3 standards compliant. This has been fixed by updating the Pega CSS to match the syntax used in this scenario.

SR-B55054 · Issue 317660

Fixed Safari refocus on section refresh

Resolved in Pega Version 7.3.1

Safari was setting the focus to document.body after a section refresh inside a details portion, causing qualifying questions to disappear. The issue was found to be that the section displaying the questions was running under a separate thread. As long as the refresh happened within that context, the behavior was as expected. However, immediately clicking on an answer for the question without first clicking elsewhere within the window caused it to run under the claims context and not render properly due to the focus shift. To correct this, modifications have been added to avoid resetting the execution thread conditionally for Safari when the blur is triggered on document.body.

SR-B44781 · Issue 315253

Case search refinements added

Resolved in Pega Version 7.3.1

Searches for S-cases included irrelevant I-cases in the results. This was traced to opening an S-case from workbasket and then creating a new interaction: in the newly created I-case pyWorkpage.pxFlow.pxFlowParameter, prevRecordKey was getting set to S-case and thus those I-cases were displayed in the content search. In order to return only the expected results, the doUIAction activity has been modified to remove "prevContentID", "prevRecordkey" and 'prevFormDirty" from the parameter page used by the clipboard.

SR-B44444 · Issue 311506

Resolved sporadic UnmodifiablePropertyException errors

Resolved in Pega Version 7.3.1

Sporadic UnmodifiablePropertyException errors were appearing in the logs when a DataPage was called through a defer load activity on a section. This has been resolved by adding a check in pzRuleCallParamsPreProcessing.

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