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-B86231 · Issue 360758

Error identification improved for Data Flow Errors landing page

Resolved in Pega Version 8.1

If a dataflow failed because of a particular input (row), the "Data Flow Errors" landing page was not showing which record was at fault. To correct this, the system will inspect the exception coming from the database layer to define which record failed the batch. If it's not possible to identify the actual record, a general exception will be generated.

SR-B88026 · Issue 354735

Modal dialog accessibility enhancements

Resolved in Pega Version 8.1

In order to ensure Modal Dialogs are accessible via screen readers and navigable using keyboard, the following criteria have been reviewed and updated as necessary for both editable and read-only use: - Modal dialog is accessible using the standard mix of screen readers (JAWS +Microsoft Internet Explorer + Windows / VO + Safari + Mac / Chromevox + chrome / NVDA / Firefox + windows) - Modal dialog is navigable using TAB key navigation - Modal dialog is dismissed on pressing ESC key - Modal dialog always has a aria label tied to the Title of the dialog - Modal dialog always has a close button

SR-B88777 · Issue 344614

Notes in the Service case in 360 Screen properly editable

Resolved in Pega Version 8.1

When attempting to add Notes in the 360 screen after launching a Service case in an interaction, the Notes section became disabled but the record of a new note was created. Investigation showed that if there was a Main section that was readonly and there was a section inside cell set to editable in the presentation tab in non-template mode, it was rendering as readonly when it should have been editable. This has been corrected.

SR-B89236 · Issue 358451

ShowHarness tabs localized

Resolved in Pega Version 8.1

Localization has been added to DC Tab names for showHarness action.

SR-B89743 · Issue 338705

Autocomplete overlay placement fixed for iOS

Resolved in Pega Version 8.1

The autocomplete overlay in mobile was not appearing in the correct place on iPhones. This has been fixed.

SR-B90076 · Issue 341632

Pagination fixed for customized reports

Resolved in Pega Version 8.1

When a report has Header display set to 'Hide column headings' or 'Summary/sort options only', clicking on the navigation page index did not display any further pages. This was caused by malformed HTML that caused the page change to not get picked up, and has been fixed.

SR-B91716 · Issue 340031

DSS rulesets for MQListener and MQConnector flows separated

Resolved in Pega Version 8.1

When both a Listener and a Connect-MQ are configured, the connector tried to make use of two DSS settings in order to work. However, this caused the previously working listener to start failing and throw an exception indicating the options being set are invalid. To resolve this, DSS rulesets for MQListener and MQConnector flows have been separated. This also makes the code backward compatible.

SR-B92177 · Issue 368665

Resolved "unique constraint" error in custom NLP data handling

Resolved in Pega Version 8.1

When saving an NLP record using a custom activity instead of the pzSaveSummaryReporting activity available from NLP framework, the error "Unique constraint (PEGADATA.PR_DATA_NLP_SUMMARY_PK) violated" was logged. This was traced to a parameter not being passed, and has been resolved by adding the unique value to pxID in pxSaveTADetails.

SR-B92421 · Issue 348757

Email Attachments use given mail encoding instead of defaulting to UTF-8.

Resolved in Pega Version 8.1

For email listener use cases, email attachments were always converted to HTML using UTF-8. This caused email characters to be changed when they were sent using any other type, ex ISO-8859-1 (Western European). To resolve this, the encoding used in the incoming email will be used to generate the HTML content before it is attached to the work object.

SR-B93296 · Issue 354784

pxIndexPurpose added to joins

Resolved in Pega Version 8.1

Declare index joins have been updated to add the pxIndexPurpose filter while joining two tables.

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