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-C91264 · Issue 433440

Localization fixed for dropdown sourced with pystate

Resolved in Pega Version 8.1.5

When pystate was used to source a dropdown, the options were all uppercase but in the review harness used lower case for IN and OR. This difference caused a failure in localization. This was caused by the Field value instance being defined in lowercase in PyCaption while the UI was treating the active value as an instance of pyCaption, leading to instances of both "in" and "IN" being present. This has been resolved by consolidating the field value to use a single case in the pega-eventprocessing ruleset.

SR-C91898 · Issue 435424

Resolved Rich Text Editor display in popup windows

Resolved in Pega Version 8.1.5

The Rich text editor was not displaying in popup windows although it did display otherwise. Investigation traced this to the harness context APIs used in "pega.contro.IRTE.init" (pzpega_control_richtexteditor.js rule) returning rteTextArea as null, leading to the RTE scripts failing to bind the ckeditor dom. This has been fixed by replacing the harness context APIs with ones better suited to this use.

SR-C91930 · Issue 439847

Corrected focus issue after form submit for SPA portal

Resolved in Pega Version 8.1.5

When a form was submitted in the SPA portal and the next form appeared after launching the case, if the second form's height was more than the screen size the vertical scroll bar was automatically moving to the bottom and the focus was given to the submit button. This has been corrected to the expected behavior of the focus staying on the first editable field.

SR-C92000 · Issue 437303

Updated date time format used pyPostEmailContent section to resolve exception

Resolved in Pega Version 8.1.5

When a pyPostEmailContent section in the Pega-Social ruleset was being referenced, the error messages "pub.util.PRDateFormat) ERROR - Cannot create format "MMM dd, yyyy hh:mm A", default format is used; java.lang.IllegalArgumentException: Illegal pattern character 'A'" was logged.This has been resolved by modifying the date time format used for the pyPostEmailContent section.

SR-C92171 · Issue 446290

Updated unique ID hashing to account for extended class names

Resolved in Pega Version 8.1.5

Multiple history classes were pointing to one database table because the historical hash method only used the the first 32 characters of a class name to create a unique identifier. This created duplicates if the class extended past this limit. To correct this, the unique ID hashing has updated in SQLGenerator to account for long identifier names: if the supplied name is greater than 32 chars, the system will hash the entire name to create a unique identifier.

SR-C92863 · Issue 436152

Catch added to handle invalid locale exceptions related to localized rulesets

Resolved in Pega Version 8.1.5

If an InvalidLocaleException was encountered while parsing through the localized rulesets in the runtime ruleset list, the system was setting the step status to fail. Localized rulesets are identified as having an underscore followed by a 2 character locale code(s). Some rulesets have an underscore in them causing them to get validated, which ends up failing as the locale is invalid. To resolve this, a catch has been added that will back out the failed step status and recover gracefully if the exception is encountered.

SR-C92901 · Issue 436503

Check added to maintain date entry error state rather than default to current date

Resolved in Pega Version 8.1.5

When both Calendar and Text Input was enabled, typing special characters or an invalid date into the Date Time control generated an error on submit while the system silently overwrote the incorrect value with the current date. On refresh/save, no further error was thrown and the current date was submitted without warning. To resolve this, a check has been added that will not reformat if the date has error attribute.

SR-C93726 · Issue 435287

Work status icons work correctly when using localization

Resolved in Pega Version 8.1.5

The pyWorkAssignmentStatus control was not displaying the status flags/icons for localized work status values due to a match failure caused by the system using the localized text for the pyAssignmentStatus to perform a string comparison against the hard-coded English values. To correct this, the control pyWorkAssignmentStatus has been modified to run the comparisons with the new string "assignmentStatus" instead of with the localized text.

SR-C93802 · Issue 436138

Rounding added to avoid exception for ADM number too small to save to Oracle

Resolved in Pega Version 8.1.5

An exception was thrown when trying to save ADMSnapshot agent predictor bin data that was too small (below 1 x 10-130) for the Oracle Number column it was written into. This blocked up-to-date reporting on adaptive models. To resolve this issue, the code has been modified to round the double type numbers to an acceptable scale before writing to the database.

SR-C94042 · Issue 432440

Resolved JSON exception with refreshrow used for navigation

Resolved in Pega Version 8.1.5

After upgrade, a custom implementation of a grid that had a menu configured on right click of the row for the category/description in the uploaded case attachments was not working. This was traced to the RefreshRow(non-list) action generating quotes that made the JSON invalid for a navigation rule, and has been fixed by modifying pzProcessRefreshRowItem to remove quotes from navigation refreshrow action generation.

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