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-115749 · Issue 167027

Support added for custom filtering and refresh inside a Repeat Grid

Resolved in Pega Version 7.1.7

If a dropdown control was placed in the column header of a repeating grid to work as a filter and perform a section refresh for the list (based on a column present in the list, but not displayed in the grid), checking the option to freeze the column headers (and use a fixed height/width) caused the dropdown to no longer work and no refresh action could be triggered. This was caused by a second hidden dropdown in the grid with the fixed header configuration that overwrote the selected value in the ASYNC request that is sent when the dropdown value changes. To remedy this, changes were made in the HTML generation to make the hidden header input disabled. This works only when configured as "auto": the control generation logic overwrites all readonly conditions to true if the dropdown is configured as "Editable".

SR-115839 · Issue 166347

Corrected radio button visibility behaviors

Resolved in Pega Version 7.1.7

Previously, some erroneous behaviors were seen with the visibility of a mandatory radio button when used in conjunction with a conditional read-only option. This has been resolved by a recent change that makes the "Required" checkbox a dropdown, fixing the design time issues.

SR-115896 · Issue 167002

Corrected flow handling for failed tickets

Resolved in Pega Version 7.1.7

Raised flow tickets using pre-existing flow-ticketed utility shapes were intermittently failing to transfer to the expected place in the flow. This was found to be an improper copy action in the task, and has been corrected. The error message has also been clarified.

SR-115896 · Issue 167322

Corrected flow handling for failed tickets

Resolved in Pega Version 7.1.7

Raised flow tickets using pre-existing flow-ticketed utility shapes were intermittently failing to transfer to the expected place in the flow. This was found to be an improper copy action in the task, and has been corrected. The error message has also been clarified.

SR-115931 · Issue 169804

Fixed read-only cascading dynamic select in Google Chrome

Resolved in Pega Version 7.1.7

The cascading dynamic select was not working in Google Chrome with ReadOnly Mode. This was traced to an error in the dynamicselect.js, and has been corrected.

SR-115985 · Issue 169316

System updated to handle partially encrypted URLs

Resolved in Pega Version 7.1.7

With URL encryption enabled, certain work types could not be loaded due to an inability to process the partially encrypted URLs. The JavaScript has been updated to correctly handle these URLs.

SR-116025 · Issue 174180

Corrected ability to add rows to a Row Repeat Grid Layout

Resolved in Pega Version 7.1.7

Previously, an error was generated when attempting to add more than 51 rows to a Row Repeat Grid Layout with two more layouts containing other fields. This was caused by a duplicate call to invoke the list section, and has been fixed.

SR-116042 · Issue 170124

Updated newline character for HTML

Resolved in Pega Version 7.1.7

On click-submit, some text paragraphs were being displayed without breaks between them. This was caused by a missing HTML tag and has been corrected.

SR-116209 · Issue 166698

Backslash '\' now showing as expected in autocomplete and search

Resolved in Pega Version 7.1.7

The AutoComplete control was filtering out backslash '\' characters when displaying the values in the list of matches, causing failures with search and autocomplete. The Rule-Utility-Function for the getProperty has been corrected to allow '\' to be handled properly.

SR-116272 · Issue 168880

Java error resolved for Smartinfo in list view

Resolved in Pega Version 7.1.7

A JavaScript error was being generated in IE8 after viewing the Smartinfo popup with a list view. This was caused by calling the focus API on top of an invisible element, and has been fixed.

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