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-115985 · Issue 169316

System updated to handle partially encrypted URLs

Resolved in Pega Version 7.1.7

With URL encryption enabled, certain work types could not be loaded due to an inability to process the partially encrypted URLs. The JavaScript has been updated to correctly handle these URLs.

SR-116025 · Issue 174180

Corrected ability to add rows to a Row Repeat Grid Layout

Resolved in Pega Version 7.1.7

Previously, an error was generated when attempting to add more than 51 rows to a Row Repeat Grid Layout with two more layouts containing other fields. This was caused by a duplicate call to invoke the list section, and has been fixed.

SR-116041 · Issue 165468

Update Manager performs version checking before installation

Resolved in Pega Version 7.1.7

An enhancement has been added to Update Manager to prevent installation of a HFIX meant for a different release of PRPC.

SR-116439 · Issue 166256

Update Manager performs version checking before installation

Resolved in Pega Version 7.1.7

An enhancement has been added to Update Manager to prevent installation of a HFIX meant for a different release of PRPC.

SR-116042 · Issue 170124

Updated newline character for HTML

Resolved in Pega Version 7.1.7

On click-submit, some text paragraphs were being displayed without breaks between them. This was caused by a missing HTML tag and has been corrected.

SR-116101 · Issue 166813

Improved handling of multipart data input

Resolved in Pega Version 7.1.7

HTTP Service uses a Parse XML to map message data, but issues were found with the handling of the "multipart/form-data" format. For example, not all of the parameters were made available in the Parameter page: while the multipart data was parsed, causing the name value pair to not be properly set. To better handle multipart data, changes have been made to the Fileupload method of the HttpUtilities java file.

SR-114595 · Issue 164792

Improved handling of multipart data input

Resolved in Pega Version 7.1.7

HTTP Service uses a Parse XML to map message data, but issues were found with the handling of the "multipart/form-data" format. For example, not all of the parameters were made available in the Parameter page: while the multipart data was parsed, causing the name value pair to not be properly set. To better handle multipart data, changes have been made to the Fileupload method of the HttpUtilities java file.

SR-116130 · Issue 168010

StackOverflow errors during passivation remedied

Resolved in Pega Version 7.1.7

An issue was found with StackOverflow errors thrown by the passivation daemon, requiring a restart of the JVM. This was found to be related to the AutoPopulate API, and has been updated.

SR-116146 · Issue 169058

CreateUniqueID enhanced to allow custom instances

Resolved in Pega Version 7.1.7

The out-of-the-box PopulateReport activity previously used shorthand notation when referencing the CreateUniqueID function instead of referencing the function using the RuleSet or library name. This caused an issue with systems that contained a custom version of CreateUniqueID in the CMSUtilities library, resulting in "Multiple suitable instances found" errors. In order to accommodate custom instances of CreateUniqueID, long hand notation will be used for matching in place of shorthand.

SR-116153 · Issue 165729

CaseTypeValues correctly created for child cases

Resolved in Pega Version 7.1.7

CaseTypeValues were not being properly set on the child case when it was added to the cover through agent creation, causing the trigger not to execute because the change was not detected. Manual creation was detected properly. This inconsistency was traced to the agent using the AddToCover activity vs. the manual creation using AddChildWork, and has been corrected.

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