INC-131592 · Issue 583435
Jsoniter parser upgraded
Resolved in Pega Version 8.2.8
After upgrade, the pxTextinput property Prompt List was being converted into decimal upon clicking finish assignment. This was traced to the jsoniter parser, and has been resolved by upgrading the parser in the jsoniter library.
INC-132876 · Issue 579646
Retrieve device log feature repaired
Resolved in Pega Version 8.2.8
Remote log retrieval was not working for delta datasync. This has been corrected.
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.
INC-128923 · Issue 594161
Cross site scripting security update
Resolved in Pega Version 8.6
Cross site scripting protections have been added to OpenNoteDetails.
INC-132590 · Issue 590493
Exported Excel from Decision Table wraps correctly
Resolved in Pega Version 8.6
After upgrade, entries were displayed in a single line on exporting a decision table to Excel despite WrapText cell formatting being set. This was traced to the WrapText cell formatting set under the UpdateGridCells() function being overridden inside an addDataFormat() function callas part of DecisionTableWorkBookConverter.java. This has been resolved by adding the new function "setWorkAreaCellStyles" and calling it after generateWorkbook() function call of super class (AbstractWorkBookConverter.java).
INC-132930 · Issue 600294
Updated UpdateDateTime handling for branch merge SaveAs
Resolved in Pega Version 8.6
After Pega API's standard branch/merge service was consumed, the service was not returning response as expected due to the system encountering listing conflicts on the branch merge. The error "a rule in lower version has been updated more recently than when the checkout was created" was generated. This has been resolved by updating the Record API (pxUpdateRecord / pxCheckIfStale) to handle setting pxMergedSynchronized property to the pxUpdateDateTime of the base rule instance when doing a Save As into a branch ruleset from a non-branch ruleset / non personal ruleset. Please note - this fix is only applicable to Record API SaveAs, and will not work if customized logic is used to perform the SaveAs.
INC-136186 · Issue 592969
JAWS reads the name of the field/instructions
Resolved in Pega Version 8.6
JAWS was not reading the name of the field/instructions in a work group. This has been corrected.