SR-124242 · Issue 186908
Resolved deletions issues for tables mapped to shared classes
Resolved in Pega Version 7.1.8
When a class in a tenant was mapped to an external table and the tenant was deleted, the tenant deletion caused the external table to be dropped/deleted as well even though there was a class in the shared layer that was mapped to the same external table. To correct this, tables mapped to shared classes are not deleted during tenant deletion if there is a tenant class mapped to the same table.
SR-124477 · Issue 187138
Logic updated for Ruleset Refactor - Merging Ruleset
Resolved in Pega Version 7.1.8
When using the rule set refactor wizard to merge the rule set from lower version to higher version, the wizard did not show the rules in the source rule set on the second screen (Rules Impacted are "0") which had a number of rule conflicts. In addition, the error "StringIndexOutOfBoundsException" was logged. This was caused by the RuleSetMaintImpl buildRuleSetInventory method not filtering out data instances correctly, causing errors when trying to validate a Data instance as a rule. This has been corrected.
SR-125313 · Issue 188224
Documentation updated regarding Update Wizard avoiding deadlocks
Resolved in Pega Version 7.1.8
Following migration, running the Update Wizard tool (Designer Studio -> System -> Upgrade -> Update Existing Applications) caused deadlock errors. This was actually an error/omission in product documentation: the connection property 'webSphereDefaultIsolationLevel' must be set in the datasource prior to running the wizard, and this has been noted.
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.