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-D11296 · Issue 484856

Microsoft Internet Explorer Flex layouts updated to mode 7.0

Resolved in Pega Version 8.3

Given a grid with 8 columns in the Agents Landing page, the columns on each end were distorted when viewing the grid in IE. This was an issue with the class flex-grid-table-wrapper not correctly handling scenarios where grid cells containing section includes were not visible, and has been corrected by updating pzagentscheckbox and pzagentsstatus to layout mode 7.0 so zoom is supported.

SR-B3280 · Issue 279492

Resolved skimming error

Resolved in Pega Version 7.3

Errors were getting thrown on the screen while performing minor ruleset version skimming of one version into a new ruleset version which was higher than the ruleset version mentioned in the application rule. This was due to the target version not having the correct context because the application didn't yet exist or because the operator was not logged into the target context. In order to resolve this, the messages in the page will be cleared before skimming to avoid validation. It is then recommended to log into the new application and use the Application Validation tool to validate the newly created rulesets application.

SR-C95250 · Issue 487995

Null check added to resolve non-impacting InvalidParameter exception

Resolved in Pega Version 8.3

Creating a child case from the SLA goal activity using the 'AddCovered' activity generated the message "Exception in queue item: cannot be null or blank". The error "com.pega.pegarules.pub.clipboard.InvalidParameterException: cannot be null or blank" was also seen. However, no functionality impact was observed. This has been resolved by adding a null check to the getPortalName method, and modifying the HarnessUIBuilder.java file to add safe checks for whether 'portalName' is empty or not.

SR-B13088 · Issue 287632

SLA correctly reset after reassignment

Resolved in Pega Version 7.3

When the SLA values were updated on routing the task, the newAssignPage and assign table were updated with the new SLA details but the pxFlow page was still holding the old SLA values. This caused the updated SLA details to not be displayed in the out-of-the-box pyAssignmentListGadget section. This was an issue with the pxAdjustSLA and Reassign activities not completely updating the embedded page pxFlow in the WorkPage completely, and has been fixed.

SR-B2093 · Issue 277296

Corrected page passivation for parameterized data pages

Resolved in Pega Version 7.3

A null-pointer exception error was generated when performing findPage() on a parameterized Data page after the page/thread was passivated and restored. This was traced to a situation where a page with meta data was not correctly saved while passivating due to a failed condition check on last update time, and has been resolved with changes to the EditDataPageHandler to update the access time whenever page is loaded from findDataPage() method.

SR-B5560 · Issue 276633

Corrected page passivation for parameterized data pages

Resolved in Pega Version 7.3

A null-pointer exception error was generated when performing findPage() on a parameterized Data page after the page/thread was passivated and restored. This was traced to a situation where a page with meta data was not correctly saved while passivating due to a failed condition check on last update time, and has been resolved with changes to the EditDataPageHandler to update the access time whenever page is loaded from findDataPage() method.

SR-C86589 · Issue 436265

Added explicit thread cleanup to resolve case worker portal UI rendering problem

Resolved in Pega Version 8.3

Creating a case in the case worker portal was resulting in the respective screen being rendered with a distorted UI. This was traced to an issue in topnavigation where the thread was being changed to a base thread and skipping the FlowModalProcess thread removal when the new DC action was triggered. To resolve this, the system has been modified to append "$FlowModalProcess" in harnessOnBeforeUnload if it is missing to make sure the FlowModalProcess thread is removed.

SR-D33359 · Issue 505773

SelectAll properly applied to only the page selected

Resolved in Pega Version 8.2.4

In repeating grid, applying SelectAll on one page resulted in it being applied to the next page as well even though all records in the other page were not selected. Investigation showed that on change, the 'when' condition added to refresh the list was always false. To resolve this, the condition in section pzBulkProcessingCheckbox which refreshes the list once the checkbox is changed has been removed.

SR-B32247 · Issue 291773

Resolved null-pointer exception at ReferencePropertyLinkToCommonParent

Resolved in Pega Version 7.3

When a reference property (liked via top level page) was copied with-in the page (intrapage), an null-pointer exception would be generated by a bad link if the number of levels in the new property differed from the original. The issue was traced to an error in the After Copy duplicator that did not correctly evaluate the target property in all environments. More robust testing has led to refinements on the duplicator to resolve this issue.

SR-C29160 · Issue 419494

Performance improvements made on bulk actions

Resolved in Pega Version 8.3

Latency was observed when performing transfer Bulk Action on cases. Investigation showed that the "Select Action" button in pzBulkProcessingActionSection contained a refresh other section action for the pzBulkProcessingCheckbox section that executed on each row of the grid rendered. This refresh is not needed as the "Post value" action will take care of posting the selected checkbox data to clipboard, so it has been removed to resolve the performance issue.

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