SR-123292 · Issue 188135
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-123628 · Issue 184174
Control inserted for determining Elastic Search (ES) index building
Resolved in Pega Version 7.1.8
As Elastic Search (ES) indexing can take significant time and may cause a temporary performance problem, an enhancement has been added to control whether or not indexes are built during an upgrade. The option also exists to start the build at a later time if it is not performed during upgrade.
SR-123636 · Issue 184161
Trojan horse protection auto-enabled
Resolved in Pega Version 7.1.8
The authentication/trojanhorseprotection previously defaulted to NEVER, creating a security vulnerability. The trojanhorseprotection setting now defaults to external.
SR-123636 · Issue 181701
Trojan horse protection auto-enabled
Resolved in Pega Version 7.1.8
The authentication/trojanhorseprotection previously defaulted to NEVER, creating a security vulnerability. The trojanhorseprotection setting now defaults to external.
SR-123712 · Issue 184471
Resolved schema qualification for dedicated tables
Resolved in Pega Version 7.1.8
When creating a data table / data class via the wizard, selecting "Create Dedicated Table" would show success on the wizard screen but the class was mapped to "pr_other" and an error was logged. This was caused by incorrect schema qualification for WorkHistory, and has been resolved by inserting a requirement for implicit schema privileges.
SR-123717 · Issue 192182
Purging of covered objects improved
Resolved in Pega Version 7.1.8
When purging a Cover item, the history of certain covered objects was not purged. This happened when the Cover and Covered classes belonged to different class groups. This happened because the 'getHistoryKeys' function tries to fetch the history details of a given key by looking into its history table. This was using the class group information from the archive configuration, which was not always the same for covered objects. To resolve this, the classgroup info will be fetched from its key - looking up Class map using the constructed class name will give the actual History Class name.
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-124473 · Issue 186179
Added handling for unauthenticated asynchronous SOAP service
Resolved in Pega Version 7.1.8
After implementing changes to work around an error with SOAP authentication, the unauthenticated asynchronous SOAP service generated an error and failed to complete. This was due to the changes to the authentication process omitting the asynchronous mode case when a SOAP service that intended to not use authentication ends up calling a sub-activity that requires authentication. This use case is now covered.
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.