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 427994

Accessibility enabled Layout group tabs browsing corrected

Resolved in Pega Version 8.3

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-C90261 · Issue 428123

Hotfix installer updated to adhere to installorder file included in the package

Resolved in Pega Version 8.3

In order to ensure hotfixes are always installed in the proper order, the installer has been updated to iterate over a set that is ordered according to the INSTALLORDER.PEGA file included in the DL file at packaging time.

SR-C88776 · Issue 428379

Added check for blank Value List Property referenced in Dropdown Control

Resolved in Pega Version 8.3

When a value list property was referred in the Dropdown control, the dropdown was shown as empty. This was traced to a property of type value list / value group, ClipboardProperty.getName() api returning as empty. To resolve this, a check has been added to ensure the value is populated with the correct property name if it is blank.

SR-D22170 · Issue 428402

Whitelisted RunTime_ControlPanel streams in Designer Studio development

Resolved in Pega Version 8.3

Using developer access in Designer Studio was generating SECU0016 errors in PDC: "Unauthorized access to the stream rule : Unauthorized access to the stream rule Data-Portal-DesignerStudio.pzRunTime_ControlPanel Rule-HTML-Section". This has been resolved by whitelisting stream names starting with pzRunTime_ControlPanel.

SR-C81653 · Issue 428450

Calling flow correctly resumed after sub-process completes

Resolved in Pega Version 8.3

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.

SR-C84939 · Issue 428565

setTenantName API exposed in the rules alyer

Resolved in Pega Version 8.3

In order to support more efficient message ingestion in a multi-tenant environment, the setTenantName API has been exposed in the rules layer.

SR-C87986 · Issue 428572

Resize handle correctly changed for RTL locale

Resolved in Pega Version 8.3

When the locale was set to RTL, dragging sections to the left caused a resize and dragging sections to the right moved them to the left. This has been resolved by ensuring the resizable handle for workarea is correctly changed when the locale is RTL.

SR-C89675 · Issue 428597

Case name caption security inserted

Resolved in Pega Version 8.3

In order to protect against the possibility of executing malicious JavaScript code by entering an appropriately modified name while adding new case type, pyCaption in menu items has been made HTMLSafe by converting JSON through the GSON library. Additional handling for Firefox has also been added to normalize tabName to properly display Recents.

SR-C91521 · Issue 428628

DX API updated for improved security

Resolved in Pega Version 8.3

Modifications have been made to the DX API to improve system security.

SR-C88236 · Issue 428787

Debug logging added to HTTP API for improved diagnostics

Resolved in Pega Version 8.3

Debug loggers have been added to the HTTP API to provide more complete diagnostics for an error where users are redirected to login screen after providing valid credentials. As a workaround, restarting the node server will resolve the login issue.

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