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 note: beginning with the Pega Platform 8.7.4 Patch, the Resolved Issues have moved to the Support Center.

SR-D17318 · Issue 489605

Enhancements added to Proposition Filter

Resolved in Pega Version 8.3

Previously, when propositions were filtered based on only specific criteria, then propositions based on both the specific and default criteria were shown. An enhancement has been added to address this, as well as to create a better user experience for the proposition filter with a simpler UI and some additional features. In this revision, there is one data model that supports the platform proposition filter as well as Pega marketing's eligibilities. The condition builder is used in the Proposition filter rule to align user experience with marketing, and the new proposition filter supports parameters for when rules. DMSample contains an example proposition filter rule that uses and showcases the new UI, including available values.

SR-D64558 · Issue 527676

AttachmentContent supports S3 storage

Resolved in Pega Version 8.1.8

Using a D_AttachmentContent data page to display the contents of an attachment by way of the pyGetAttachmentContent activity worked when using the Pega database for storage, but generated an error stating CMIS access was disabled after switching to S3 storage. This was traced to restrictions on Link-Attachment pages in Step 2, Line 64 of pyGetAttachmentContent to enable attachment stream retrieval from web storage and repositories by D_AttachmentContent, which has now been removed. In addition, pyGetAttachmentContent has been updated to behave the same whether a Link-Attachment page or Data-WorkAttach page is provided when populateAttachStream is set to false, and the rule documentation (description/usage) has been updated accordingly.

SR-C87881 · Issue 427101

Additional dropdown options exposed for RD column definitions

Resolved in Pega Version 8.3

When using Column formatting in Report Definition ruleform, the "Negative format" option was losing its custom style after opening and submitting the "Format" popup using the magnifying glass. This was caused by the submitted popup overwriting the inherited style reference. Previously, the style ref options were hidden from the dropdown because the same UI is shown in the ruleform and the end user portals and the desire was to avoid end user confusion. In order to support developer use, pzPopulateNegativeFormat has been updated to expose the missing options in the dropdown.

INC-175990 · Issue 652088

Browser check added to ensure on-click event trigger

Resolved in Pega Version 8.6.1

Clicking Submit from the screen after opening the case from the worklist did not trigger the click event action when using Microsoft Internet Explorer 11. This was due to a change in that browser, and has been resolved by adding a check.

SR-D7114 · Issue 483623

Corrected grid column header misalignment

Resolved in Pega Version 8.3

After upgrade, a grid's first column heading was misaligned when using the Microsoft Internet Explorer browser. This was traced to Quirks mode related CSS not being removed after support for Quirks mode ended, and has been corrected.

SR-D59504 · Issue 524641

Attachment drag drop searches only current Ajax context

Resolved in Pega Version 8.1.8

When the Interaction for customer service was open and more than 1 task from the sidebar was open, the drag and drop zone was missing on any subsequent Task/Cases past the first. In an Ajax container scenario, getElementByID js was searching in all the containers because they were present in DOM, and it was losing context. To resolve this, the code has been updated to only search in the current context when using an Ajax container.

SR-D51601 · Issue 516703

Hover logic updated

Resolved in Pega Version 8.1.8

When using a dropdown in a grid layout configured with a smartInfo to be displayed on Hover, the smart tip was sometimes not displayed when the hover moved from the top to point to the dropdown. If the hover was done quickly, it was displayed. Previously, the hover was calculated only by cursor x, y positions and elements boundaries: to resolve this issue, the logic has been updated to also consider cases where the element is still hovered without meeting these conditions.

SR-C74648 · Issue 422904

Autocomplete arrow placement corrected in Right to left local mode

Resolved in Pega Version 8.3

When using the Autocomplete control, the blue arrow was seen to have an incorrect placement/orientation in RTL mode. This was traced to the autocomplete background-image in RTL mode being the same as that for LTR, and has been resolved by adding specific background-image for RTL.

SR-D37326 · Issue 504935

Resolved clipboard formatting issue in Reply Thread and Send Correspondence

Resolved in Pega Version 8.2.4

Issues were seen with the table formatting of client data after mail was sent. This has been resolved by ensuring all borders are retained in RTE when used in both "Send Correspondence Task" and "Reply Thread".

SR-D42143 · Issue 509316

Tab names maintained after Ajax container refresh

Resolved in Pega Version 8.2.4

When using an Ajax container in Tabs mode, a browser refresh with multiple tabs opened caused the active tab name to be changed to the main tab name. This was caused by the work object name being lost during the refresh, and has been corrected.

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