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-B67688 · Issue 320076

Fixed use of FieldValue for templatization

Resolved in Pega Version 7.3.1

When templatization was turned on, a FieldValue containing property references that was set as a Label control value was not getting evaluated properly. This is due to the evaluated FieldValue is being set for pyLabelValue in the metadata of the label when the FieldValue actually needs to be evaluated at client side in templating. To resolve this, the property reference will be used directly instead of FieldValue.

SR-B67935 · Issue 319257

Updated decision shape iteration for StarCaseFlow

Resolved in Pega Version 7.3.1

When a decision shape in the pyStartCase flow contained only a boolean expression and the connector (true and false) of decision shape was attached to two assignment shapes, the flow worked on the desktop but did not work on mobile. This was due to 'ForDecisionShape' case being offline enabled while Library functions were not, and has been fixed by modifying the system to iterate and evaluate all the decision shapes in Create New Work .

SR-B67940 · Issue 316306

IAC authentication fixed for Mashup gadget headers

Resolved in Pega Version 7.3.1

The feature to pass headers to the Pega Web Mashup gadget Via JavaScript (i.e. browser) was not working because the Ajax request was sending a request for blank HTML and not establishing the appropriate cookie. To correct this, the Java script has been updated to better handle exceptions, and pzMashupProxyPage has been modified to replace the "blank.html" call with a new "pzMashupProcessHeaders" activity.

SR-B68379 · Issue 323426

Setting updated to determine whether Microsoft Internet Explorer 11 portal can steal desktop focus

Resolved in Pega Version 7.3.1

When Microsoft Internet Explorer 11 users multitasked and submitted something in a Customer Service portal then changed desktop windows to another non-Pega application, when the Customer Service task was completed the portal would steal desktop focus from the other application. This focus logic is by design, but Microsoft Internet Explorer 11 is more aggressive with overtaking application focus than other browsers. To counter this, focusNextElement in pzpega_ui_doc_focus .js has been updated to honor the pyIsWindowStealFocusInIEAllowed 'when' rule value.

SR-B68434 · Issue 325774

Null parameter handling added to InitializeContextPage data transform

Resolved in Pega Version 7.3.1

When the end user portal was launched and a few tabs were opened, logging into a new session with same user ID caused content in tabs to generate an error and not load. This failure was traced to null parameters being passed to the InitializeContextPage data transform of the display harness activity, and the code has been updated to handle empty data transform parameters.

SR-B68837 · Issue 318361

Bad 'when' fixed for ruleset translation

Resolved in Pega Version 7.3.1

Due to an error in a 'when' condition that caused incorrect overwriting, Spanish rulesets were being displayed for saving correspondence/paragraph rules irrespective of the language translations that had been imported. This has been fixed.

SR-B69149 · Issue 320820

Header level reading fixed for JAWS

Resolved in Pega Version 7.3.1

JAWS was not reading the header levels properly due to them being treated as heading level 2 even though there were headings at level 1. This has been fixed by adding the aria-level for the header div to the element with role=heading.

SR-B69403 · Issue 317542

Refined Modal Dialog RUF for standard format override

Resolved in Pega Version 7.3.1

The modal dialog format was applying multiple style formats if the "Standard" format was overridden. The pzSkinGenWFModalDialog RUF has been refined to prevent this.

SR-B69420 · Issue 320400

Repeating Dynamic Layout can use source for base in Microsoft Internet Explorer

Resolved in Pega Version 7.3.1

When using Microsoft Internet Explorer, repeating dynamic layouts were only taking Data- as the base and could not be configured to add a source. Dragging and dropping a section did not provide the source either. oSectionBody, which is a DOM element, is sent to redrawSectionFieldSetCaptionInfo as a parameter. In Microsoft Internet Explorer this element is removed from the DOM and hence has no parentElement. This is the reason that the call to redrawSectionFieldSetCaptionInfo was failing. To resolve this, a check has been added to see if the oSectionBody is in the DOM by using the check oSectionBody.parentElement at the start of redrawSectionFieldSetCaptionInfo.

SR-B70222 · Issue 322936

Property value submit event for screen flow works in Microsoft Internet Explorer

Resolved in Pega Version 7.3.1

FinishAssignment Action was configured as an Enter Key event for Dynamic layout in order to submit the flow in screenflow, but at runtime when using Microsoft Internet Explorer some of the property values were not submitting to the clipboard as expected. The issue was a defect in the UI framework related to submitting a form through any event when the input had focus in Microsoft Internet Explorer, and a check has been added to resolve the error.

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