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.

INC-150555 · Issue 620543

isDCSPA flag added to ensure correct harness after reload

Resolved in Pega Version 8.5.3

When moving from a Process Flow to a Screenflow configured with tabbedscreenflow7, the first reload caused a switch to a Perform Harness that resulted in the error "Unable to open an instance using the given inputs", and footer buttons disappeared until multiple refreshes were done. This was an issue specific to the environment configuration at the site, but to avoid future issues a code update has been made that will add the isDCSPA flag if the value is not present in the parameter page.

INC-150731 · Issue 612883

Stages list wraps in App Studio preview

Resolved in Pega Version 8.5.3

While previewing an application in App Studio, the Approval stage section which included a header containing a chevron with each of the eight stage names across the top was displayed with the center pane expanded to accommodate the header and part of the right pane content pushed off the right edge of the window. A horizontal scroll bar was also added even though the stage names were truncated and displayed with ellipses ("..."). Investigation showed that the styles targeting stages were using flex nowrap as part of custom styles generated in pyenduser, and the styles have now been updated for stages for desktop to wrap if the number of stages would otherwise extend the screen.

INC-150778 · Issue 612311

Treatment UI screen correctly refreshes on save

Resolved in Pega Version 8.5.3

In the Web Treatment screen, saving was not working as expected and the edit button was not visible. Investigation showed that whenever Web Treatment was saved after an edit, the grid was not getting refreshed and the previous treatment rule was opened instead of the new one. This was caused by the declarepage params handling in DecisionDataRecords which treated the value as a separate argument not specific to any section and resulted in empty parameters. This has been resolved by adding an additional check for the declare page in addition to the declare page parameters while processing each section of a multiple section refresh.

INC-150872 · Issue 613080

JAWS reads the tab name and the close icon details seperately

Resolved in Pega Version 8.5.3

By default, all currently opened Work Objects Close icons have the label "Close Tab", but when moving across tabs while using the JAWS screen reader, reaching a work object tab caused JAWS to read the entire tab header as "S-123 close tab". In order to improve accessibility, aria-labels will be added while setting label to the tab so the header and close icon will be read separately.

INC-151050 · Issue 610679

Added check for empty string to custom Timeline Date Range

Resolved in Pega Version 8.5.3

When using the Timeline control and selecting Date Range as a custom value, the loading icon (busy indicator) showed continuously on the screen and no other operations were possible. Selecting any Date Range other than the custom field value worked as expected. Investigation showed that the Timeline control was not working when the Date Range value was empty, which in this case was traced to a value being entered at design time and then cleared. In timeline options, the Date Range end option was checking for the value being undefined and did not consider the empty string (""); this has been resolved by adding a condition to check if the Date Range option end is an empty string.

INC-151401 · Issue 615717

Context set for progressive scroll load of dynamic layout

Resolved in Pega Version 8.5.3

When setting pagination as 'Progressively load on scroll' for a repeating dynamic layout in a section with page list as the source, scrolling resulted in a null pointer exception and no further scrolling was possible. The issue was not seen when 'Progressively scroll on user action' was used. Investigation showed the activity Reload Section was failing because of the failure in the pre-processing activity, and this has been resolved by setting the correct context before making the pagination call.

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.

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