SR-128179 · Issue 197764
Pagination added for ruleset versions ruleform
Resolved in Pega Version 7.1.8
Opening the Developer ruleform to view a ruleset in an environment containing multiple rulesets with thousands of versions presented performance issues where rendering took multiple minutes and scrolling was impossible due to the very large file size. To improve performance, pagination has been enabled for the ruleset versions section.
SR-128192 · Issue 193639
Libraries updated to reflect ruleset versions
Resolved in Pega Version 7.1.8
New ruleset versions were not showing in the Library. This was caused by improper version population: when a version-resolved rule (such as property/section) was created, a a data page would hold the default ruleset version. When a library (which is non version-resolved) was created, the default ruleset version was not reset and it became associated to the library rule. A fix has been added to reset the value of pyRuleSetVersion.
SR-128206 · Issue 192572
Added null check for RD column containing a function
Resolved in Pega Version 7.1.8
When running a report definition with a column that has a function, it showed the error "illegal zero-length identifier". This was due to the alias name for the Rule-Alias-Function with return type 'True or False' being empty in the pxSQLStatementPost function, and a check has been added to handle this.
SR-128220 · Issue 195539
Screen layout options now visible before saving a new harness
Resolved in Pega Version 7.1.8
When using a screenlayout in a harness, the options for defining the properties were not displayed. This was due to changes made to replace panel sets with screen layouts in this area, and was only an issue if the harness had not been saved yet. In order to facilitate development, these options will now also be present before saving.
SR-128228 · Issue 193947
Smoothed locking for cloud team logins
Resolved in Pega Version 7.1.8
In a large cloud team, a high number of simultaneous logins caused a requestor lock exception that required a system restart to resolve. This was caused by threads deadlocking while attempting to acquire a common resource during compilation. To resolve this, the locking has been modified to sync requests in order to ease congestion.
SR-128320 · Issue 193581
Updated chart export handling for Safari
Resolved in Pega Version 7.1.8
The charts in reports are getting disappeared on click of When using the Safari browser, clicking on Export to Excel/Export to PDF caused the charts in reports to disappear. This was traced to the form target being blanked in the browser handling, and a browser check has been added to invoke special handling for Safari..
SR-128380 · Issue 194162
Refined Excel specifications import
Resolved in Pega Version 7.1.8
Importing specifications from Excel was registering unexpected characters. This was caused by the system mistakenly importing rPh tags from the "sharedStrings.xml" in the "xl" folder, and has been corrected.
SR-128397 · Issue 193116
reRunReport modified to use fully qualified RUF from Procomm ruleset
Resolved in Pega Version 7.1.8
In some cases, re-running a report would fail due to an inability to pick the correct instance of the Rule-Utility-Function getPropertyValue from two rulesets with the same parameters (in the KYC ruleset and the Procomm ruleset). This has been resolved by modifying the reRunreport activity to use the fully qualified RUF from the PegaProcom ruleset.
SR-128416 · Issue 193685
Updated ImportTranslations activity to fully display all errors
Resolved in Pega Version 7.1.8
While importing the translated strings into the application wizard displays, errors on the last line were being overwritten with new errors rather than adding new rows. The pzImportTranslations activity has been updated to resolve this unexpected behavior.
SR-128495 · Issue 196402
Repeat grid pagination scroll bar improved
Resolved in Pega Version 7.1.8
A repeat grid with progressive pagination format (with a page size set) that had its container collapsed during load was showing its scrollbar when the number of rows was at the minimum number (i.e., when the page size is set to 5, the expectation is that the scrollbar shows only when there are 6 or more rows. But it was found that the scrollbar shows up even if there is only 5 rows). This has been corrected in the autoAdjustProgressiveGridHeight() API.