Skip to main content

Resolved Issues

View the resolved issues for a specific Platform release.

Go to download resolved issues by patch release.

Browse release notes for a selected Pega Version.

NOTE: Enter just the Case ID number (SR or INC) in order to find the associated Support Request.

INC-127347 · Issue 568022

GenerateAttachControl updated for iOS 13 compatibility

Resolved in Pega Version 8.2.8

It was not possible to upload files from an iPad using the Google Chrome browser when the "Attachments" control was used in the application. The attach control flowaction was not opening to select any files, and attempting to directly open the folder to add attachments showed them as grayed out. This was traced to the "Accept" tag not being supported in iOS 13, and has been resolved by removing accept= / from pzGenerateAttachControl .

INC-128731 · Issue 568840

Able to download/view attachments in Pega Mobile

Resolved in Pega Version 8.2.8

After uploading a PDF or .png file to a case, attempting to view or download it from Pega mobile was not working. The error "LINK-ATTACHMENT PEGASOCIAL-DOCUMENT Resource interpreted as Document but transferred with MIME type application/octet-stream" appeared in the browser console. This has been resolved.

INC-130499 · Issue 581443

Mobile offline nested repeating dynamic layout repaired

Resolved in Pega Version 8.2.8

Attempting to open a repeating dynamic layout while working in mobile offline caused the screen to freeze and an UnmodifiablePropertyException error to be generated. This has been corrected.

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-153805 · Issue 627966

Mobile app language remains consistent after data sync

Resolved in Pega Version 8.4.5

When using a Field Service Mobile App where the locale of all workers was set to nl_NL, the UI was intermittently flipping from NL to EN and and back again. This was traced to the locale of the requestor (field worker) being lost during synchronization of the mobile app data to the server, causing the UI to fall back to the default value of EN. This has been resolved by ensuring the requestor always uses the chosen locale for the operator.

Ready to crush complexity?

Experience the benefits of Pega Community when you log in.

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us