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-C77633 · Issue 415454

Report definition rules correctly revalidate and save in Bulk wizard

Resolved in Pega Version 8.2

Report definition rules were failing on re-validate and save from the Bulk Actions wizard. This was caused by pzCopyPySource attempting to set a blank value, and has been corrected.

SR-C70867 · Issue 414702

Resolved focus for new IE windows in Citrix environment

Resolved in Pega Version 8.2

When opening a new IE window in the Citrix environoment, the window would open in the foreground and then immediately shift to the background. Investigation showed that when a menubar item was clicked, there was a call to show submenus in a settimeout of ZERO which implicitly did a focus on the menu item. Though the focus on the menu item happens after the window.open (action) is called, for in-house cases the focus occurs before the window is completely opened. However in this case, this focus was delayed and the new window was sent to the background. To correct this, the system has been updated so it will not perform focus on the menu item if the document itself is not in focus.

SR-C69441 · Issue 415966

Copy/Merge Wizard ProcessRequest will create new rule instead of modifying the old

Resolved in Pega Version 8.2

When using the Copy/Merge wizard to move the rules from one ruleset to another with the "Delete Source RuleSet(s) upon completion of merge" option set to YES, the SECTION rules were still being referred even though the target ruleset was not part of the application stack. In the Tracer, it could be seen that the rule appears in the source ruleset version even though the ruleset did not exist, and attempting to open the rule from tracer or from Live UI caused it to open in the Target ruleset version (which was not part of application). This was traced to the system not updating the cache, leading to RULE-OBJ-ACTIVITY PEGAACCEL-MANAGEMENT-REFACTOR-RULESET PROCESSREQUEST applying an incorrect strategy when updating the rule and rulesets. Because the original rule was never invalidated, its shortcut and entry remained and any references to it weren't updated. To correct this issue in a comprehensive way, the ProcessRequest has been modified to create a new rule instead of modifying the old rule, and pxCreateDateTime will be added to the rulepage before saving.

SR-C71053 · Issue 413208

Added handling for defer-loaded dynamic layout inside a flowaction grid

Resolved in Pega Version 8.2

When using a grid configured to show the details in expandable rows and the inner grid was a work bound grid, trying to expand the rows only showed the "Loading ..." message and never completed. This was traced to a missing use case for having a defer-loaded Dynamic layout which wraps the grid inside a flowaction embeddedpane grid, and has been corrected.

SR-C71070 · Issue 417206

UI-Toolkit updated to resolve issue with fields overlap in dynamic layout collapse header

Resolved in Pega Version 8.2

The UI-Toolkit has been updated to resolve an issue with Dynamic layout where using a Collapsible Header that has multiple fields to be displayed resulted in the fields overlapping or being mis-aligned.

SR-C74047 · Issue 416352

Automatic Cloud Terminations updated with retry logic and exception handling for nodes being disconnected while in use

Resolved in Pega Version 8.2

Agents were being disabled when a node was about to be shut down and the lock operation timed out. This was traced to an issue where the Hazelcast operation timed out trying to communicate with a node that had not yet dropped out of the cluster but did shortly after, and was due to the refactored code around delegating to a cluster component missing a lock method. In order to ensure the cluster component handles such exceptions gracefully, the lock operation now contains retry logic along with exception handling that will return 'false' instead of raising an exception.

SR-C76394 · Issue 417568

Support added for parameterized localized strings for headers

Resolved in Pega Version 8.2

Support has been added for parameterized localized strings in headers by way of getLocalizedTextForParameterizedString. This can be used for the field values of LABEL and header text.

SR-C78352 · Issue 417617

Transform on an onclick event refresh added to DT

Resolved in Pega Version 8.2

When calling the refresh method, the transform on a onclick event refresh was not invoked. Support for this refreshSection action has been added for running data transform and activity.

SR-C78362 · Issue 415981

Preprocessing added to GET assignments and cases

Resolved in Pega Version 8.2

When the /assignments/{ID}/actions/{actionID} API was called, the result of the flow action did not include either the data transform nor the activity from the preprocessing section. The system has now been updated to run preprocessing for GET /assignments/{ID}/actions/{ID} and GET /cases/{ID}/actions/{ID}.

SR-C77100 · Issue 417036

Flow actions with validation errors are correctly populated to embedded page

Resolved in Pega Version 8.2

After upgrade, a pyFlowData page was not populating an embedded pyFlowActionsInError page with the list of flow actions with validation errors. This led to the AddRuntimeInfo activity (called from step 8 of GetFlowData activity) to fail in setting the correct step status (pyStatus) as “error”(under pySteps embeded pages of pyFlowData page). Any additional logic based on this status value then failed because of the incorrect status. This was traced to a missing call to the researchPropertyReference API in pzGetActiveValue RUF.changes, and has been corrected.

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