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 update your bookmarks. This site will be discontinued in Dec 2024.

Pega Platform Resolved Issues for 8.1 and newer are now available on the Support Center.

SR-B796 · Issue 277684

Report Definition updated to handle null value field grouping

Resolved in Pega Version 7.3

Report Definitions gave a blank count when grouped by a field with null values. An unnecessary check has been removed from the GenerateGridHTML RUF to correct this issue.

SR-B7965 · Issue 291732

Resolved mobile case switching exception

Resolved in Pega Version 7.3

The console error 'Exception while trying to set work item as completed in assignment list' was seen while context switching a case in a custom mobile app. This was caused by the configuration calling submit during preprocessing, and has been fixed by ensuring the onSuccess callback of finishAssignmentAction is called when there is no next Task.

SR-B8129 · Issue 280611

Resolved DATA-ADMIN-LOOKUPLIST authentication error

Resolved in Pega Version 7.3

After upgrade, the security access error "You lack access required to execute RULE-OBJ-ACTIVITY DATA-ADMIN-LOOKUPLIST was encountered while performing an obj-save during the creation of a Modal operator ID. This was traced to a difference in how an authentication activity was called, and has been fixed.

SR-B8133 · Issue 277199

Support added for cloning SLA agents

Resolved in Pega Version 7.3

The SLA worker agent was not working as expected based on a prior recommendation to clone agents. The cloned agents are not handling any requests. The original agent is still working, but all 3 clones do not perform any work. 6 nodes, for agents per node, and on each node only the original node is working. Cloned agents were not processing work in production if they were duplicated from SLA agents. In order to support this use, a new feature has been added to agent to allow dequeueing pages queued for another agent. This new configuration setting clones Pega-ProCom to multiple custom rulesets or creates a new agent rule in a custom ruleset with multiple rows for the ServiceLevelEvents agent in that rule. Example:

SR-B8469 · Issue 278141

RTE linkbox input handling corrected for modal windows

Resolved in Pega Version 7.3

In an "inline editable" grid with 'click to edit' selected, clicking on the RTE link inputbox in the modal window caused the grid row to be submitted as if the click took place outside the grid. The gridEventHandler has been updated to correct this.

SR-B8478 · Issue 278805

ExtractSection data transform optimized

Resolved in Pega Version 7.3

The code in pzExtractSectionPostDT and pzExtractSectionPostActivity has been optimized to improve data transform processing time.

SR-B8495 · Issue 279313

SVG image support added

Resolved in Pega Version 7.3

Support has been added for previewing and searching for SVG type images.

SR-B8696 · Issue 279855

Support added for FCM GetNextWork

Resolved in Pega Version 7.3

When using Federated case management (FCM) to get next work, the work object pulled was not assigned to the operator. This was due to the implementation of FCMR not supporting the moving of workbasket assignments to worklist through get next work. To support this use, the following functions now accept extra parameters as last param: FCMRGetNextWork FCMRGetNextWorkItem FCMRProbeNextWorkItem This will enable distinguishing between normal GNW and federated GNW, and it is possible to override any py rule call MoveToWorklist.

SR-B8744 · Issue 279872

OnClick passes parameters to DT from inside a grid

Resolved in Pega Version 7.3

The OnClick event was not passing its parameters to a Data Transform or activity if it was inside a grid due to the property not being generated with its full reference. This has been fixed by modifying pzActionAppendValue to generate the complete property reference instead of just the property name.

SR-B8793 · Issue 278410

Flow warnings show consistently

Resolved in Pega Version 7.3

Due to conflicting handling of temporary pages by two different processes within the Rule-Save function, warnings were only displaying intermittently as flow rules were saved, refreshed, or checked in. To ensure consistent handling, a single internal parameter has been added that will be used for creating/removing temporary pages

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