SR-123260 · Issue 184319
Resolved error with Declare Index rule validation
Resolved in Pega Version 7.1.8
An error occurred when trying to save a Declare Index rule with a source page context of .Page.PageList(). This was caused by a resolution error, and has been corrected.
SR-123292 · Issue 188135
Property Optimization Wizard working for Page level properties
Resolved in Pega Version 7.1.8
The Property Optimization Wizard was not working on Page level properties in a PageList due to due to the 'PropertyPath' Param in the displayResults activity having "()" characters that did not exist in previous versions. To resolve this, the "()" are stripped off in the Rule-Declare-Index name.
SR-123302 · Issue 186407
Row alignment corrected for tree grids in repeating tabs
Resolved in Pega Version 7.1.8
When a tree grid layout was included inside a repeat tab layout, the rows were not rendered with the correct alignment. This was due to a fixed row height, and the rendering will now use 'auto'.
SR-123303 · Issue 185053
Corrected Case match rule reporting
Resolved in Pega Version 7.1.8
The Case match rule was not reporting results that were greater than the cut off score. This has been corrected by changing the rule RunDuplicateCasesReport to check on InsKey instead of pyID as InsKey is available for all pages of different classes where pyID is not.
SR-123303 · Issue 176110
Corrected Case match rule reporting
Resolved in Pega Version 7.1.8
The Case match rule was not reporting results that were greater than the cut off score. This has been corrected by changing the rule RunDuplicateCasesReport to check on InsKey instead of pyID as InsKey is available for all pages of different classes where pyID is not.
SR-123313 · Issue 185096
Drilldowns fixed for reports containing text values
Resolved in Pega Version 7.1.8
In Summary view reports, Onclick functionality to open the drilldown report is not working for the non numeric values. This was an issue with the SummaryViewBodyTag.java not properly handling quotes around database values, and the code has been modified.
SR-123330 · Issue 188222
Resolved exceptions generated by empty property values
Resolved in Pega Version 7.1.8
Empty values passed to the java object were generating the exception "ProjectName.value is blank and the jar file expecting a value". This was an issue with a new code generation strategy on property set where the empty value set on a java property was not setting it on the wrapper. This has been corrected.
SR-123342 · Issue 186178
Smoothed use of Row Repeat with a Repeating Grid that shares references
Resolved in Pega Version 7.1.8
Issues were found with the display of Row Repeat. It was not displayed when a section contained a repeating grid and row repeat layout that had the same pagegroup property reference, and in other cases was displayed improperly after taking the wrong class for a 'when' condition. The failure to display was due to the active page being the last page of the page group as set by Repeat Grid. The RepeatGrid layout generation was changed beginning in v6.3 onwards, and now uses a method-based engine. However, the RowRepeat layout has been deprecated and therefore still uses the previous generation method. This difference creates a conflict when the RowRepeat kicks off in the same stream generation. Furthermore, this issue arises only when the two layouts bound to same PageGroup property source, and not with a Pagelist property. To resolve this, the system now resets the activePage to that of the primary page in case of page group data source in the Repeat Grid generation so that the Row Repeat gets the proper active page for its generation. The issue with displaying when it should not has been resolved by retaining the existing business logic wherever the section rule with body visible when condition is used in a repeating layout.
SR-123344 · Issue 185832
DeleteOrphanStaticContent activity modified to prevent CSS errors
Resolved in Pega Version 7.1.8
The DeleteOrphanStaticContent is used to delete any un-used assembled static contents, but it was sometimes deleting CSS files that were still in use by the system, causing 404 errors. This activity has been changed to use use the node statue query in order to ensure it clears items correctly.
SR-123344 · Issue 191091
DeleteOrphanStaticContent activity modified to prevent CSS errors
Resolved in Pega Version 7.1.8
The DeleteOrphanStaticContent is used to delete any un-used assembled static contents, but it was sometimes deleting CSS files that were still in use by the system, causing 404 errors. This activity has been changed to use use the node statue query in order to ensure it clears items correctly.