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-B2863 · Issue 275455

Improved offline decision shape handling for GoToPreviousTask

Resolved in Pega Version 7.3

The skipFlow condition in handleNotAFlowAndNotDisplayableShape function in the pzpega_process_engine rules has been updated to better handle offline use of customized GoToPreviousTask decision shapes.

SR-B30403 · Issue 290587

Layout group contents now load fully during a tab overflow

Resolved in Pega Version 7.3

Layout group contents were only partially loading when encountering a tab overflow in nested layout groups with defer loads. This was caused by an incorrect Layout Group height calculation, and has been fixed.

SR-B30416 · Issue 292621

Removed extraneous showerrors check from onfocusinlistener

Resolved in Pega Version 7.3

After configuring a Grid item with validation rules, adding multiple records to the grid and clicking on submit without providing the values on the required fields as expected resulted in all of the error messages based on the configuration showing. An unneeded check to showerrors as part of the onfocusinlistener function has been removed to resolve this.

SR-B30822 · Issue 289826

SignatureDate populated correctly

Resolved in Pega Version 7.3

The out-of-the-box signature control was passing the current date to the signature date field rather than the date parameter given. This has been fixed.

SR-B31303 · Issue 288518

Revision management GET logic revised

Resolved in Pega Version 7.3

When the revision manager creates a new revision, the second step is to add rules (strategies/data transforms etc.) into that revision so that a strategy designer can work on that. However, it was found that if one of the HTTP requests was of GET method, selecting the rules and hitting 'submit' constructed an oversized URL which listed all the rules listed on the Revision page and the browser would hang due to the GET exceeding the character limit. To avoid this, the logic used to create the post body has been modified to creating avoid long parameter values.

SR-B31533 · Issue 290736

Fixed wide repeat grid focus jump in IE

Resolved in Pega Version 7.3

When clicking on a wide grid in Microsoft Internet Explorer 11, the focus jumped to the left automatically even when all click/focus events have been removed from the grid. This has been resolved with a check so the system will not capture focus in cases where a horizontal scroll bar is present.

SR-B31778 · Issue 294184

First column name displays in tree grid

Resolved in Pega Version 7.3

The first column name was not appearing in the tree grid using the freeze header configuration. This has been fixed.

SR-B31778 · Issue 290725

First column name displays in tree grid

Resolved in Pega Version 7.3

The first column name was not appearing in the tree grid using the freeze header configuration. This has been fixed.

SR-B31778 · Issue 301431

Fixed tree grid column alignments for Internet Explorer/ Chrome

Resolved in Pega Version 7.3

When using freeze headers with fill 100% width, Internet Explorer and Chrome showed alignment issues between the header and content columns in a tree grid. This was caused by a missing semicolon in the inline style of left grid header for tree grid, which has been fixed.

SR-B31885 · Issue 288772

Attachment icons display correct type

Resolved in Pega Version 7.3

The attachment icon was not reflecting the attachment type. This was caused by an error in the pzWorkAttachmentIcon control which caused the File name to be passed as empty, resulting in a failure to fetch the correct image name. This has been fixed.

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