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-128423 · Issue 194206

RD filter caption localized

Resolved in Pega Version 7.1.8

In report definition, expanding the filter link showed the caption of the filter icon was not localized. This has been corrected by creating a new control and applying it to pyFilterLabel in pzEditSingleFilter.

SR-129062 · Issue 194086

App Explorer enhancement sets number of properties displayed

Resolved in Pega Version 7.1.8

If there were a large number of properties in a navigation panel of App Explorer, only a few properties were shown and a link displayed 'Show all results'. It was then not possible to optimize a property inside a page list in Work Class as it was displayed under new tab when 'Show all results' was clicked. This was found to be an issue with the behavior of Property Optimization wizard being different when it is launched from App Explorer menu than from when it is launched from RuleForm-->Actions menu. The system now provides an extension point for clients to increase the number of properties that appear in the App explorer. The default is 100, with a max cap of 10000.

SR-129062 · Issue 195029

App Explorer enhancement sets number of properties displayed

Resolved in Pega Version 7.1.8

If there were a large number of properties in a navigation panel of App Explorer, only a few properties were shown and a link displayed 'Show all results'. It was then not possible to optimize a property inside a page list in Work Class as it was displayed under new tab when 'Show all results' was clicked. This was found to be an issue with the behavior of Property Optimization wizard being different when it is launched from App Explorer menu than from when it is launched from RuleForm-->Actions menu. The system now provides an extension point for clients to increase the number of properties that appear in the App explorer. The default is 100, with a max cap of 10000.

SR-131985 · Issue 201549

Sorting now working with filtering and pagination for RD

Resolved in Pega Version 7.1.8

Using filtering and pagination on Report Definition and then sorting on one of the subpages caused the error "no results found". This was an issue with the page index not being reset to 1 on apply of modal dialogue, and has been corrected.

SR-131985 · Issue 195991

Sorting now working with filtering and pagination for RD

Resolved in Pega Version 7.1.8

Using filtering and pagination on Report Definition and then sorting on one of the subpages caused the error "no results found". This was an issue with the page index not being reset to 1 on apply of modal dialogue, and has been corrected.

SR-129291 · Issue 201471

Added ability to configure node cluster timeouts

Resolved in Pega Version 7.1.8

If a cluster has many nodes, all nodes starting at the same time ended up contending for lock and throwing an exception if they timed out. When the cluster starts, none of the nodes have yet registered their cluster address in pr_sys_statusnodes. There is code that guards against a race condition and includes locking with a timeout controlled by the waitTime (set to 2000ms) and the number of attempts (set to 30) for a total of 1 minute. However, a large number of nodes contending for this lock could exceed these limits. In order to avoid this, the timeout for the lock during check cluster consistency is now configurable using "cluster/consistency/lockattemptdelayms" and "cluster/consistency/maxlockattempts". Additional tuning on this locking is anticipated to be included in ML9.

SR-129291 · Issue 201670

Added ability to configure node cluster timeouts

Resolved in Pega Version 7.1.8

If a cluster has many nodes, all nodes starting at the same time ended up contending for lock and throwing an exception if they timed out. When the cluster starts, none of the nodes have yet registered their cluster address in pr_sys_statusnodes. There is code that guards against a race condition and includes locking with a timeout controlled by the waitTime (set to 2000ms) and the number of attempts (set to 30) for a total of 1 minute. However, a large number of nodes contending for this lock could exceed these limits. In order to avoid this, the timeout for the lock during check cluster consistency is now configurable using "cluster/consistency/lockattemptdelayms" and "cluster/consistency/maxlockattempts". Additional tuning on this locking is anticipated to be included in ML9.

SR-126787 · Issue 194580

MultiSelectList details propagated correctly

Resolved in Pega Version 7.1.8

MultiSelectList details were getting saved for the second row with the same values given for the first row. This was an error with the "MultiSelectList" control, and the code has been updated in the MultiSelectList.java file.

SR-126799 · Issue 192968

Grid action events carried over after upgrade

Resolved in Pega Version 7.1.8

After upgrade, the actions configured for a grid that had been multiple click actions became split across multiple action sets - click, enter, up key, and down key. This was an issue with already configured actions not being copied correctly from "pyEditBehavior" to "pyActionSets", and has been corrected.

SR-126852 · Issue 196797

Handling added for click parameters containing HTML to open rule with magnifying icon

Resolved in Pega Version 7.1.8

If a parameter contained HTML characters, it was not possible to open any rule using the magnifying glass icon from next to a field. This behavior was related to XSS security catching the HTML, and has been resolved by sending the requested parameter in post body.

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