INC-161398 · Issue 639855
DataSync SynchronizationResponseStreamer logging enhancements
Resolved in Pega Version 8.7
The PegaRULES log contained "Response page does not match request, will generate failure response" errors even though no functional impact was observed. In order to enhance troubleshooting, additional DEBUG logs have been to DataSyncHandler, SynchronizationResponseStreamer is now logged on INFO level and contains more detail, and the error message has been modified to "Cannot prepare continuation response because offline package was stale. Will generate reset schedule response." to be more informative.
INC-168935 · Issue 645394
CalendarGadget updated to display events in Saudi locale
Resolved in Pega Version 8.7
When using the pxCalendar section with the locale setting ar_SA, the calendar was correctly converted to a Saudi calendar but the events which were showing in the English version of the calendar were not showing up in in the Saudi Calendar. This was caused by the CalendarGadget page not populating properly due to the localized Hijri calendar failing a datetime check that was looking for a Gregorian calendar with time in GMT format, and has been resolved by updating the when rule "pzShouldDisplayEvent " to use the proper function for the localized calendar.
INC-190270 · Issue 681086
MSGraph email listener enhancements
Resolved in Pega Version 8.5.6
Attachments with .eml /.msg extensions were treated as FileAttachments by the MS Graph API and generating a classcastexception. To resolve this, a check has been added to identify the attachment along with content type so .eml will be correctly recognized. In addition, the MSGraph email listener functionality related to converting from Graph to MIME message has been enhanced around the 'TO' and 'CC' recipients in a MIME message and for parsing nested attachments in Item attachment for addition to MsgraphMessage.
SR-D83060 · Issue 547919
Repaired History class report column sorting
Resolved in Pega Version 8.5
Attempting to sort any of the columns in a report using the History class did not render the results and the error "Cannot render the section" appeared. Tracer showed a Fail status for some OOTB activities with the message "java.lang.StringIndexOutOfBoundsException". Investigation showed the logic in pzMergeAutoGenForProp activity was failing because the pyIsFunction property was not set on the UIField pages for function columns. To resolve this, the logic for pzMergeAutoGenForProp has been modified to get pyIsFunction from the field name.
SR-D94258 · Issue 560795
Thread context updated to supply steppage
Resolved in Pega Version 8.5
After upgrade, Server Startup was failing with the error "PEGA Rules Server not available". Investigation traced this to missing steppage information while invoking Rule-Utility-Function (from declare trigger when rule) during startup, which was caused by the thread calling the declare trigger, which was different from the thread running WhenRule, not being properly initialized during startup. To resolve this, the thread context has been changed to gThread, which contains the necessary steppage information.
INC-126662 · Issue 561314
Thread context updated to supply steppage
Resolved in Pega Version 8.5
After upgrade, Server Startup was failing with the error "PEGA Rules Server not available". Investigation traced this to missing steppage information while invoking Rule-Utility-Function (from declare trigger when rule) during startup, which was caused by the thread calling the declare trigger, which was different from the thread running WhenRule, not being properly initialized during startup. To resolve this, the thread context has been changed to gThread, which contains the necessary steppage information.
SR-D67667 · Issue 533265
Corrected unexpected Survey button toggling
Resolved in Pega Version 8.5
After configuring the radio buttons so that on click of YES a new section should be displayed, clicking on the radio buttons in Pega Survey was toggling the buttons automatically. Investigation showed that on click, both refresh section and run activity were executed asynchronously, triggering the property mapping refresh before answers were clicked. To correct this, the clearSelection function call in pzsurvey_ui_userscript JS file has been modified, and questionPageName has an added 'if' condition.
SR-122637 · Issue 183016
MaxFileLength property added to avoid truncating attachment names
Resolved in Pega Version 7.1.8
While adding the attachments to the case using drag and drop functionality, the file name and file description were being truncated. However, a new property named "pyMaxFileLength" is now available as an override in pyDefault Model to set a different name limit. If this property is not set, it will take the default value of 60 and proceed. Also for UI error messages, pyNote property in Data-WorkAttach-File and Embed-DragDropFile in the application ruleset must have the max length limitation removed from there or the MaxFileLength will be overridden by that setting.
SR-128081 · Issue 193016
Session Timer / Log Off corrected
Resolved in Pega Version 7.1.8
After upgrade, the Session Timer control was not working correctly when created as a script in the section and then embedded in a portal harness. In ML7, the usage of window.showModalDialog was altered because Google Chrome and Firefox no longer support it. This included modifying the desktop app TimeoutLogoffDialog to use a modal dialog, but a syntax error was introduced in oSafeURL; correcting this resolved the display issue with the timeout dialog. In addition, the LogOffTimer has been modified to use the updated windows.close() function and pxSessionTimer has been marked as available.
SR-129117 · Issue 196578
Resolved agent/tenant parent/child access for disabled agents
Resolved in Pega Version 7.1.8
When a shared system had an agent which was disabled, doing a "Save As" of the agent into the tenant env (to different application / RS) by logging into the tenant and enabling the agent failed with the error "No such Access group." This happened because the agent rule (created in the tenant) was running in the context of the shared system instead of the tenant system and could not find the access group. The issue was that the runActivityAsTenant function was not working as expected in the case of a child requestor trying to use the parent requestor's authorization, and this has been fixed.