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.

SR-A19599 · Issue 237365

Made getLocalizedValue function call fully qualified

Resolved in Pega Version 7.2.1

In environments where there are multiple versions of the function getLocalizedValue (which is true for any environment where the FSIF and KYC frameworks have been installed), pzFetchCaseStatusUpdate fails due to an unqualified function call. This has been corrected by providing the full context including library while calling functions in the property-set method in the mentioned activity.

SR-A19761 · Issue 237142

Fixed Require flag usage for Validate rule

Resolved in Pega Version 7.2.1

Saving a Validate rule that had a Required flag on one or more properties automatically reset the value, resulting in the inability to set the Required flag on any property of the rule. This was an error in the temporary activity handling, and has been fixed.

SR-A19810 · Issue 239496

PopulateRecipient set to consider pyEmail1

Resolved in Pega Version 7.2.1

After upgrade, an error was occurring while trying to save the Data-Corr-Email.populateRecipient activity into an application ruleset due to code changes used to specify the email property field. The "populateRecipients" activity has fallback logic to handle using pyEmailAddress [old method] for pyAddresses(Email) [new method], but some sites had the data in ".pyEmail1". PopulateRecipients has now been updated to look for pyAddresses(Email)").(".pyEmailAddress") and then consider values from ".pyEmail1".

SR-A19932 · Issue 243259

Corrected cancel function in Calendar options

Resolved in Pega Version 7.2.1

If the pxCalendarViewGadget was launched in a modal dialogue, clicking the cancel button in the Calendar options menu caused the assignment to be submitted. This was caused by a form submit and harness refresh being incorrectly called together by the cancel, and has been changed so the click of cancel in calendar options will refresh the pzCalendarOptionsDefinition section but disable the form submit, resulting in the previous values being retained.

SR-A20087 · Issue 238967

Removed date truncation to allow alternate calendar formats

Resolved in Pega Version 7.2.1

When locale was set to Japan, the date in the calendar for the weekly option was incorrectly truncated. This truncation was based on an assumption that the date could be captured in the first four digits of dd/mm/yy, and failed to consider the alternate format for locales that use yy/mm/dd. The truncation logic has been removed to fix the issue.

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-A21096 · Issue 241281

Clarified dynamic text handling to better support localization

Resolved in Pega Version 7.2.1

The use of properties and multiple field values to show dynamic text caused an issue where separate field values (3 fvs) were created for each part of a sentence and the context was not being correctly kept during localization. To resolve this, the system now uses a single field value with parameters.

SR-A21096 · Issue 239803

Clarified dynamic text handling to better support localization

Resolved in Pega Version 7.2.1

The use of properties and multiple field values to show dynamic text caused an issue where separate field values (3 fvs) were created for each part of a sentence and the context was not being correctly kept during localization. To resolve this, the system now uses a single field value with parameters.

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