SR-127091 · Issue 193209
Forward chaining commit error resolved
Resolved in Pega Version 7.1.8
A sporadic pyCommitError was observed when performing 'Action' during a 'Phone call' interaction for a specific user. During forward chaining, a malformed variable change that occurs when a page copy happens on a embedded page of a work page is recreated in order to not corrupt the fragment collection cache. Previously, this was done only while evaluating the declare expressions. The system has now been updated to do the same during evaluation of other declarative flavors during forward chaining.
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-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-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-128670 · Issue 194884
Fixed removal of uncommitted hotfixes
Resolved in Pega Version 7.1.8
If a hotfix was installed in an environment but not committed, attempts to un-install the hotfix via System -> Tools -> Update Manager -> Uncommitted Hot fixes failed with the error "The following hotfixes could not be rolled back due to an exception". This was caused by the system not being able to switch threads context from the clipboard viewer, and has been corrected.
SR-128676 · Issue 194416
Existing BIX pr_extract_time tables preserved during install
Resolved in Pega Version 7.1.8
In older versions of the software, the pr_extract_time table was created by the core PRPC installation. This table creation was recently moved to the installation of BIX, but the system was improperly dropping this table from the data schema if it already existed during installation. This has been corrected.
SR-128861 · Issue 195852
Corrected temp directory for upgrade file extraction
Resolved in Pega Version 7.1.8
On upgrade, the extractedfiles directory was being written to the java.io.tmpdir location instead of to the Web-tier temporary path, i.e.. the temp location of the application server. This was incorrect, and the web temp directory is now set as the default temp directory in PRPC.
SR-128945 · Issue 197784
Ensured compliance for localization checkbox on RadioButtons control label
Resolved in Pega Version 7.1.8
In RadioButtons control, it was seen that a label was localized without regard to the status of the localization checkbox checked at the section level. This has been fixed.