SR-126156 · Issue 190077
Random ID generation changed to use OpenSAML
Resolved in Pega Version 7.1.8
In certain cases, SSO setup with SAML 2.0 failed with the message "Unable to process the SAML WebSSO request: Unable to process SAML2 Authentication". The error was due to the generated ID being sent with a "+" character in it which could not be handled smoothly. To avoid this issue, the system has been changed to use the OpenSAML API instead of using UUID when generating random IDs for all types of WebSSO requests.
SR-D38318 · Issue 519715
Data pages explicitly cleared after QP use
Resolved in Pega Version 8.1.8
The Util Node was showing as Offline in the Search Landing Page, and when Jobs were submitted for execution from other Nodes the message "Detected active run with unreachable nodes" was logged. The util node, configured as a backgroundprocessing node, was running QPs; the queue size for custom QPs is 500 messages /queue items per minute, but investigation showed the requestor level and thread level data pages corresponding to the QP activities were not being cleared after use. This led to high heap memory issues that made the node unreachable, and has been resolved by adding code to explicitly remove the data pages when processing has finished.
SR-118735 · Issue 175180
Addressed ruleset integrations problems using Google Chrome
Resolved in Pega Version 7.1.8
When using Google Chrome and running the Integration > Tools > Rule-From-File wizard, the ruleset version was not displayed and it was not possible to proceed past the screen that requires values for rule name, ruleset, ruleset version and class name. This was due to there not being an input field for RuleSet Version, and the validation of that step in the wizard fails. This issue occurred due to Google Chrome not supporting the use of document.all in the HTML code, leading to an undefined value for the JavaScript. This has been resolved by changes to the HTML to make it browser code independent.
SR-123018 · Issue 183818
Addressed ruleset integrations problems using Google Chrome
Resolved in Pega Version 7.1.8
When using Google Chrome and running the Integration > Tools > Rule-From-File wizard, the ruleset version was not displayed and it was not possible to proceed past the screen that requires values for rule name, ruleset, ruleset version and class name. This was due to there not being an input field for RuleSet Version, and the validation of that step in the wizard fails. This issue occurred due to Google Chrome not supporting the use of document.all in the HTML code, leading to an undefined value for the JavaScript. This has been resolved by changes to the HTML to make it browser code independent.
SR-124298 · Issue 186402
SQL Merge use clarified for custom Tomcat installations
Resolved in Pega Version 7.1.8
Logic was added to ML7 to disable the SQL Merge command in environments that do not support it, but this was failing with an exception trying to parse the Tomcat name/version string if the installation was using a custom version of Tomcat and the string was not in the expected format. To handle this, the logic has been updated to to handle a custom Tomcat Name/Version string that may or may not contain version information. However, please note the following important information: The system will disable Merge if the out-of-the-box Tomcat version is detected where version If the system is using a custom Tomcat instance
SR-127237 · Issue 189891
Time-related RUFs now use operator's time zone
Resolved in Pega Version 7.1.8
Date properties and Time properties were taking their reference from the server's default time zone, which created unexpected behaviors for operators in other time zones using start and end date functions. This has been resolved by updating the time-related RUFs to use the operator's defined time zone
SR-122529 · Issue 184997
Creation and testing corrected for ATOM server connection using Alfresco 4.2
Resolved in Pega Version 7.1.8
When creating a new ATOM Server instance with Alfresco 4.2, an error was logged and shown on the screen. This process worked with Alfresco 4.0. In the process of upgrading openCMIS jars, Atom and SOAP server connectivity tests were also changed to use HTTP, and Atom Server connectivity tests should now work for all versions of Alfresco.
SR-114819 · Issue 175544
Localization added for currency values using commas vs decimal points
Resolved in Pega Version 7.1.8
Excel within PRPC was not properly localizing for the use of decimal and comma as thousand and decimal separators for decimal/double currency property values, a use that is common in non-English installations. The records editor has been changed to support localization for properties of type double and decimal.
SR-124747 · Issue 186549
Added fallback keyinfo handling
Resolved in Pega Version 7.1.8
When a SAML assertion response is received in the authentication activity, an error indicated the KeyInfo was missing in the signature. This was caused by a lack of redundancy in the keyinfo handling that caused an exception when keyinfo was not included in the SAML response. Support has now been added to check the certificate in the truststore where the certificate from IDP metadata would have been imported, and there is an added null check in the debug logs.
SR-126719 · Issue 189646
Added fallback keyinfo handling
Resolved in Pega Version 7.1.8
When a SAML assertion response is received in the authentication activity, an error indicated the KeyInfo was missing in the signature. This was caused by a lack of redundancy in the keyinfo handling that caused an exception when keyinfo was not included in the SAML response. Support has now been added to check the certificate in the trust store where the certificate from IDP metadata would have been imported, and there is an added null check in the debug logs.