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-194446 · Issue 691352

Mobile app validates collapsed layouts

Resolved in Pega Version 8.8

Validation did not fire in the offline app when the fields were in collapsed layouts. This has been resolved by removing the validateHiddenFieldsInOffline flag for Offline.

INC-194564 · Issue 700782

Cancel button shown as expected in modal dialog on Mobile

Resolved in Pega Version 8.8

A modal dialog in a mobile app used to show all the phone numbers of a customer did not display a Cancel (close) button after update even though the cancel button was defined on the underlying PhoneNumbers section. This has been resolved by adding a check to assess if the button is visible when calculating modal height.

INC-195683 · Issue 687954

Security update for MashUp

Resolved in Pega Version 8.8

Cross site scripting protections have been updated for the LoadMashupPage activity and RedirectTo parameter.

INC-196186 · Issue 725413

Check added for repeating dynamic layout submit context

Resolved in Pega Version 8.8

The postprocess of a local action was not executing when the local action was in a table that contained a repeating dynamic layout, and a null pointer exception was generated. Investigation determined that when a repeating dynamic layout was used inside a grid, the submit action on the layout was incorrectly happening in the context of the grid. To resolve this, a check has been added to determine whether the repeating dynamic layout is inside a grid so the correct context is used.

INC-199137 · Issue 708167

PD4ML upgraded

Resolved in Pega Version 8.8

Issues with PDF generation have been resolved by upgrading PD4ML to version 4.0.13.

INC-199469 · Issue 707514

PDF margins made available as parameters

Resolved in Pega Version 8.8

After update, margins were different in exported PDFs. This was due to upgraded jar files: PD4ML v3 used setPageInsets(new Insets(top, left, bottom, right)) , but the v4 jar uses setPageMargins(new PageMargins(left, top, right, bottom)) . Because the order of values (20, 10, 10, 10) were not changed this produced a different result. To resolve this, PD4ML margins are now available to be set as parameters: Param.pyMarginLeft, default value 20 Param.pyMarginTop, default value 10 Param.pyMarginRight, default value 10 Param.pyMarginBottom, default value 10 When standard activities like HTMLToPDF / pyViewAsPDF / pyAttachAsPDF are used, add a Property-Set step before calling the activity to add the necessary margin parameters. When CreatePDF smart shape is used, set the parameters via the connector of the CreatePDF.

INC-200340 · Issue 719090

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-200936 · Issue 703687

SFTP support added to ValidateURL rule

Resolved in Pega Version 8.8

SFTP has been added to the list of schemes which are accepted as part of the validation in the pxValidateURL rule.

INC-201929 · Issue 692849

Removed incorrect field validation errors

Resolved in Pega Version 8.8

When integer controls in a section were configured as required field, clicking on the field but not entering any value resulted in the prompt for the required field validation "Value cannot be blank", and any attempts to add a positive integer using number keypad after that resulted in the repeated validation error. This has been resolved by updating pzpega_control_textinput.

INC-202210 · Issue 740665

Resolved blind transfer error in Pega Call

Resolved in Pega Version 8.8

Attempting to do a blind transfer to another agent using Pega Call generated the run time exception message "Unable to perform ConvertStringToPage, due to invalid inputs." Investigation traced this to the event details not being passed to the UpdateCallFromEvent activity due to the Blind transfer event formatting received from Avaya. To resolve this, an 'if' condition has been added to inpzpega_ui_doc_ajaxengine_js in the PostData function.

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