INC-202943 · Issue 700195
WorkLink URL generation updated for security
Resolved in Pega Version 8.5.6
When using a WorkLink in an email, clicking the link and entering credentials on the login screen resulted in a 403 unauthorized error. This was due to a WorkLink URL generation issue caused by the non-encryption of the RedirectAndRun activity call in the URL, and has been resolved.
INC-204676 · Issue 699111
Localization added to subject line for SendEmailToAssigneeOnGoalTime
Resolved in Pega Version 8.5.6
When a Callback case was created and the assignee notified by email, the subject line was not localized. This has been corrected.
INC-207218 · Issue 706370
Check added to prevent duplicate approval by single agent
Resolved in Pega Version 8.5.6
When using a cascading Approvals process supported both by a web access button or by responding via email, a single agent could use both methods and advance a case an additional step as if they were the next approval level. This was due to the system only checking the pzInsKey when processing the approval while the assignment key will be the same for the cascading approvals assignments. This has been resolved by introducing a datetime check to validate if the email approval assignment creation datetime and the one in the database have same value; if yes the approval process will proceed and if not it will exit.
INC-163628 · Issue 660555
Corrected view generation logic for nested subsections
Resolved in Pega Version 8.5.6
Performing a save-as of the pyCaseMainInner work- section in the UIKit resulted in an infinite loop in the view generation logic. This was traced to the system recursively generating views from subsections, and has been resolved by updating the logic so a view is only generated for valid py prefixed sections on save of a section.
INC-164620 · Issue 640658
jQuery variable handling updated for mashup
Resolved in Pega Version 8.5.6
After upgrade, embedded mashup was not working. The browser console log showed the error "Uncaught TypeError: $ is not a function at pega.web.manager._initGadgets (PegaReg?pyActivity=pzIncludeMashupScripts:69)". The $ function belongs to the jQuery library, and investigation traced this to a difference in variable handling. This has been corrected by updating the referring jQuery to use the variable 'jQuery' instead of '$'.
INC-164775 · Issue 681238
Web page generation security updated
Resolved in Pega Version 8.5.6
Cross-site scripting protections have been enhanced around web page generation.
INC-165992 · Issue 657690
Table Filter save uses correct harness
Resolved in Pega Version 8.5.6
After creating a new view for table and then relaunching the portal or switching between tabs, the created views were not visible. Investigation showed that the views were saved under the incorrect pycaseworker harness on initial load, causing them to not be visible when returning from the switch and using the correct pyCWPortalContent harness. This has been resolved with the addition of the new parameter innerHarnessName to get the harness name when creating a personalization instance.
INC-167704 · Issue 671628
Email timing updated to ensure content captured
Resolved in Pega Version 8.5.6
Outbound email replies constructed using a pyReply section were intermittently blank if the 'Send' button was clicked immediately after adding text. This was traced to the blur not happening immediately on click of the submit button, and has been resolved by introducing window.blurDelay to ensure the data is captured. The delay time is configurable, and by default is set to 200ms.
INC-167871 · Issue 666295
Desktop browser java render error corrected
Resolved in Pega Version 8.5.6
Attempting to open Clipboard, schedule a report, or perform any activity which generated in a pop-up resulted in a blank screen and browser errors indicating "Uncaught TypeError: (…) is not a function 2. Uncaught TypeError: cannot set property '...' of undefined". This has been resolved by adding a semicolon to the last line of pzpega_desktop_automation_support_js.
INC-170466 · Issue 671852
Page group property passed correctly for complex questions
Resolved in Pega Version 8.5.6
When the Pega Survey Smart shape was used to configure a list of complex set of questions using Question rules and invoked using the Survey shape, the reload system was not passing the subscript value for the Page group property pyQuestionnaire. This caused an Invalid Reference exception and displayed an error pop up for the end user. Investigation traced this to a call to RefreshList to load a section holding pyQuestionnaire(Subscript) page content which was in place as part of a legacy fix but which has since been made unnecessary due to infrastructure changes in the DOM utilities. To resolve this, the ComplexQuestionCheckboxTemplate and pzComplexQuestionCheckBoxTemplateRowDetails section rules have been updated to remove the RefreshList action on checkbox.