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.

INC-147873 · Issue 610865

Custom header character encoding for Subject added

Resolved in Pega Version 8.5.5

Case correspondence that contained a Subject with accent characters such as "Invitation à être" was being rejected by MailJet on the basis of encoding issues on the "Thread-Topic" when using custom headers. The error "BAD HEADER SECTION, Non-encoded non-ASCII data (and not UTF-8)" was generated. This was traced to the Send Email Smart Shape handling when using custom headers, and has been resolved by encoding the Subject before appending it to the Thread-topic header while adding custom headers.

SR-B66795 · Issue 317118

ConvertAttachmentToPDF Activity deprecated as part of PDM removal

Resolved in Pega Version 8.1

As the Pega Distribution Manager is no longer offered as part of the Pega application, the "ConvertAttachmentToPDF" function previously offered as part of PDM 3.3.5 is now [Withdrawn,Deprecated] from 'Pega-ProCom' & 'Pega-ProcessEngine'

SR-B69359 · Issue 337302

Tab header value works for SSO

Resolved in Pega Version 8.1

The Tab header value was not updated with the rule name or Work Object ID when SSO authentication was used with sub-domain URLs. This has been fixed.

SR-B73087 · Issue 343814

Fixed incorrect number formatting application in Spanish locale

Resolved in Pega Version 8.1

Errors were seen for fields having pxCurrency and pxNumber control when using the Spanish locale (es_CR):1. After entering an amount like 917.25 on a field which is configured to refresh section on click/on change, clicking on the field caused the decimal to move and resulted in multiplying the amount by 100 (91725.00) 2. Fields did not allow entering a comma as a decimal delimiter or were stripping the comma. This has been fixed by modifying pzGenerateTextinput assembly to not apply formatting for numbers in some specific locales.

SR-B74459 · Issue 329573

Corrected additional Fork connector

Resolved in Pega Version 8.1

When using a Fork decision shape configured to skip assignment conditionally, an extra connector link appeared in the screen flow. This has been fixed.

SR-B77623 · Issue 346655

Handling added for empty queue in DeleteDeferred

Resolved in Pega Version 8.1

The DeleteDeferred method was setting a step status fail after trying to delete a non-existent queue item. A catch block has been added which will back out if the SLA queue deletion fails.

SR-B78077 · Issue 364120

Documentation updated to assist in fixing UnresolvedAssemblyErrors when resolving RUF rules

Resolved in Pega Version 8.1

To address UnresolvedAssemblyErrors resolving RUF rules, the following help topics have been updated: Selecting-import-file-tsk Importing-cli-tsk Importing-cli-web-tsk To include the following cautions: * Review the archive contents to better understand which rule sets are capped and to determine the relatives risks and benefits of running uncapped rule sets. * Do not import an archive into an active runtime instance of Pega Platform because the archive can overwrite rules in use.

SR-B79034 · Issue 333532

Flow breadcrumbs improved for temporary objects

Resolved in Pega Version 8.1

Issues were seen with navigating a screen flow properly when the work object was temporary. The screen flow contained sections with some required properties and “Allow errors” was checked to support navigating back and forth when there were errors; clicking the breadcrumb to go back in the flow worked, but clicking Next to go forward again did not proceed to the next flow action. This was due to missing validations, and changes have been made to the Complete Assignment function to handle the errors for Temporary and Non-Temporary Cases.

SR-B82031 · Issue 345364

Filter popup aligns with selected column

Resolved in Pega Version 8.1

When a wide grid was scrolled to the right and a column was filtered, the filter popup as not aligned with the column being filtered. Instead, it was shifted to the left of the column. This was due to the popover not being aligned properly with the target, and has been fixed.

SR-B84658 · Issue 345365

Popover visible for autocomplete on overlay

Resolved in Pega Version 8.1

The Popover was not visible for autocomplete on an overlay when the center overlay option was checked. This has been fixed by adding a scroll handler with an 'if' condition to the rootPopover when there is a child popover on it.

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