INC-133301 · Issue 580677
Resolved authorization request errors on mobile
Resolved in Pega Version 8.2.8
After upgrading and rebuilding the APK with the HC Client Version – 7.41.8-SNAPSHOT, numerous "PYREDIRECTAUTHORIZATIONREQUEST" alerts during mobile interactions caused system performance issues. This was traced to a change in the handling for OAuth2 tokens and related to missing pyClientID column in the database table which forced the system to read all records from the table, and has been resolved.
INC-135159 · Issue 580673
Logic updated for deepMergeObj API
Resolved in Pega Version 8.2.8
Issues with the embedded page values being removed when navigating from a flow action and inconsistent localization of labels and captions in a mobile app were traced to the deepMergeObj API; the logic for the API has been revised to ensure the pxObjClass property is not removed from embedded pages during the doSave function.
INC-144948 · Issue 602275
Resolved JBoss memory leak
Resolved in Pega Version 8.2.8
JBoss logs indicated connection leaks. This has been resolved by limiting the scope of instance of ActionProvider, DataSyncRequestParser to a try-with-resources block which ensures that all resources are released.
SR-D95638 · Issue 556964
Added handling for mobile SharePoint attachments
Resolved in Pega Version 8.2.8
When an application was using SharePoint to store the attachments, adding an attachment in an offline-enabled mobile app and then synching resulted in the mobile app crashing if the user re-logged in and launched the same work object. This was due to the attachment handling. Attachments are downloaded during synchronization and they are base64 encoded: when a mobile phone processes the synchronization response, it decodes the base64 encoded attachment and saves the data in internal storage. In this scenario, attachments retrieved from SharePoint (REST Service) use a base64 conditional encoding that is different than in case Repositories or Pega Database storage. To resolve this, a check has been added to determine whether the base64 text contains newline characters, and if so the text is merged into one line.
SR-D18725 · Issue 488208
OrgUnit delete works as expected
Resolved in Pega Version 8.4
After creating two organization units such as Unit1 and Unit11 on the same level and mapping one operator to Unit11, attempting to delete Unit1 resulted in an error indicating the operator had to be deleted first even though unit1 had no operator associated with it. This was traced to Obj-List performing a 'like' check instead of exact match check for the deletion, and has been resolved by updating the ValidateDelete activity to do obj-browse instead of obj-list.
SR-D19999 · Issue 488268
Logic updated for displaying email attachments
Resolved in Pega Version 8.4
Once an Email had been sent with attachments, additional attachments could be added to the work object at a later time and would show up when the work object was opened as if they had been part of the original transmission of the message. This was traced to the logic not accounting for for the state of the data-corr-email object and showing all the work object attachments as sent as part of the email irrespective of when the attachment was added. To resolve this, the system has been updated to save all the attachment keys that are sent as part of the email on the data-corr-email instance and use that property while retrieving the list of attachments sent on the email. If the attachment is deleted, no hyperlink will be shown but instead a message on hover on the attachment memo will note that the attachment was deleted and not available for download.
SR-D22415 · Issue 493442
Enhancement added to expose BrowserAttachmentTypeTable
Resolved in Pega Version 8.4
By default, the inline view of PDF files appears with the thread name visible. An enhancement has been made to expose pzBrowserAttachmentTypeTable as a py rule: when the DT is overridden such that return is false for PDF, the inline view is not displayed but instead the PDF is downloaded when clicked.
SR-D23723 · Issue 503089
pxGenerateExcelFile updated for handling blank dates
Resolved in Pega Version 8.4
When using a custom template for exporting to Excel, blank DateTime property column values defaulted to the current date or to 1/1/1970. To resolve this, the pxGenerateExcelFile activity has been updated to ensure that an empty date will be exported as blank and that given dates will appear in the correct datetime format.
SR-D24470 · Issue 494628
Custom attachment category parameter passed to dropdown
Resolved in Pega Version 8.4
Attempting to use the out-of-the-box “Attachments control” which was configured at design time to use a custom category where both the custom category and the section class were in the same work class resulted in the attachment category dropdown defaulting to “File” instead of the custom category. Investigation showed that the custom attachment category name configured on the control was missing in one of the pre-processing activities sequence. To resolve this, the activity Work-.pzInitAttachContent and the initAttachmentPage activity have been updated to pass the custom attachment category parameter.
SR-D24651 · Issue 495766
Proper assignment instructions sent when transferring
Resolved in Pega Version 8.4
Assignment instructions were not getting added properly when transferring to Workbaskets. Because both .pyInstruction and Param.InstructionNote are set in call Reassign (to workbasket), the same instruction value was being given twice. To resolve this, step 8 (Call Reassign) of Work-.pyReassignAssignment has been modified and will not send the InstructionNote param as instruction is already updated on the newassign page with the instruction value on reassign page in the previous step (step 7).