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.

SR-A18404 · Issue 235467

New parameter to disable logging of Tidy PDF processing warnings

Resolved in Pega Version 7.2.1

When purge/archive was enabled, the system logs were filling with Tidy warning errors during PDF conversion. To resolve this, the new parameter 'pyShowWarning' has been added to the HTMLTOPDF Activity: set it to 'false' to avoid Tidy processing warnings in logs.

SR-A18464 · Issue 234927

"Grand Total" localized

Resolved in Pega Version 7.2.1

Localization has been added for the pyFieldCaption property "Grand Total" .

SR-A18466 · Issue 235142

Updated getDate function to use UTC

Resolved in Pega Version 7.2.1

Setting the system to the Brazil time zone ("UTC-03:00 Brasilia") with the operator set to Brazil/Acre caused a duplicate day to appear in October of every calendar year when the Microsoft Internet Explorer browser was used. This was traced to a difference in how the getDate function performed on the browser, and that function has now been updated to use getUTCDate() instead of getDate() to ensure cross-browser consistency.

SR-A18493 · Issue 235336

Cross-browser checks added for disabled checkboxes

Resolved in Pega Version 7.2.1

The Checkbox Caption was not properly not disabled on Microsoft Internet Explorer when the checkbox was disabled due to a missing definition for the parent element. Extra condition have been added to find the disabled value of radiobutton and checkboxes regardless of browser.

SR-A18624 · Issue 239177

Fixed post-upgrade data table conversion to local storage

Resolved in Pega Version 7.2.1

After upgrade, updating a data table into a local storage source generated the error "Cannot change keys for a class with (725) instance(s) ". This occurred when the local variable ?classKeysChanged? is true, which happened during comparison of the Key fields of the step page (classPage) and the primary page (ClassForm) because the order of the keys had changed even though the number of keys were same. The "AddProperties" activity has now been modified to check if there are keys already set in the class and if there are any, then skip resaving the class and exit the activity.

SR-A18694 · Issue 246976

Method changed for locating Word Templates folder

Resolved in Pega Version 7.2.1

The method used to obtain the Word templates folder always lower cases the folder path, but this poses a problem for the Turkish locale when the path contains capital I with no dot. Turkish has two variants of I - one with dot and one without dot. To resolve this, the Office templates folder path will be determined based on a combination of certain registry keys dependent on the Word version.

SR-A18701 · Issue 235846

Repositioned BusyIndicator to cover Target element

Resolved in Pega Version 7.2.1

If the section with busy indicator was taller than the viewport height, the busy indicator mask did not cover the lower part of the section when scrolling and the section was editable. This has been fixed by repositioning the mask to cover the part of the section editable in the viewport and also show immediately on scroll.

SR-A18702 · Issue 236022

ImageSection / pzImageSectionWrapper localized

Resolved in Pega Version 7.2.1

Localization has been added to ImageSection / pzImageSectionWrapper.

SR-A18787 · Issue 240329

Busy icon shows properly when clicking Save/Refresh

Resolved in Pega Version 7.2.1

The Busy indicator has been updated to ensure it appears as expected after clicking the Save/Refresh button of any harness.

SR-A18813 · Issue 236196

Support added for auto-generated numeric IDENTITY columns in RD

Resolved in Pega Version 7.2.1

Because IDENTITY auto-generated columns were not supported , RD did not identity the column of type numeric() IDENTITY and generated an error when accessing a table with NUMERIC column types in SQL Server 2012. Numeric() TYPE was already supported for generation in RD, and an SQL connector has been added to handle tables with numeric() IDENTITY as well.

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