SR-131553 · Issue 203114
Passivation handling added to changelist
Resolved in Pega Version 7.1.9
A Rule-Declare-Index defined on a Context page property was intermittently failing to fire. This was traced to a missing changelist following passivation. Changelists were never originally designed to be passivated, but it is possible to passivate requestor or PRThreads which then affected the pages with changelists. The system has now been updated to properly passivate changelists in order to prevent this issue.
SR-131691 · Issue 204727
Improved performance for incorrect password handling
Resolved in Pega Version 7.1.9
When the operator entered the wrong password in the login screen, numerous "Stream Overwritten" alerts appeared the Alert log. There was no workflow problem involved, but the logging indicated that there was an additional unnecessary call being made to Stream Web-Login, and that unneeded call has been removed to improve system performance and remove the error being logged.
SR-131726 · Issue 202769
Fail-over updated to cover server crash scenarios
Resolved in Pega Version 7.1.9
In a testing event, the user session did not properly fail over to another server if the original server was shut down; an error was thrown instead. This was found to be an authentication issue where on node crash, a new requestor was created on the second node and then immediately authenticated as it is SSO. As part of authentication, the mRequiresSpecialProcessingForNodeCrash flag was cleared, meaning the node crash activity was not executed and entire portal was not refreshed. This has been corrected by updating the system to execute crash node activity for SSO cases.
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-A1350 · Issue 205576
Added support for adding custom GuardrailWarning
Resolved in Pega Version 7.1.9
A customer-created custom activity "addGuardrailWarning" with incoming parameter (WarningMessage) of type Rule-Message with the intent that whenever the new activity was called from another activity, the SmartPrompt-enabled parameter would provide a list of Rule-Message instances starting with any defined on the class of the Step Page (or the class of the calling Activity when the Step Page is blank), and then working up the inheritance hierarchy, much like the behavior provided on other activity methods such as the Data Transform parameter of the Page-New method. However, the SmartPrompt for this custom function only showed rule-messages of pyCategory "Error", or "blank" due to lack of support for this custom Guardrail Warning. In order to support this customization, the function alias pxAddGuardrailMessage has been created and this FA can be accessed by a call-function method in activity as 'Add a message to a page using [Name of the Message Rule]'.
SR-A2 · Issue 203635
Updated use and edit of the 'Search for work' rule
Resolved in Pega Version 7.1.9
After upgrade, an out-of-the-box functionality to search for work items by selecting the case status and selecting a particular field to add as filter on that search was not working correctly and the search icon (which gives the list of status window dynamically) was missing. An attempt to perform a private check out of of the rule generated an error and did not allow 'save as' because it was unable to identify a property pyStringType. This issue was traced to a missing property 'pyStringType' in @baseclass, and this has been added.