SR-B41874 · Issue 301766
View parsing regex fixed for union statements
Resolved in Pega Version 7.3
While importing jar file through import out-of-the-box, generated SQL Scripts from the manual option system had scripts which were already present in the Database. This was caused by the view parsing regex not handling UNION statements, and has been corrected.
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-B42009 · Issue 304044
Authentication timeout smoothed for re-login
Resolved in Pega Version 7.3
If custom authentication was used with a stream specified to enter credentials upon authentication timeout, re-login failed after the timeout. This was traced to two issues: first, the custom configuration defaulted to using the out-of-the-box stream "Web-TimeOut", which expects the password to be in base64 encoded format and so attempts to base64 decode it. This caused an authentication failure. Second, when restarting with authentication instead of a timed-out request, the starting activity of operator was being executed and the portal was rendered unexpectedly. To resolve this, the object references needed for the successful resumption will be cloned when there is authentication timeout and used for redirection upon successful authentication.
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-B42110 · Issue 299959
RD "Available & Valid Values" properly populated
Resolved in Pega Version 7.3
The filter conditions in the report definition for the Available and Valid value list was displayed as blank or empty for properties which were exposed for reporting purpose and are at one level below the PyWorkPage. This was traced to an improper splitting of the property when pointed from the Parent, and has been fixed.
SR-B42218 · Issue 300079
Updated logic check for property panel invalid actions
Resolved in Pega Version 7.3
Configuring invalid actions on the events & actions property panel was not triggering the validation messages when submitted, saved, and checked-in. When the action was re-opened, no changes were saved. This was due to a segment of code called on load of the property panel that remained for backwards compatibility but should not have been called in this scenario. This has been fixed by adding a check at the top of this activity for messages/errors which will route the logic appropriately.
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-B42262 · Issue 303693
Field Values displayed correctly in mobile dynamic layouts
Resolved in Pega Version 7.3
Dynamic layout headers that reference Field Values were not displayed correctly in the mobile application. This was caused by the getLocalizedValueFromList function not passing activeContext to the resolveParams function, and has been fixed.
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.