SR-B41820 · Issue 299434
Map from field updated to ensure Correspondence Name and Type are included
Resolved in Pega Version 7.3
An error was generated while configuring a Map From field as Correspondence. This was an issue with the Correspondence Name not being passed: when the Map From is selected as Correspondence, the backend expecting the Map from Key as a space separated combination of Correspondence Name and Correspondence Type. If only the Correspondence Name was selected, then the back end failed to find the Correspondence Type. This has been fixed by modifying the code to combine left and right from key part to ensure both parts are sent.
SR-B4193 · Issue 274552
NexFlow requestor performance improvements
Resolved in Pega Version 7.3
The deployment of the Nexflow Application RAP was failing due to a requestor synch timeout if 'includeSynonyms' was enabled on the DB connection. Code updates have been implemented to improve performance to resolve this.
SR-B42078 · Issue 298933
Improved logic for external Connect-SOAP error handling
Resolved in Pega Version 7.3
An application with a requirement to check all data pages before loading the portal was generating an error if there was a Connect-SOAP failure during data page load. To resolve this, the logic has been modified to better handle external system exceptions caused by a SOAP failure.
SR-B42078 · Issue 298145
Improved logic for external Connect-SOAP error handling
Resolved in Pega Version 7.3
An application with a requirement to check all data pages before loading the portal was generating an error if there was a Connect-SOAP failure during data page load. To resolve this, the logic has been modified to better handle external system exceptions caused by a SOAP failure.
SR-B42249 · Issue 301181
Resolved HashMaps memory leak
Resolved in Pega Version 7.3
A memory leak was found with HashMap "mapHosts" within MultiThreadedHttpConnectionManage. To handle this, updates have been made to prcommons-pr54.jar (MultiThreadedHttpConnectionManager.java) and cross verified with the latest library from Apache.
SR-B42305 · Issue 299199
Parse-XML generation updated for complex XML element
Resolved in Pega Version 7.3
When generating the datamodel using the REST wizard, if the response XML had a page with type attribute then the value was ignored at run time. This has been fixed with updates to the "RuleGeneratorREST.java" for data model generation and "ParseXMLSAXRuleWrapper.java" for run time handling.
SR-B42374 · Issue 299138
Data Import Wizard Flow error corrected
Resolved in Pega Version 7.3
The Data Import Wizard was failing with the error "Unable to perform {1}: assignment does not exist." This was due to the pzDataImport screen flow being in Draft mode, causing any rule that runs it to fail if the system is in Production level 5. This has been corrected by setting the draft mode to off.
SR-B42374 · Issue 299446
Data Import Wizard Flow error corrected
Resolved in Pega Version 7.3
The Data Import Wizard was failing with the error "Unable to perform {1}: assignment does not exist." This was due to the pzDataImport screen flow being in Draft mode, causing any rule that runs it to fail if the system is in Production level 5. This has been corrected by setting the draft mode to off.
SR-B42964 · Issue 302624
History table updates with data table record deletion
Resolved in Pega Version 7.3
The Deletion of the record from a data table was not adding an entry into History table. This behavior has been changed with a "History-Add" step in the pzDeleteRecord activity.
SR-B43331 · Issue 302897
Help file updated for consequences of "Ignore Locale" setting
Resolved in Pega Version 7.3
Issues with date values were encountered in set ups where a localized Language Pack had been installed and developers used the "Operator Ignore locale preference" in Designer Studio in order to have Designer Studio in English. While the user portal was correctly translated and European format dates were accepted, an error stating "date is not a valid date value" would appear when a date time field was updated or a new ruleset was created. In order to ease the use of the setting, the help files have been updated to clarify that the "Ignore Locale" option on the Operator screen causes ALL locale settings to be ignored and the default en_US settings to be used. In addition to the display language, these settings include date, time and number formats.