SR-A5565 · Issue 217722
Added missing filename encoding for drag and drop
Resolved in Pega Version 7.2
An error was being generated when opening an attached file with "$" in the filename. This was due to missing encoding for cases attached with drag and drop, and has been corrected.
SR-D33966 · Issue 504607
Corrected accessibility error after resize
Resolved in Pega Version 8.2.4
From within a Case and on a screen displaying the Information and Audit tabs in a Layout group, it was possible to use a series of sequences that included resizing the browser and opening Audit to cause the information tab to no longer be accessible. This has been resolved by setting the transform value to 0 after completing the resize.
SR-D29832 · Issue 503225
Corrected image alignment for email case creation
Resolved in Pega Version 8.2.4
An issue with missing image styling when an email was sent to create a case was traced to the Owasp library stripping align attributes from the img tag. This has been fixed.
SR-A4171 · Issue 213701
Added keyword support for <current>
Resolved in Pega Version 7.2
Variations between system versions were causing a decision table containing some regexp functions to pass or fail validation depending on the version. To remedy this, support has been added for using the regular expression function as a keyword to ensure valid tables are properly handled.
SR-A11956 · Issue 223935
Logic added to RUFs for Self-looping FlowAction
Resolved in Pega Version 7.2
In previous versions, it was possible to add a self-looping FlowAction on an AssignmentService shape. After upgrade, attempts to use this structure resulted in the error message ?Java generation failed; see log for details?. This was traced to handling for self-looping connectors logic not being included in the newly written pzGetDisplayableIncomingShapeIDs RUFs. This has been added.
SR-A1948 · Issue 210407
Enhancement added to Edit in Excel for large data instances
Resolved in Pega Version 7.2
Edit in Excel was failing with an error when editing data instances of a class having more than 245 columns mapped to its external mapping tab. In Excel 2003, The maximum number of columns is A to IV (i.e. 256 columns), so when the number of columns exceeds 256 (including "Import status", pzInskey, PxInsname), macros were designed to throw an error to be consistent with various versions of MS office. As Excel 2007 allows more than 256 columns, a new XLSX user template has been introduced to leverage that ability. A new node "pyGenericXLSXTemplateName" has been added to "ImportManager_Settings" for this purpose.
SR-133255 · Issue 204955
Resolved NPE caused by outbound email call after wait shape
Resolved in Pega Version 7.2
After a wait shape, a NullPointerException was thrown when a work item was moved to the problem flow after a call to send an outbound email. Changes have been made to the "ProcessIndividualDepAssignment" activity and "FlowProblems" flow to correct this issue.
SR-A8848 · Issue 219083
Correct class being passed in SubProccessTab flow
Resolved in Pega Version 7.2
n the pzSubProcessTab section. the value for the "RuleClassProperty" was not being passed as blank to the pzRuleCallParamsWrapper section when the flow was defined on the current page and was instead defaulting to Work Pool Class. The system has been modified to pass the proper class.
INC-168368 · Issue 651081
Correct flow actions loaded in multi-thread portal refresh
Resolved in Pega Version 8.7
The member authentication screen was displaying an incorrect flow action on doing browser refresh after creating a new interaction. Refresh is a special case where the parameter retention is different across single-threaded & multi-threaded portals alongside the execution order of activities. In this case, this inconsistency occurred in a multi-threaded portal when newAssignPage had the information to load the proper assignment but the parameter indicated an old index. This has been resolved by adding 'when' conditions to to populate and pass the correct references and labels and to honor the Param.TaskIndex set and sent by UI activities so it's retained in case of multi-thread portals.
SR-A13044 · Issue 226206
insHandle updated to resolve PrintWork OOM error
Resolved in Pega Version 7.2
When PrintWork activity was called with an empty insHandle, the activity tried to fetch all the attachments with pxInsHandle as null, causing an out of memory error. To avoid this, a check has been added to skip fetching attachments if the inshandle is blank.