SR-132732 · Issue 201617
SMA Instance MRU report updated
Resolved in Pega Version 7.1.9
The SMA Advanced / Rule Cache Summary report showed "NA" for pruning, even when the system had been impaired by extensive pruning. The correct data was available under Advanced / Reports / Most Recently Used Caches Report, but the NA results were purposeful: this particular report branch had been incompletely refactored while implementing multitenancy, and the decision had been made to have this report show NA rather than zero because zero was misleading and inaccurate. We apologize for any confusion this may have caused, and the report should now accurately report the expected results.
SR-132809 · Issue 207385
Next run in agent schedule updates after DB access issue
Resolved in Pega Version 7.1.9
It was discovered that if access to the database was interrupted, the Next run in agent schedule was not updating and not being run. This has been fixed by updating AgentQueue.handleProblem() to handle unexpected errors and ensure delayDueToProblem() is invoked always.
SR-133057 · Issue 205137
System updated to better handle multi-node rule resolution
Resolved in Pega Version 7.1.9
In an upgraded multi-node environment, the error 'com.pega.pegarules.pub.database.MultipleRuleVersionException: Rule resolution identified 2 versions of the rule' was sporadically appearing. Once the issue occurred, it would persist and the only way to resolve it was to bounce the server. This was an issue with an instance of one rule being found in one node and not found in other node, and was related to the trigger logic. This should not occur with the current Pega7 version, as trigger logic has been moved into the engine and there is no longer a database trigger to fix. In order to ensure continued smooth trigger resolution, tests have been added that will check for this condition in the updates cache table to ensure that this scenario does not occur again
SR-133561 · Issue 203840
Garbage Collector tool removed from SMA
Resolved in Pega Version 7.1.9
Issues were found when attempting to view Garbage Collector statistics in SMA, and the "Collect" button which should point to the GC log instead gave an error. After investigation, it has been determined that the SMA Garbage Collector Tool no longer meets customer needs: it failed to parse JDK 1.7 GC logs and did not give useful failure information when parsing a JDK 1.6 log. Therefore, the Garbage Collector function has been removed from the system. Instead, third-party analysis tools such as HP Jmeter and IBM Support Assistant are recommended for this purpose.
SR-133756 · Issue 203835
Debugging enhancement added for role of BATCH requestor
Resolved in Pega Version 7.1.9
An enhancement has been added to the system to give more detailed debugging information in the PegaRULES logs if the startup-process detects the following roles : ?PegaRULES:SysAdm4, COB:User1, COB:LEGUser1, COB:CreditUser1, PegaRULES:AutoTest, MS:Restricted, COB:Administrators?. This DEBUG log message has been added to provide information on the role assigned to the requestor type BATCH.
SR-133557 · Issue 202993
Schema URL' field in Parse XML rule now supports Global Resource Settings
Resolved in Pega Version 7.1.9
The 'Schema URL' field in Parse XML rule now supports Global Resource Settings (GRS), and the developer help documentation has been updated to reflect this.
SR-A1536 · Issue 205669
Fixed exception for read-only edit on data page
Resolved in Pega Version 7.1.9
Exceptions were being logged for a data page when edit mode was set as Read Only. This was caused by setIsReadonly in ClipboardPropertyImpl directly using the mPageValue which would be null for ref-type properties. The system has been updated to use getPageValue() instead of mPageValue directly.
SR-A3157 · Issue 207690
Corrected reference matching for relative pagegroup properties
Resolved in Pega Version 7.1.9
During page copy, the references in pagegroup property were becoming corrupted when given as a relative reference. Reference matching has been updated to resolve this.
SR-A3170 · Issue 213298
Stabilized encoding and decoding of Thai characters in imported CSV files
Resolved in Pega Version 7.1.9
While importing CSV files containing Thai characters, the methods of encoding and decoding were different and JVM differences could lead to output from the file being garbled. This has been updated to uniformly ensure the Thai characters will be properly recognized and converted.
SR-A3170 · Issue 212348
Stabilized encoding and decoding of Thai characters in imported CSV files
Resolved in Pega Version 7.1.9
While importing CSV files containing Thai characters, the methods of encoding and decoding were different and JVM differences could lead to output from the file being garbled. This has been updated to uniformly ensure the Thai characters will be properly recognized and converted.