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.
SR-116157 · Issue 165994
Improved crash recovery in a complex system
Resolved in Pega Version 7.1.7
During crash recovery in a clustered, load balanced system, attempting to recover a user's progress displayed a message that the session was recovered but the page did not then properly load the recovered data. To ensure proper crash recovery failover on complex systems, the user is now authenticated on the STANDARD thread instead of a work thread when restoring work in progress.
SR-116209 · Issue 166698
Backslash '\' now showing as expected in autocomplete and search
Resolved in Pega Version 7.1.7
The AutoComplete control was filtering out backslash '\' characters when displaying the values in the list of matches, causing failures with search and autocomplete. The Rule-Utility-Function for the getProperty has been corrected to allow '\' to be handled properly.