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 update your bookmarks. This site will be discontinued in Dec 2024.

Pega Platform Resolved Issues for 8.1 and newer are now available on the Support Center.

SR-D50584 · Issue 518450

Security added to retrieving operator list by URL extension

Resolved in Pega Version 8.4

It was possible to append information to the application URL which allowed an unauthenticated user to find a list of operators. This has been corrected, and will now result in the message "There has been an issue; please consult your system administrator."

SR-D50725 · Issue 516515

Page cleanup processes updated to facilitate Pulse Task creation

Resolved in Pega Version 8.4

Attempting to create a Pulse Task in an assignment resulted in a "The Operation completed successfully, but returned no content" screen after clicking submit. This was traced to an incorrect usage of createworkpage. To resolve this, the system has been updated so that before calling createworkpage, a page-remove will be done so createworkpage will not clean the assignment page.

SR-D53266 · Issue 516397

Synchronization continuation updated so mobile attachments properly preview

Resolved in Pega Version 8.4

Clicking on attachments in mobile would open them if the attachment had just happened, but otherwise would not open them at all. This was traced to an issue with Synchronization continuation: the page was properly loaded from database but its content was not used to fill the named OfflinePackage page (which contains only the search keys). This has been corrected by replacing the empty page with the one loaded from the database.

SR-D55559 · Issue 520973

Setting added to allow commas in bulk upload survey questions

Resolved in Pega Version 8.4

Questions uploaded in bulk to Survey Designer were delimited by comma, potentially causing an issue when an option itself contains a comma. Because this is a hard-coded Excel template value, this has been addressed with the addition of an extension where delimiter values can be configured and overridden.

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.

INC-136410 · Issue 591892

Check for mobile added

Resolved in Pega Version 8.6

While performing external assignment in the Designer Studio, the console error "Uncaught TypeError: Cannot read property 'isMultiWebViewOfflinePegaMobileClient' of undefined" was generated. Investigation showed that this was caused by the pega_desktop_api checking pega.mobile.isMultiWebViewOfflinePegaMobileClient, which was undefined while not working on mobile. To resolve this, a check for mobile has been added.

INC-136768 · Issue 588451

Question Wizard import will downcase answer types to match system requirements

Resolved in Pega Version 8.6

The Question Upload wizard would not create a File type question while using a survey template. The template has a column Answer mode in which accepts an input of the type of answer expected, but in this use case "File" was given instead of "file", resulting in the question being created using the default values. To resolve this, during the import process when the system parses the file and gets the contents from the data using the pzSetdefaultValuesforQuestions DT, mode values will be explicitly set to lowercase.

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