SR-123911 · Issue 189019
Changed timing for retrieving autocomplete values after modifications
Resolved in Pega Version 7.1.8
When AutoComplete controls is used to populate Data, a wrong value was sometimes getting populated in the AutoComplete. The issue was due to the delay in change tracking request after the request is complete, causing it to take values from the server before the changes were committed. This has been corrected.
SR-123911 · Issue 192195
Changed timing for retrieving autocomplete values after modifications
Resolved in Pega Version 7.1.8
When AutoComplete controls is used to populate Data, a wrong value was sometimes getting populated in the AutoComplete. The issue was due to the delay in change tracking request after the request is complete, causing it to take values from the server before the changes were committed. This has been corrected.
SR-123960 · Issue 184251
Error message updated for report 'save as'
Resolved in Pega Version 7.1.8
The error message created when doing a 'Save As' report to a private category has been updated for clarity. Previously, the error generated was "The name you entered is not valid". This has been changed to "The name should start with letter followed by letter or digit or underscore".
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-124580 · Issue 192241
Changes made to Save preferences option in SummaryView to retain filter values
Resolved in Pega Version 7.1.8
In the reports filter section, even after clicking on save preferences button the selected filter values were not retained the second time. In the SavePreferences activity, pyAdvicetext was set to pyLabel and caused the selected filter value to not be stored. To correct this, changes were made to the SavePreferences and getPreferences activities: In getPreferences, pyAppName is set to advicetext if its length is more than zero or set to pyAppname from primary page if not. Also, in the SavePreferences activity, pyAdvicetext is set to local.adviceText (previously it was set to pyLabel).
SR-125210 · Issue 189127
Customization corrected for RRHeader section of RD
Resolved in Pega Version 7.1.8
If the RRHeader section item was customized and renamed, opening Report Definition and clicking "Edit Report Title" did not produce the expected results even with the "Edit Report Title" command enabled. This was due to the RRHeader section being hard-coded; this is now loaded dynamically to allow for customization.
SR-125245 · Issue 187386
Search ability corrected for rule names containing spaces
Resolved in Pega Version 7.1.8
While a space was allowed in the rule name of a report category rule, searching for a rule name with a space generated the error "Unable to open instance Error: Can't find record". This was due to a missing JavaIdentifier validator for the "pyCategoryName" property in "Rule-Category" class, and this has been added.
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.