SR-133163 · Issue 203273
Refined property-set expansion to support complex activities
Resolved in Pega Version 7.2
Attempting to expand a property-set in an activity with many steps (20+) caused a failure and the activity locked up. Tin order to support complex activities, the activity call and clipboard functions in this call have been refined for efficiency.
SR-A5355 · Issue 215511
Resolved browser hang with large Map Values
Resolved in Pega Version 7.2
While opening very large Map Value ruleforms, some systems were hanging and thread dumps were seen in the logs. With Microsoft Internet Explorer , the error was "There was an error while loading the content given. Microsoft Internet Explorer Error Description: Not enough storage is available to complete this operation." This was an issue with the display grid not being able to show huge number of records in the map value grid. To resolve it, the map value grid will be hidden if it exceeds the given cell threshold.
SR-A8561 · Issue 217554
Resolved browser hang with large Map Values
Resolved in Pega Version 7.2
While opening very large Map Value ruleforms, some systems were hanging and thread dumps were seen in the logs. With Microsoft Internet Explorer, the error was "There was an error while loading the content given. Microsoft Internet Explorer Error Description: Not enough storage is available to complete this operation." This was an issue with the display grid not being able to show huge number of records in the map value grid. To resolve it, the map value grid will be hidden if it exceeds the given cell threshold.
SR-A10681 · Issue 221581
Resolved tracer issue for new operators
Resolved in Pega Version 7.2
A tracer issue was found where selected events for newly-created operators were clearing off. This has been fixed by refactoring the code handling adding new event types.
SR-A589 · Issue 218042
CRLF payload protection enhanced
Resolved in Pega Version 7.2
In some cases, CRLF characters in thread names were not being caught in thread name protection, causing a 303 response and allowing the CRLF characters to be executed in the response back to the browser. To ensure expected behavior, the Location header value will have CR, LF and . removed when PRPC is preparing the HTTP redirect (303) response.
SR-A10706 · Issue 220688
CRLF payload protection enhanced
Resolved in Pega Version 7.2
In some cases, CRLF characters in thread names were not being caught in thread name protection, causing a 303 response and allowing the CRLF characters to be executed in the response back to the browser. To ensure expected behavior, the Location header value will have CR, LF and . removed when PRPC is preparing the HTTP redirect (303) response.
SR-A12347 · Issue 212822
Added check for BIX extract that will exceed filesize name limit
Resolved in Pega Version 7.2
Running a BIX extract with the -i option failed with the error "Error while creating the csv file: The file name entered exceeds the maximum size allowed (255 characters)". This happened in environments where the codehit the OS limit on the filepath name. This can be avoided by ensuring the File Specification tab of the Extract Rule contains a directory path shorter than 255 characters and by taking care not to have another Extract Rule with the same name in a Branch or a higher ruleset version with file specification path longer than 255 characters. To assist this, a check has been added.
SR-A7275 · Issue 216805
Added non-ASCII character handling to MSOGenerateExcelFile activity
Resolved in Pega Version 7.2
When the name of the file to be downloaded contained Japanese characters, the resulting file name displayed spaces in place of the Japanese characters. This was due to the characters in the file name not being encoded using the same character set which would then be used by the browser to decode the file name. To resolve this, the name of the file to be downloaded is now set as part of the Content-Disposition response header and will support non-ASCII characters
SR-133693 · Issue 206383
Agent SystemCleaner default time changed
Resolved in Pega Version 7.2
Timezone conversion issues were causing sporadic issues with Agent SystemCleaner terminating prematurely in J2EE environments. By default, the agent will now run at 12:05am rather than precisely at midnight.
SR-A2960 · Issue 218751
Asynch loaded data pages correctly pulled into main thread
Resolved in Pega Version 7.2
After using Load-DataPage, using Connect-Wait to synchronize with child requestor caused the data page to be loaded again when it was referenced instead of the system bringing the asynchronously-loaded data page forward. This was caused by differing value handling during the cache key building for ADP load, and has been corrected.