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-120586 · Issue 178686

Assignment dependencies with child cases now properly resolve

Resolved in Pega Version 7.1.8

Using a dependency on an assignment based on a child case can case an error. This was due to the obj class being wrongly populated, and has been resolved.

SR-120592 · Issue 183002

Corrected circumstanced list views called from within a section

Resolved in Pega Version 7.1.8

A circumstanced List view based on a property was not being properly called from within a section. Instead of passing the primary page which has the circumstance property details for the ruleset work flow, a new page was always created. Since the new page did not have the circumstance property details, the circumstanced list view was skipped. To correct this, the Rule-Obj-ListView.DisplayView rule has been modified to always pass the primary page instead of creating a new one.

SR-120596 · Issue 183801

Resolved mapping issue for SOAP-connect with multirefs

Resolved in Pega Version 7.1.8

After upgrade, mapping the soap-connect response to page in activity was not working as expected. This was an issue with a Parse-XML rule, and has been corrected with added support for multirefs and SOAP arrays with multirefs.

SR-120603 · Issue 178264

RTE tooltips localization expanded

Resolved in Pega Version 7.1.8

The localization for RTE tooltips has been expanded to include the spin/roll button (to select font size).

SR-120615 · Issue 183300

SQL rules searches now display full details

Resolved in Pega Version 7.1.8

Expanding the connect SQL rules in a search result did not display "ruleset version," "updated by" or "availability" details. This was caused by a mismatch in the RuleName formatting for the Search Results and Transform activities, and has been corrected.

SR-120615 · Issue 178695

SQL rules searches now display full details

Resolved in Pega Version 7.1.8

Expanding the connect SQL rules in a search result did not display "ruleset version," "updated by" or "availability" details. This was caused by a mismatch in the RuleName formatting for the Search Results and Transform activities, and has been corrected.

SR-120622 · Issue 186851

Resolved browser hang issue with IAC

Resolved in Pega Version 7.1.8

After opening a case displayed through IAC, attempting to close the browser caused it to hang and the CPU cycles to elevate. This was traced to an undeclared variable causing recursion, and has been resolved by using a var keyword to declare a variable in JavaScript.

SR-120654 · Issue 179938

Made busy indicator location consistent in SFA portal

Resolved in Pega Version 7.1.8

The 'loading' icon (aka "Throbber") was not being displayed in a consistent location in the SFA Portal. This was traced to the busy indicator being registered in reference to the workarea gadget, causing the busy indicator to appear in an unexpected place if the gadget was hidden. This has been corrected by showing the indicator directly on the portal window.

SR-120673 · Issue 185098

Refresh behavior updated for sections with list views

Resolved in Pega Version 7.1.8

After configuring a refresh section on a control with a list view in the section, the refresh was happening only on the first iteration. This was an issue with loading "pega_tools_evaldomscripts.js" multiple time and the HTML has been updated to ensure the "ListViewHeader" rule uses the tag instead of tag.

SR-120701 · Issue 179702

Email listener error handling improved

Resolved in Pega Version 7.1.8

When an email arrived with a zero byte attachment, the email listener was failing to generate a work object. An error was seen in the log, and the listener marked the email as seen even though no WO was created. This has been fixed by suppressing the IOException that arises while processing a zero-size INLINE attachment, allowing the rest of the email message to be processed. An exception will be logged, but the attachment that caused the issue will not be added to the work object.

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