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.

INC-151418 · Issue 610230

Authentication updated for legacy activities

Resolved in Pega Version 8.5.3

Authentication updates have been made for several legacy activities invoked via URL by custom HTML.

INC-151858 · Issue 610352

Updated currency decimal precision

Resolved in Pega Version 8.5.3

Hungarian and Taiwanese currencies were previously hardcoded to use zero decimal precision. In order to be compliant with the current ISO-4217 standards, these currencies have been updated to be precise to two decimal places.

INC-151952 · Issue 609340

Expand Pane icon responds to enter key when using JAWS

Resolved in Pega Version 8.5.3

In an Operator ID rule in Dev Studio, pressing the Enter key when focused on an Access Group expand icon caused the focus on the page to move to the top of the Contact Information frame (top left corner of the Frame). The only way to use the enter key to expand the pane without the refocus was to tab to the arrow icon and then tab a second time before pressing enter. This was traced to the expand caret icon being focussed twice due to the tabIndex for both the TD and SPAN elements holding the caret icon: TD had a focus element for accessibility of the grid, and SPAN had it for the expand pane accessibility. This has been resolved by adding a check condition before adding tabIndex to the first cell in the Grid.

INC-152084 · Issue 620952

Handling added for cross-origin DOM exceptions

Resolved in Pega Version 8.5.3

When an openURLWindow action was used to open any other domain, DOM exceptions were generated related to cross-origin iFrames communication and the UI became unresponsive. This has been resolved.

INC-152171 · Issue 610975

Unused query parameter cleaned up from harness

Resolved in Pega Version 8.5.3

Recent testing showed a legacy 'encodedPassword=true' query parameter lingering after changes were made to convert harness actions. Although there was no security implication as no sensitive information was being sent, this unused query has been removed.

INC-152227 · Issue 613671

Corrected filter icon on hierarchical table

Resolved in Pega Version 8.5.3

After creating a section with a hierarchical table, filter icons in the header of the table were displayed in the form of a box and as a normal filter icon. This has been resolved.

INC-152283 · Issue 626400

Added handling for switching table context in a section

Resolved in Pega Version 8.5.3

After configuring multiple tables in a section with row-editing on master-detail, opening the detail section of one of the tables and clicking inside it and then trying to open the details of another table generated the error "Can not render section'. The section would render correctly if the browser was refreshed. Investigation showed this was due to the new section opening in the wrong context, and the system has been updated to support this use case.

INC-152340 · Issue 610911

Scrollbar consistent on switching between grids in tabs

Resolved in Pega Version 8.5.3

On switching between two grid tabs configured in a layout group of tabs, the scrollbars intermittently disappeared or doubled. This was traced to the initscrollbars function being called multiple times and adding hScrolldiv and vScrolldiv each time. To resolve this, the logic has been updated to recalculate the position style.

INC-152547 · Issue 619031

Check added for SPA portal

Resolved in Pega Version 8.5.3

When using the FlowAction "ToCancel" to proceed to the "Withdrawn" stage, the "Confirm" Harness was not opening in a custom Portal. This was traced to a missing NO_UI configuration for FlowAction, which for SPA portal meant its single page caused doc.submit to repaint the whole window/portal. This has been resolved by adding a check for the SPA case.

INC-152945 · Issue 613933

Skin rule applied correctly post-upgrade

Resolved in Pega Version 8.5.3

After upgrading from v7 to v8.5, attempting to apply the previous skin to the new application resulted in a java exception while saving. This was caused by null or empty values for the horizontalDividerHeight and verticalDividerHeight variable which were parsed as double values and led to a null pointer exception. To resolve this, null and empty checks have been added to GenerateFlexScreenLayout.java.

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