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-221722 · Issue 739201

Menu button no longer steals focus on dismissal

Resolved in Pega Version 8.8

Action menus in the portal harness were stealing focus from input fields in the work harnesses. This was an unintended side effect of work done to correct an issue where focus was not correctly remaining in the table layout, and has been resolved by updating the control menu to avoid the explicit focus in the hideNode function when the menu is already dismissed.

INC-221955 · Issue 719288

Archival association supported without data retention policy

Resolved in Pega Version 8.8

Previously, configuring an archival association when the data retention policy had not been created resulted in an error and the associations were not saved. Handling for this use has now been added in order to support the archival of custom-associated data.

INC-221956 · Issue 721686

Archived cases with custom data viewable in ThemeCosmos

Resolved in Pega Version 8.8

Support has been added to ThemeCosmos to allow reviewing archived cases with custom data association.

INC-222553 · Issue 724226

Repaired Perform for 'Assignments with Errors'

Resolved in Pega Version 8.8

The 'Perform' button was not working on the "Assignments with errors" pop-up. This was an inadvertent side effect of changes made in 'pega_desktop_support' (Pega-Desktop ruleset), and has been resolved by adding a check before calling pega.mobile.isMultiWebViewPegaMobileClient.

INC-222769 · Issue 720982

Report filter popup displays correctly for UI kit applications

Resolved in Pega Version 8.8

Previous work done on the popover js to correct the filter popup placement and vertical and horizontal scrollbars for report columns has been further updated to handle the use case of UI kit applications.

INC-222784 · Issue 739536

BAC handling added for calling StartNewFlow activity from UI

Resolved in Pega Version 8.8

After modifying the pycaseactionarea submit button to call a flow that uploads a PDF to a third party system using the order action 1) Finish Assignment; 2) Call an activity and inside the activity call startflow to initiate the integration; and 3) Launch local action, clicking the button to finish the assignment showed only the first local action instead of the expected behavior of having a modal appear to the user to confirm that their file was successfully uploaded. An access control error also appeared. This was traced to the registration details being removed after generating the pdf with an activity running on a different thread, and has been resolved by adding a flag tools.putParamValue("skipResetQueryStringRegistration",true); in pzCreatePDFHarnessWrapper to avoid wiping the registration details and skip resetting the query string registration during the process.

INC-222800 · Issue 725125

Currency Code updates

Resolved in Pega Version 8.8

A Section configured with an editable currency input using auto-formatting failed to render at runtime if configured using Type -> Number, Symbol -> Currency, Other currency, and Currency -> "USD". The error "Invalid Locale : USD" was logged. This was an unintended side effect of work done to configure currency codes for the Number control, and has been resolved by accounting for the locale settings and handling the condition for the error "Invalid local-USD" so that the the UI rendering appears as expected. In addition, when the Currency control was configured with editable mode "Editable" and "Display value using read-only formatting" checked, read-only formatting generation did not happen for the control. Entering a value and tabbing out caused the ReloadCell activity to return empty content, which resulted in the server returning full HTML markup with a message "Operation Successful". Because the ReloadCell activity handler expected only control markup with formatted value to be returned, the HTML markup containing inline CSS styles in it appeared in the Currency input field on tab out. There was a workaround of unchecking "Display value using read-only formatting" on the control's presentation tab, but this has been resolved by using Post value infrastructure to get the formatted value from the server.

INC-222922 · Issue 722995

Validations fire on collapsed accordion layouts

Resolved in Pega Version 8.8

Client validation was not firing on the selected tab of a layout group if the accordion layout was collapsed. If focus was switched to the second tab, the client validation on the first collapsed tab did not work. This has been resolved by modifying the 'else if' condition to pass the validation for the fields places in layout group tabs.

INC-223222 · Issue 723635

Corrected apiContext when using bulkActions

Resolved in Pega Version 8.8

Row selections in the multi-selection table were intermittently not working after opening a table with bulk actions enabled. Investigation showed that opening a table with bulkActions enabled and then navigating to a table where bulk actions are not available but multi-select is enabled led to functions like setSelectedRows and getSelectedRows still being available in apiContext. This has been resolved by correcting apiContext when bulkActions is enabled.

INC-223504 · Issue 723197

Harness handling updated for Tertiary Ajax Container

Resolved in Pega Version 8.8

After configuring a Create Stage with a single step and a second stage with a screen flow configured with Multistep form, creating a case caused the Step under the Create stage to come up on the Tertiary Ajax Container as expected, but on click of create the second stage also started to run the same Tertiary Ajax Container. This has been resolved by updating the harness handling so the Tertiary Ajax container will close and the second stage will open on the main action area within the Cosmos Portal.

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