SR-125539 · Issue 188736
Property Optimization Wizard working for Page level properties
Resolved in Pega Version 7.1.8
The Property Optimization Wizard was not working on Page level properties in a PageList due to due to the 'PropertyPath' Param in the displayResults activity having "()" characters that did not exist in previous versions. To resolve this, the "()" are stripped off in the Rule-Declare-Index name.
SR-125539 · Issue 188739
Property Optimization Wizard working for Page level properties
Resolved in Pega Version 7.1.8
The Property Optimization Wizard was not working on Page level properties in a PageList due to due to the 'PropertyPath' Param in the displayResults activity having "()" characters that did not exist in previous versions. To resolve this, the "()" are stripped off in the Rule-Declare-Index name.
SR-126177 · Issue 189199
Major ruleset skim logic updated
Resolved in Pega Version 7.1.8
When skimming a ruleset to a new major version, property rules (Rule-Obj-Property) which were available in lower rulesets but withdrawn in a higher ruleset version were skimmed to the new ruleset with their status as Available. This was contrary to expected behavior, as these rules should be ignored and not added to new ruleset. This has been addressed by correcting the logic in the special handling for Rule-Obj-Property types during skimming.
SR-126439 · Issue 189008
WebSphere security updated for class name
Resolved in Pega Version 7.1.8
IBM issued a bug alert for WebSphere that affected the prsysmgmt application. To meet the security criteria outlined, the serveServletsByClassnameEnabled attributes have been changed to false in prjmxui/WEB-INF/ibm-web-ext.xmi file.
SR-126448 · Issue 189959
Special character handling added to 'pzupgraderulemessages'
Resolved in Pega Version 7.1.8
The 'pzupgraderulemessages' activity was introduced to recalculate the pzinskeys of Rule-Message instances. These instances were migrated to a new table and the property, and pyclass name was made part of the key. Running this activity was made mandatory as part of upgrade/update process effective v 7.1.7. This activity selects each rule-message instance using its pzinskey and checks if it needs to be recalculated. To fetch the Rule-Message record, a plain SQL is used which did not escape any special characters in the pzinskey (\t, etc.).However, this lack of character escape was problematic for some customers who had existing rules utilizing special characters, so the activity has been updated to use a prepared statement which takes care of escaping characters in place of the generated plain SQL.
SR-126530 · Issue 188522
Enhanced error handling for exceptions generated by import
Resolved in Pega Version 7.1.8
After upgrading to a single schema on Oracle 11.2 database, the system started up showed the login page, but once logged in a blank Screen/UI would be displayed and errors were logged indicating "Failed to resolve rule file". The rule file varies depending on the content source. This issue was caused by exceptions not being handled properly by import, and has been resolved by modifying the runWithRequester method (importImpl.java) to check for Exception as a return object object from the method invocation, and propagating the exception if one is returned.
SR-126530 · Issue 193829
Enhanced error handling for exceptions generated by import
Resolved in Pega Version 7.1.8
After upgrading to a single schema on Oracle 11.2 database, the system started up showed the login page, but once logged in a blank Screen/UI would be displayed and errors were logged indicating "Failed to resolve rule file". The rule file varies depending on the content source. This issue was caused by exceptions not being handled properly by import, and has been resolved by modifying the runWithRequester method (importImpl.java) to check for Exception as a return object object from the method invocation, and propagating the exception if one is returned.
SR-126719 · Issue 177348
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 178793
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-126901 · Issue 190595
Handling added for temp install directory names with spaces
Resolved in Pega Version 7.1.8
If the install directory name contained spaces, the install failed at the point where the directory was used as a script parameter due to the parsing handling the name up to the space as one parameter and after the space as another parameter. In order to resolve this, handling has been added to allow temp directory names with spaces.