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.

Please note: beginning with the Pega Platform 8.7.4 Patch, the Resolved Issues have moved to the Support Center.

INC-155214 · Issue 617006

GetBinaryFilesRef updated for resolving wildcard

Resolved in Pega Version 8.5.3

After upgrading from 8.2 to 8.4, errors related to "Unable to serve file java.lang.IllegalArgumentException: Illegal characters detected in the path" appeared numerous times during full syncs, either on first time login or after cache clear. This was traced to normalizeRelativePath failing, and was caused by a resource declaration in pzGetBinaryFilesRef that encountered an issue where wilcarded URLs were not automatically resolved while packaging Static resources. This has been resolved.

INC-155752 · Issue 622772

Hidden Question pages and answers will be saved to database

Resolved in Pega Version 8.5.3

After a question page was shown and some values were entered, going back to the question and reverting an option caused the question page to not be visible, but the answer values persisted in the clipboard and were eventually saved into the database. This was a missed use case for Question page smart shapes, and has been resolved by updating the pzSetQuestionPageParams data transform so that whenever a question page is evaluated to either to show/hide, when the question page visibility is set to false and the pyClearAnswerValuesWhenQPHidden 'when' rule is overridden, the corresponding values will be wiped from the clipboard and only the required values will be saved to the database. However, please note this is not supported for branching logic and visibility conditions should be used instead.

INC-156211 · Issue 620193

Verbose comments removed from wrapper

Resolved in Pega Version 8.5.3

Comments with references to external links have been removed from some harness wrappers.

INC-157317 · Issue 620573

Signature Capture supported in RDL

Resolved in Pega Version 8.5.3

An enhancement has been added which supports using Signature Capture on forms in repeating dynamic layouts.

INC-157596 · Issue 624124

Mobile channel upgrade wizard correctly initiated

Resolved in Pega Version 8.5.3

After upgrade, the offline mobile app was not loading the correct portal. This was traced to missing properties needed to launch the upgrade wizard for channels upgrading from a previous release to v8.5, and has been resolved by setting those properties in upgrade activities.

INC-158468 · Issue 626380

RecordFieldValuesList page cleared

Resolved in Pega Version 8.5.3

Investigation o0f web node crashes traced the issue to a condition where the RecordFieldValuesList page was not cleared. This has been resolved.

INC-135015 · Issue 591982

Handling added for overriding questions rules

Resolved in Pega Version 8.6

After overriding questions rules and then upgrading/validating Question Groups, questions were not shown. It was necessary to manually edit, save, and refresh for the questions to appear, affecting mainly Rule-PegaQ-QuestionGroup rules. This was traced to missing handling for this usecase. The commit was added in Revalidate and Save, which was committing different data because the upgraded data was not copied back to step page being used. Due to this, the commit in BulkValidateSave was overriding the changes done in the pzUpgradeSurveyInstance activity, and the survey upgrade was failing. To support this use, Page-Copy has been added to pzUpgradeSurveyInstance after the pzSaveSurveyInstance call step to copy the updated data to the step page which will later be committed by BulkValidateSave during revalidate and save.

INC-135720 · Issue 594793

Case link shows in Social messages for the old cases

Resolved in Pega Version 8.6

After upgrade from v7, the case link was not visible for the cases that were created in the old platform version. In Pega 7.1.7, metadata was stored in .pyPrivacyContextor while the later versions are using .pxContextType for Case type to show the related data. To resolve this, new properties have been implemented to hold the Case ID link.

INC-136091 · Issue 598905

Activity updated for Mobile attachment access

Resolved in Pega Version 8.6

Preview and download were not working for attachments stored in Pega Cloud Storage repository for mobile devices. Attempting to open an email attachment to preview or download resulted in a console error and the tracer showed the message 'Class pxLinkedRefTo does not exist'. This has been resolved by updating "pzpega_control_attachutil" to use the activity "GetAttachmentReference" for interactions with the attachments from any storage type.

INC-136202 · Issue 603904

Needed offline mobile resource added for upgraded channels

Resolved in Pega Version 8.6

The error "Mobile login issue - "Resource missing. See client logs" appeared after upgrading the platform and updating the mobile channel interface. A logout button appeared, and clicking it generated a popup with "Cancel" and "Log off" buttons. Clicking Cancel returned the user to the default UI in the mobile screen. This was traced to py-avatar.css not being present, which is a resource needed for the offline application with the current platform, and this has now been added.

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