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-C81185 · Issue 427993

Accessibility enabled Layout group tabs browsing corrected

Resolved in Pega Version 8.2.2

When using Layout group (Tab) or a Tabbed Layout for viewing client information in Tabs with Accessibility enabled, the system was reading each tab and its content but then focus was returning to the browser and tracing through all elements before moving on to the next tab. This was traced to an incorrect tabindex setting in the pzpega_ui_template_layout_header file, and has been fixed.

SR-C89504 · Issue 435566

Multi-Select values visible in read-only

Resolved in Pega Version 8.2.2

The Selected Multi-Select values were not seen on the read-only review screen. This has been corrected.

SR-C95187 · Issue 433824

IO exception logging enhanced

Resolved in Pega Version 8.2.2

In order to improve diagnosing problems such as DDS nodes not joining a cluster despite Cassandra nodes being run successfully, logging enhancements have been added that include details about IO exceptions.

SR-C95253 · Issue 435787

Custom datetime controls correctly appended to Excel export

Resolved in Pega Version 8.2.2

The timezone was not being appended to datetime when exporting to Excel if a custom control was used. This has been corrected.

SR-C90418 · Issue 436017

Exception handling improved for pxAdjustSLA, pxAdjustSLATimes, and pzAdjustSLATimesInBulk functions

Resolved in Pega Version 8.2.2

If the SLA Deadline days were updated from 0 to 1, the SLA agent did not trigger the deadline escalation activity and the error "com.pega.pegarules.pub.context.PRQueueException: Instance of class Queue not found: SYSTEM-QUEUE-SERVICELEVEL.SYSTEM-QUEUE-SERVICELEVEL" was generated. This has been resolved with the addition of better failure handling to the pxAdjustSLA, pxAdjustSLATimes, and pzAdjustSLATimesInBulk functions for cases where an exception is generated.

SR-D3767 · Issue 438200

Enhancement added to track list based report definitions for statistics

Resolved in Pega Version 8.2.2

In order to expand the use of pyDefaultReport for Log-ReportStatistics, an enhancement has been added to pzPopulateListReport to call the pzPopulateStatisticsInfo activity with the required parameters to enable tracking of list based report definitions so they can be included in the report statistics table.

SR-C97772 · Issue 435630

Fixed Export to PDF page formatting

Resolved in Pega Version 8.2.2

A formatting issue was seen when using export to PDF; the first page contained only the title of the report as well as the filter, the generated date, and the number of records, and the exported data was included only from the 2nd page onwards. This has been corrected.

SR-D3788 · Issue 437779

Corrected temp page reference for save-as in CreateAndManageWorkFromEmail

Resolved in Pega Version 8.2.2

Attempting to save-as pyCreateAndManageWorkFromEmail was failing due to a missing reference to TempCurrentPage in Pages and Classes. This has been corrected.

SR-D3405 · Issue 439259

URL construction logic updated for Tracer

Resolved in Pega Version 8.2.2

When trying to trace a requestor from the requestor management landing page, a 400 bad request error was generated. Investigation showed that when forming the tracer URL, the pxRequestor.pxRequestorPathInfoInReal property was being appended to it. Because the property contained unencoded characters([), the request was not being processed. To resolve this, the URL construction logic has been changed to use pxThread.pxReqBaseURI.

SR-C89040 · Issue 438828

Calling flow correctly resumed after sub-process completes

Resolved in Pega Version 8.2.2

If a case was processed via Operator1 and passed as an assignment to a workbasket where Operator2 picked it up and performed a Reject case on it, the process in Flow1 correctly called Flow2, but once Flow2 was processed Flow1 was not resumed. If Operator2 only performed the Reject processing, Flow1 was resumed. To to ensure the correct flow resumption, the location of the pyFirstRun setting in flowMethodBody FUA has been updated.

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