SR-A3992 · Issue 211563
WSDL generation updated
Resolved in Pega Version 7.1.9
A coding error for the constants used in generating WSDL was creating a problem for some installations with the resulting data. This has been corrected.
SR-A4918 · Issue 211744
Reverted WSDL naming convention to previous style
Resolved in Pega Version 7.1.9
In earlier versions of the system, the exposed Pega-generated WSDL had ComplexType named "CreateCaseWSRequestType" with uppercase "T". A recent change to naming the ComplexType "CreateCaseWSRequesttype" with lowercase "t" required a manual override to use previously generated WSDLs after upgrading, so the naming has been reverted to using the uppercase "T" format.
SR-A5413 · Issue 212956
Null check added to ParseXMLSAXRuleWrapper
Resolved in Pega Version 7.1.9
Thread lock error messages were being generated in the clipboard when trying to access a property pyNote whose value has been initialized with XML content. This was traced to ParseXMLSAXRuleWrapper adding a null value to the Clipboard Value list, and a null check has been added to prevent this.
SR-A959 · Issue 205668
Enhanced locking for EmailListener to detect and process auto-reply
Resolved in Pega Version 7.1.9
Due to thread locking timing, the EmailListener was not detecting 'autoreply' emails, causing infinite loops. This has been fixed by adding code to look for DSS Email/AutoReplySubject. If present, it will lock the requestor before getting the custom AutoReply setting and processing as expected.
SR-A4056 · Issue 211550
Corrected validation error for Extract rule field length
Resolved in Pega Version 7.1.9
A validation error noting that the field length of the table was limited to 30 characters was occurring when trying to check in an Extract rule even if the field value had been shortened. While checking in the extract rule, a block of code in the Rule-Utility-Function validateTreeProperties was recomputing the pagelist's table name instead of using the one provided by the user. The Rule-Utility-Function validateTreeProperties function has been modified to fix the issue.
SR-D71977 · Issue 535602
Obj-Browse will retrieve more than 50 records
Resolved in Pega Version 8.5
After performing multiple skims, a newly added property was not retrieved when an Obj-Browse was performed. In Obj-Browse action, when a class is mapped to an external table and does not contain BLOB column pzpvstream, in a specific case where pxObjClass value is a reference to a parameter, a list of properties mapped to the class explicitly by querying pr4_rule_property table using NativeSQL is fetched. This call by default returns only 50 records: in cases where there are more than 50 properties for an external class, some of the properties from the obj-browse response mapping are therefore missed. To resolve this, the limit of 50 records has been removed from this NativeSQL call.
SR-D65112 · Issue 541149
Added support for imported rules to populate bixreportpage
Resolved in Pega Version 8.5
Extract rules were not holding the filter criteria after upgrade while performing save-as (for the first time) of the imported rules from the previous version. Criteria were held when the filters were created in the new version. This was caused by BIX extracts created in earlier releases (7.x) not having bixreportpage included. When an environment was upgraded to 8.x versions, opening an extract required the bixreportpage to be populated with RD metadata including the filters defined in the actual extract. Although the filters from the original extract were converted to filters that are acceptable by ReportDefinition, they were not being added to bixreportpage on opening the extract. To resolve this, the system has been updated to copy the filters back to bixreportpage on opening the extract in the upgraded environment.
SR-D76150 · Issue 539454
Logging updated for EmailListener and Data-Agent queue items
Resolved in Pega Version 8.5
In order to avoid the pr_sys_queue_ftsindexer table being overwhelmed with Data-Admin-Connect-EmailListener and Data-Agent-Queue instances for queued items, the Data-Admin-Connect-EmailListener and Data-Agent-Queue class definitions have been modified to filter queue items to incremental indexing if updates are from system and instance type is data- .
SR-D66986 · Issue 539414
BIX command line support improved
Resolved in Pega Version 8.5
Post-upgrade, it was seen that changes to the engine which validate that Data-Admin-DB-Name is not defined multiple times caused the BIX command line extracts to no longer work the same way. In order to improve backwards compatibility, updates have been made to loosen the validation in JdbcConfigurationFactory to always prefer prconfig settings if there are multiple definitions.
SR-D70890 · Issue 542871
Enhanced diagnostic logging for automatic search re-index
Resolved in Pega Version 8.5
To better analyze an out of memory error, enhanced diagnostic logging has been enabled for the below classes to get more information regarding re-index triggered automatically after search index is complete. PegaSearch.SearchManager.SearchInitlizationUtils PegaSearch.SearchManager.BuildIndicesTask Rule_Obj_Activity.pzLPFTSManagerRunBuildIndex.Pega_Search_Manager.Action PegaSearch.Indexer.AbstractIndexer