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-C80084 · Issue 417239

Target connectivity preference updated in Revision Manager to address deployment error

Resolved in Pega Version 8.1.3

Using the deployment page to deploy a revision or migrate it to a target environment was failing. This has been resolved by correcting the target connectivity preference in the connector rules.

SR-C81857 · Issue 420240

Enhancement added to support dropdown with page list property

Resolved in Pega Version 8.1.3

To enable the use of a dropdown control with a property of type page list, an enhancement has been added to support a clipboard page for drop down and autocomplete.

INC-141895 · Issue 601985

Options not cached by default for picker controls

Resolved in Pega Version 8.4.4

Properties created in the data model of the case type were not showing in the drop down of custom conditions in a decision step. The property did not appear on the left hand side 'when' rule of the case designer in App Studio or Dev Studio, but did appear on the right hand side of the same 'when' rule. The issue temporarily resolved when the context class parameter was hardcoded with the class name. This was traced to the properties being cached by pzInnerEmbedConditions, and has been resolved by unchecking "Enable caching of options" for any picker control.

SR-C79302 · Issue 416825

Added backwards compatibility for ValidateDelete in Records Editor

Resolved in Pega Version 8.1.3

Due to a missed use case, ValidateDelete was not being called from the new records editor. This has been corrected by adding the step to call ValidateDelete in pzDeleteRecord activity.

INC-148115 · Issue 605423

Autocomplete results list position scrolls inside a table

Resolved in Pega Version 8.4.4

Given a row editable table with a fixed height and freeze grid header, when autocomplete was included in a row of a table and the down-arrow was pressed to get the list of options in dropdown, this drop-down popup was not moving along with the row during scrolling. This was due to scroll handler not being triggered for popover when inside a hierarchical table, and has been resolved.

INC-140110 · Issue 600400

Large filter values accepted in Report Definition edit

Resolved in Pega Version 8.4.4

Report definition edit filter values were not accepting large comma separated values properly. This has been resolved by modifying the logic in RRFilters_Logic to use ReportFilter.getReportFilters.

INC-139574 · Issue 606143

Exception handling added for dataflow rule assembly

Resolved in Pega Version 8.4.4

A Blue Screen error was coming up in the Customer Service Web Chat Application after an agent accepted the incoming chat request and sent messages in the chatbox in the Interaction portal. This has been resolved by adding handling for exceptions that occur when inlining templates during dataflow rule assembly, when inlining templates, we weren't handling exceptions properly.

INC-150578 · Issue 607479

rich text editor control handling updated for survey display text

Resolved in Pega Version 8.4.4

After upgrade, Display text in the survey was missing for the question rules which used Rich Text Editor control. This has been resolved by updating the system to copy DisplayText and QuestionText into DisplayTextWrapper.

SR-C71070 · Issue 417207

UI-Toolkit updated to resolve issue with fields overlap in dynamic layout collapse header

Resolved in Pega Version 8.1.3

The UI-Toolkit has been updated to resolve an issue with Dynamic layout where using a Collapsible Header that has multiple fields to be displayed resulted in the fields overlapping or being mis-aligned.

INC-144851 · Issue 604482

Date Time picker works with locale es_US

Resolved in Pega Version 8.4.4

When an Operator had the locale es_US (Spanish) set on the Profile, the Date Picker on the application was throwing validation errors when a date or time was chosen from the out-of-the-box Date Time Control. Investigation showed the date-time format for locale es_US was not supported, and the getDateTimeFormat API has been updated to support this format (11:00 a.m.).

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