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-A20147 · Issue 238046

Caching added to improve login speed

Resolved in Pega Version 7.2.1

In order to improve login performance, caching has been added for the following classes accessed from the database on every login: DATA-ADMIN-SECURITY-AUTHSERVICE DATA-BROADCAST DATA-ADMIN-SECURITY-KEYSTORE

SR-A20148 · Issue 239782

Repeat grid wrap column header center aligned upon resize

Resolved in Pega Version 7.2.1

The repeat grid wrap column header was not properly center aligned upon resize due to the text padding. This has been fixed.

SR-A20162 · Issue 238035

Added validation to check for Agents run every *blank* days

Resolved in Pega Version 7.2.1

When configuring a Rule-Agent-Queue instance, the Pattern can be specified as "Recurring", which opens an "Advanced" button. The modal window that opens for the Advanced button allows specifying the recurring pattern, and it's possible to specify that an agent executes Daily, Every X days. If the Every X days option was selected, it allowed leaving the number field blank. However, doing this generated an invalid delay time error after the agent ran. To avoid this, validation will be performed on this field to ensure that a value is entered. Additional changes were also made to not allow a blank value in the field, numberOfMonths, numberOfDays, and numberOfYears as well.

SR-A20183 · Issue 238612

Localization handling updated for High Level Overview documents generated in Word

Resolved in Pega Version 7.2.1

In a localized environment, High Level Overview documents generated in Word included some garbled characters if there were images or attachments in between the content of sections. The localization code has been updated to properly handle this format.

SR-A20219 · Issue 239018

Page-Set-Messages error properly displayed in harness

Resolved in Pega Version 7.2.1

Error messages were not displayed after setting the page- set messages in an activity and calling on post processing of the flow action. This was due to the improper clearing of messages during the ReloadSection, and the API has been updated to resolve this.

SR-A20287 · Issue 235728

Corrected refresh results for filtered propositions

Resolved in Pega Version 7.2.1

A refresh error related to filtering performed with the propositions using a certain business issue & group in PegaMarketing caused a list refresh that automatically brought back all the propositions after selecting one. This has been fixed.

SR-A20289 · Issue 245275

Custom header section of Calendar retained after Smartinfo popup displayed

Resolved in Pega Version 7.2.1

If the mouse moved over the custom header section of Weekly, Daily calendar and the SmartInfo popup appeared, the custom value was reset to the label value. To correct this, a custom header check for setting subject to subject time has been added to pzAllDayEventBlock to maintain the custom setting.

SR-A20300 · Issue 239490

SLAs agree in assignment gadget and action area

Resolved in Pega Version 7.2.1

An assignment created with an SLA of 2 years was showing different SLA info in assignment gadget and action area. On the assignment list gadget, the deadline displayed was "1 year 12 months from now" which is correct. On the top right corner of the action area it says, "Due in 1 year 11 months from now". This has been fixed by modifying the base calculations of the pyAssignmentTimeLimitDeadline control.

SR-A20336 · Issue 240862

Corrected SLA name set with passed value

Resolved in Pega Version 7.2.1

The SLA name was not correctly set on the assignment page during creation if the field was left empty for a passed value to fill. This has been corrected.

SR-A20346 · Issue 242973

Cell height/width rounded in "," decimal locales

Resolved in Pega Version 7.2.1

Localization for areas that use "," as the decimal separator led to errors indicating the height/width of a merged cell of Free Form layout was a non-integer value. To avoid this, the design time JS will round the measurement for cellWidth and cellHeight.

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