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.

INC-130677 · Issue 570040

When rule accepted in column header

Resolved in Pega Version 8.1.9

A grid was not rendering if it contained a 'when' rule on a column header. This was a missed use case and has been resolved.

INC-143545 · Issue 600711

Support for 'when' action evaluated in runtime

Resolved in Pega Version 8.1.9

A 'when' rule was not evaluating properly on enabling "Optimized code" and "Personalize table" options for table/grid. This has been resolved by adding support for a 'when' action in a templated grid.

INC-211018 · Issue 707524

Number control correct when IME is Japanese

Resolved in Pega Version 8.6.4

The Microsoft Windows Input Method Editor (IME) allows developers to enter complex characters in four different East Asian languages using the standard keyboard. When IME was in Japanese mode, entering a number resulted in the input happening twice with the result of an entry such as 12345 becoming 124512345. This has been resolved by updating the code to ensure there is no duplicate IME keyboard event.

INC-204256 · Issue 701948

Helper Text displays for radio buttons with 'when' condition

Resolved in Pega Version 8.6.4

The helper text overlay was not displaying on radio button fields that were conditionally visible using a 'When' rule, though it displayed as expected if a visible expression had "Run visibility condition on client" checked. This has been resolved by adding support for a helper text overlay on radio button with visibility condition (when rule).

SR-D68328 · Issue 557751

Unload handler added for use with custom popups

Resolved in Pega Version 8.1.9

A memory leak seen in Microsoft Internet Explorer was traced to a custom script to close windows which bypassed window unload and continued to hold some objects in memory. This has been resolved by introducing a new file which will load only for popup harnesses and which registers the unload handler to remove the popup window references.

INC-130011 · Issue 571833

Resolved stale reference error when swapping stages with drag and drop

Resolved in Pega Version 8.1.9

If user swapped stages (2nd stage to 1st stage) using drag and drop and then added a participant or role in the stage, a Pega blue screen appeared. This was traced to using a grid with reorder and an inner grid in the cell. On drag and drop, the grid reference object was stale and not in sync with the latest table. To resolve this, code has been added to reinitialize the inner grid on drag and drop.

INC-142277 · Issue 601778

Header style inheritance corrected

Resolved in Pega Version 8.1.9

When a header style for a container was explicitly set, any layout underneath inherited that style when using container formats set to 'Use Skin Base Settings'. This has been resolved by increasing specificity for the header title.

INC-212509 · Issue 708358

Support added for Checkbox control for property with declare expression

Resolved in Pega Version 8.6.4

The checkbox control was not displaying the true/false text configured for the control in section when using a property with declare expression. This has been resolved by adding the logic necessary for this use case.

INC-215582 · Issue 712286

Cosmos calendar icon handles allow entry set to no

Resolved in Pega Version 8.6.4

When using the Cosmos theme, the Calendar icon became disrupted when "allow text entry" option was set to "no". This has been resolved.

INC-199469 · Issue 707513

PDF margins made available as parameters

Resolved in Pega Version 8.6.4

After update, margins were different in exported PDFs. This was due to upgraded jar files: PD4ML v3 used setPageInsets(new Insets(top, left, bottom, right)) , but the v4 jar uses setPageMargins(new PageMargins(left, top, right, bottom)) . Because the order of values (20, 10, 10, 10) were not changed this produced a different result. To resolve this, PD4ML margins are now available to be set as parameters: Param.pyMarginLeft, default value 20 Param.pyMarginTop, default value 10 Param.pyMarginRight, default value 10 Param.pyMarginBottom, default value 10 When standard activities like HTMLToPDF / pyViewAsPDF / pyAttachAsPDF are used, add a Property-Set step before calling the activity to add the necessary margin parameters. When CreatePDF smart shape is used, set the parameters via the connector of the CreatePDF.

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