SR-130038 · Issue 199608
Localization added for RD label "No matching data was found"
Resolved in Pega Version 7.1.8
The Report Definition label "No matching data was found" was not being localized. This has been corrected by adding localization for the ValidValueList and AvailableValueList listviews.
SR-129382 · Issue 197003
Display corrected for tabs within a tabbed repeat
Resolved in Pega Version 7.1.8
All tabs within a tabbed repeat were not displayed on the screen: depending on the screen resolution, only a few tabs were displayed in the available screen area with the rest hidden. This was found to be an issue with the CSS on the UL tag, and has been fixed.
SR-129382 · Issue 199747
Display corrected for tabs within a tabbed repeat
Resolved in Pega Version 7.1.8
All tabs within a tabbed repeat were not displayed on the screen: depending on the screen resolution, only a few tabs were displayed in the available screen area with the rest hidden. This was found to be an issue with the CSS on the UL tag, and has been fixed.
SR-128423 · Issue 193544
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-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.