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-128433 · Issue 194694
Added template to handle certificate needed by Word MacroManager
Resolved in Pega Version 7.1.8
Because the Word macrocode must be signed with a current certificate, a Signed and timestamped template has been added.
SR-128475 · Issue 194266
DB Trigger logic refactored for better vw table syncing
Resolved in Pega Version 7.1.8
There are many times in customer environments where for whatever reason the database triggers are disabled for a period of time and thus the vw table gets out of sync. Typically in that case the triggers are reenabled and a statement like "update pr4_rule_file set pzinskey=pzinskey" is run to get the vw table populated correctly. However, if the system was being upgraded the statement would update an existing row in the vw table but it would not add any missing rows to the vw table during migration. To ensure that all rows are handled correctly, trigger logic has been completely refactored for 7.1.8.
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.
SR-128580 · Issue 199345
Localization added for Audit screen
Resolved in Pega Version 7.1.8
Localization was missing from the 'Complete Task' section of the Audit screen. This has been added.
SR-128620 · Issue 193739
MapCases error resolved with blank page check
Resolved in Pega Version 7.1.8
The MapCases function was generating sporadic errors at a Wait Shape or after Updatestatus that required a logout/login before it was possible to proceed with the Case. MapCases runs tools.findPageByHandle(coverinskey) which can lead to an empty page being returned by the engine if one exists, leading to this error; a blank page check has been added that will then use the default work page if the cover key is empty.
SR-128634 · Issue 195936
Enhanced authentication setting carryover
Resolved in Pega Version 7.1.8
An issue was found with calling out-of-the-box authenticated activities from unauthenticated service activities. For example, when the declare page reload was triggered by a SOAP request (e.g. soap request creates new work which refers to the declare page), the report definition failed with an error saying that the requestor was not authorized to execute pxRetrieveReportData. This happened even though the SOAP Service Package and data page load activity had been set up to not require authentication. This authentication conflict was caused by the rule resolution disregarding the initial setting skipping authentication when it encountered the authentication requirement for the pxRetrieveReportData activity. This has been resolved by setting the authentication requirement to be applied to all rule execution in the same requestor.
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.