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-128285 · Issue 193082
Added handling for column size mismatch on Oracle import
Resolved in Pega Version 7.1.8
When upgrading versions of CMF, errors were generated when importing the Pega jar file. The exported schema has pyAccessibility and pyBrowserSupportLevel datatypes as "integer" with size 10, but on the target Oracle database the same column was defined as Number with default precision and scale (0, -127). While importing, the logic checks for column compatibility and was generating an alter statement based on this scale mismatch. This has been resolved by modifying the system to detect that the metadata is returning the new style of NUMBER column metadata handling it correctly.
SR-128296 · Issue 197865
Modified SOAP envelope activity to handle Axiom bug
Resolved in Pega Version 7.1.8
The version of InvokeAxis2 provided in updates was encountering a bug with Axiom's implementation for adding OMNodes and not all header elements were being mapped to their SOAP request. To resolve this, the pzAddCustomeHeaderstoSOAPEnvelope activity has been updated to add a line of code to remove a node from its child iterator once it is added.
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-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.