SR-C58890 · Issue 398423
Merge Wizard errors fixed, and created rules will use the highest ruleset version available
Resolved in Pega Version 8.2
Code errors in the Merge Wizard that were causing Null Pointer Exception errors have been fixed, In addition, branch rule sets created through this wizard did not have the 'Application validation' option and rule set pre-requisite filled automatically; the system has been updated so the version prerequisite will be the highest existing ruleset version in the ruleset.
SR-C74047 · Issue 416352
Automatic Cloud Terminations updated with retry logic and exception handling for nodes being disconnected while in use
Resolved in Pega Version 8.2
Agents were being disabled when a node was about to be shut down and the lock operation timed out. This was traced to an issue where the Hazelcast operation timed out trying to communicate with a node that had not yet dropped out of the cluster but did shortly after, and was due to the refactored code around delegating to a cluster component missing a lock method. In order to ensure the cluster component handles such exceptions gracefully, the lock operation now contains retry logic along with exception handling that will return 'false' instead of raising an exception.
SR-C53056 · Issue 398514
Bulk delete updated and NPE handling improved to resolve deadlock when loading data flow landing page
Resolved in Pega Version 8.2
A large number of data flow objects on the data flow landing page were making the system unresponsive, and bulk delete activity would sometimes fail on a null pointer exception when progress could not be retrieved. To resolve this, the bulk delete activity provided in [Data-Decision-Service] pyDeleteByStatusAndTime has been modified to be more flexible by allowing deletions based only a date or a status, and the documentation for the activity itself has been improved. Additional handling was added for a potential null pointer exception, and the activity will continue trying to delete other runs if a null pointer exception does occur. The system will not load a data flow run object anymore (which can cause issues when rules do not exist), and will instead load the run progress directly from the database.
INC-198765 · Issue 696686
Public URL will be appended with "/" if it is not present
Resolved in Pega Version 8.7.1
When using the Worklink Correspondence Fragment rule with authentication service type "prweb/PRAuth/sso", the returned URL did not contain the needed "/" at the end of public link. The "/" was present when using the legacy authentication service "prweb/sso". This has been resolved by updating the system to include a "/" at the end of a public URL if one is not present.
SR-C50324 · Issue 393499
Synchronized block method added to load keystore set with RUF
Resolved in Pega Version 8.2
A recent enhancement allows for the SAML auth service to use a reference to an external file for the signing certificate keystore. When the keystore had the password set using a Rule-Utility-Function, rather than being static, there were intermittent login fails with the error "unable to process SAML WebSSO request1" on the screen, and the RULES logs contained thousands of entries of an error indicating "Password is wrong". It was sometimes possible to log in by starting a new browser sessions and trying again. This was an issue with the PasswordHash property being changed from a static to a non-static field: it was not thread safe, though each object got its own copy of the instance, because if two or more threads call the setPasswordHash() method on the same object, all of these threads tried to simultaneously update the passwordHash instance variable and incorrect results were seen. To correct this, the system will use a synchronized block when loading the entries into cache in the getKey() method - Caller function of KeystoreCacheImpl.java.
INC-173098 · Issue 694090
Signature map updated for fetching keys
Resolved in Pega Version 8.7.1
MFA login worked with SAML 2.0 when the certificate was disabled but failed when the certificate was enabled in Auth Service. The error " "Signature algorithm is null" appeared. This has been resolved by updating the signature map to ignore case sensitivity while fetching keys.
SR-C46537 · Issue 395372
Code added to format location header for redirect response in IE
Resolved in Pega Version 8.2
When using Internet Explorer, authentication was working but the portal did not load. This was traced to IE mandating the presence of a location header in the response: an HTTP 303 "See Other Response" was being returned along with the initial portal HTML payload, but recent modifications to SAML 2.0 to use the PRAuth Servlet were missing this specific redirect case. To resolve this, generic code has been inserted that adds the location header in all redirect cases.
INC-200218 · Issue 692431
Added handling for calling truncate with external Cassandra
Resolved in Pega Version 8.7.1
A JMX exception was generated when using external Cassandra. This was traced to the combination of calling truncate and using external Cassandra for DDS, and has been resolved by adding a 'do not execute' consistency check during a truncate operation when using external Cassandra.
INC-184040 · Issue 688256
Improved accessibility for Disclosable Documents/attach files/auto selection dropdowns
Resolved in Pega Version 8.7.1
When using Dragon for accessibility, issues were seen when trying to select different options in the dropdowns related to attaching multiple files. This was caused by the legacy grids being used not supporting this type of accessibility functionality, and has been resolved by updating pzAttachFileDDFileList to use an optimized table instead.
SR-A23050 · Issue 244774
Rule generation updated to handle related JSONs
Resolved in Pega Version 7.2.1
The system was failing to parse inbound JSONs when the corresponding Pega Data Model was generated using the same JSON, and was unable to use valuelist or pagelist properties for generating JSON to pass to connect-Rest Method. This generation and runtime of rest connector was failing when the same name property existed in multiple places with different modes and same levels. To support this use, the rule generation has been updated to correctly populate the qualifier name along with modified run time code to support mapping when same properties are there in the same class.