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-B13517 · Issue 293343

Icon alignment fixed in grids with skin inheritance

Resolved in Pega Version 7.3

The Header Title and the Collapsible Icon of a grid were misaligned due to an error in skin inheritance. The pzTemplateNewSkin1 legacy standard format has been changed to correct this.

SR-B14210 · Issue 284725

Autocomplete updated to handle null resultcount from data page

Resolved in Pega Version 7.3

The autocomplete control was not rendering a list supplied by data page results due to the pxResultCount being null in the results of the datapage. The count size calculation in the autocomplete function has been reworked to resolve this.

SR-B14416 · Issue 289018

Fixed double actions on repeat layout

Resolved in Pega Version 7.3

In a Grid Repeat Layout, actions added on the event 'Enter' were automatically added to event 'Click' and resulted in double actions at the runtime. This was an issue with the system incorrectly setting the pyKeyCode in pzGridActionSets Activity, and has been fixed.

SR-B14432 · Issue 286451

Editability check added to asterisk symbol (mandatory field expression) display

Resolved in Pega Version 7.3

Sections using conditional read-only and editable modes displayed the mandatory expression (asterisk symbol) in both modes. To correct this unexpected behavior, the GenerateLabelCellContent RUF has been updated to check whether the control is editable and only generate the asterisk if the result is true.

SR-B1478 · Issue 274489

Better handling for empty LockInfo page

Resolved in Pega Version 7.3

Intermittent errors were encountered when attempting to expand rows of a repeat grid. This was due to handling difference related to a pre-condition check for the LockInfo page used to create error messages. Since the LockInfo page is not required or consistently used, the system has been updated to better handle cases where it is empty.

SR-B15575 · Issue 285206

Accessibility added to flow action label

Resolved in Pega Version 7.3

When an accessibility tool such as JAWS was used, the flow action label was not read out and no indication was given regarding what action was expected. To correct this, the RUF pzGenerateControl has been updated to add tabindex=0 so the section heading can be read out by accessibility tools.

SR-B15575 · Issue 290496

Accessibility added to flow action label

Resolved in Pega Version 7.3

When an accessibility tool such as JAWS was used, the flow action label was not read out and no indication was given regarding what action was expected. To correct this, the RUF pzGenerateControl has been updated to add tabindex=0 so the section heading can be read out by accessibility tools.

SR-B15673 · Issue 288077

DatePicker calendar pop works as expected

Resolved in Pega Version 7.3

Unexpected behavior was seen where the input box of a date control used as Date+calendar popped up the calendar on click when Text entry was not allowed and did not pop up the calendar when Text entry was allowed (both in disabled mode). This was traced to an error in the data-ctl attribute for that span, and has been fixed.

SR-B15673 · Issue 288076

DatePicker calendar pop works as expected

Resolved in Pega Version 7.3

Unexpected behavior was seen where the input box of a date control used as Date+calendar popped up the calendar on click when Text entry was not allowed and did not pop up the calendar when Text entry was allowed (both in disabled mode). This was traced to an error in the data-ctl attribute for that span, and has been fixed.

SR-B15790 · Issue 285997

Handling added for dot in visible-when rule

Resolved in Pega Version 7.3

On click of the icon next to the visible-when rule in order to open the rule, the error "Unable to open the rule as Base Class Value is empty" was generated if the 'when' rule of the conditions included a dot. To correct this, the pega_openRuleSP logic has been modified to fall back to the section class from the PRXML when the value of baseClassValue is empty.

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