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-D51554 · Issue 514064

Local UUID cache will be updated when merge event is detected

Resolved in Pega Version 8.1.7

Cluster-related issues were seen in multiple production clusters. For some nodes in the cluster the Cluster Management screen showed all expected nodes with valid Node IDs displayed, and on other nodes the Cluster Management screen showed the node ID of itself, SERVER@localhost:5701. On an impacted node displaying the wrong ID, the Node Information landing page did not work and displayed the error "Unable to execute job on ." Multiple advanced agents running on nodes in the affected clusters, both with correct and incorrect IDs, also failed with a similar error "Unable to execute job on <node's job id>". This was traced to a merge performed after a split brain. To resolve this, the code has been updated to handle merge events: when the node UUID is changed as part of a split brain recovery, the local UUID cache will be updated when the merge event is detected.

SR-D20423 · Issue 503447

Improved upgrade handling for tables using classes with property references

Resolved in Pega Version 8.1.7

After upgrade, some page property values were blank and exposed database columns did not contain the values. Investigation showed that the reference properties did not have context and hence column population was not able to determine their value. To resolve this, instead of doing column population for all the columns, the system will identify classes that have property references and that are being optimized as part of upgrade process and maintain a list of specific columns to update.

SR-D29485 · Issue 503514

Enhancement added to modify URL encryption for load testing

Resolved in Pega Version 8.1.7

An enhancement has been added which allows conditionally modifying URL encryption for load testing. This uses the flag crypto/useportablecipherforurlencryption: if true, a portable hardcoded key is used to encrypt the URLs and if false, a dynamically generated key per thread/requestor is used to encrypt the URL.

SR-D52969 · Issue 514705

Column population honors thread count of 1

Resolved in Pega Version 8.1.7

The thread count parameter in the column population activity was not being honored, causing repeated deadlocks when trying to populate columns. Investigation showed that the ExposeCols process did not honor the thread count when it was 1 (the default is 4), and this has been fixed by adding the necessary code so that if the thread count is 1, it will not run in multhreaded mode.

SR-D16543 · Issue 487946

Thread cleanup improved for application switching to resolve skin issue

Resolved in Pega Version 8.1.7

After opening a Case from the HR application and then switching to another application to open another case, the Review Harness skin control was not loading correctly. This was traced to a thread cleanup issue relating to the Portal: on application switch, the system should clean up all threads created on the current application before switching to new application, but in this case thread cleanup was not happening as expected due to conflicts in the unload event handling. This has been corrected.

SR-D40938 · Issue 509687

Free form layout controls will be converted to dynamic layout

Resolved in Pega Version 8.1.7

After upgrade, a a pzActionDropdown control that was inside a pyActionDropdownSection was not visible anymore. Using the pzActionDropdown control directly worked as expected. Investigation showed that pyActionDropdownSection was using Freeform layout instead of the upgraded Dynamic Layout, and that the custom control was failing to generate the markup whenever drag/copy-paste was used for the control in any layout. To resolve this, the system has been updated so it will remove the control from a free form layout and use dynamic layout instead.

SR-D48881 · Issue 514602

Corrected alignment of column header and content when fixed header is used

Resolved in Pega Version 8.1.7

The tables header column was misaligned with the context columns when a fixed header was used. This has been resolved by correcting the code calculating the width of the header cells.

SR-D23174 · Issue 499569

Check logic added for change in datetime

Resolved in Pega Version 8.1.7

After selecting a valid date in the calendar UI, clicking outside of the DateTime control caused the date to disappear when using the Microsoft Internet Explorer browser. Investigation showed that the order of events execution is different in Microsoft Internet Explorer and Google Chrome, so that by the time the getReadOnlyFormatting method was called, the data-changed attribute had already been updated to 'false'. This caused the read-only formatting to not be applied so the data-display-value was considered to be empty. To resolve this, a check has been added to better detect the change so that read-only formatting gets applied.

SR-D31599 · Issue 503201

Table layout filter by format works for empty value

Resolved in Pega Version 8.1.7

If a DateTime property with empty values in a table layout grid was filtered by format, no result was returned even though the grid had the Records for empty DateTime property. This was traced to null value filtering being done with empty values instead of a formatted null value, a difference that could produce different results depending on the control. To resolve this, the activity has been updated to support null values filtering.

SR-D32525 · Issue 505469

Dirty check added to offer save/discard changes when closing tab

Resolved in Pega Version 8.1.7

With the out-of-the-box section enabled, performing a change in the form (changing a text value, selecting a option in a dropdown, etc.) and closing the case generated an unexpected alert indicating that the case was changed and the modifications were lost. This differs from the previous behavior of showing the section pyDirtyCheckConfirm which offered the opportunity to save the work. This was a missed use case and has been resolved by updating the system to perform a check for the dirty state when closing the interaction and show a modal dialog asking the user to choose either save/discard if dirty.

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