SR-B44280 · Issue 302124
Fixed REST call to JVM property http.non.ProxyHosts
Resolved in Pega Version 7.3
If JVM system properties are used to configure an HTTP proxy, it is applied unconditionally by all REST connectors. The JVM property http.non.ProxyHosts is normally used to exclude connections selected hosts from using the proxy, but due to an error this property was not being consulted by the REST connector. This has been corrected.
SR-B44280 · Issue 301832
Fixed REST call to JVM property http.non.ProxyHosts
Resolved in Pega Version 7.3
If JVM system properties are used to configure an HTTP proxy, it is applied unconditionally by all REST connectors. The JVM property http.non.ProxyHosts is normally used to exclude connections selected hosts from using the proxy, but due to an error this property was not being consulted by the REST connector. This has been corrected.
SR-B6244 · Issue 277565
Documentation and log messages updated for BIX/useHistoryClasses
Resolved in Pega Version 7.3
When using command-line BIX 7.1 to extract records and write them to a secondary database, messages from the system gave the impression that some of the records were skipped. This was due to a mismatch in the number of records reported at different points in the extraction: as the records got updated while the extract was running, those particular updated records got skipped as they did not fall into the time range that user was passing. To avoid this confusion, the text in the logs has been clarified to read: "Processing Class class name with XXXX instances (processing count may vary as records get modified before BIX extraction)." In addition, the documentation regarding the usage of the BIX/useHistoryClasses option has been updated to reflect this information.
INC-162262 · Issue 654966
Query added to find time zone for MSSQL database
Resolved in Pega Version 8.7
The exception "com.microsoft.sqlserver.jdbc.SQLServerException: xp_regread() returned error 5, 'Access is denied.'" was generated when the AES agent PushDBSizeInfo was being run. This was traced to the GetDBInfo activity trying to retrieve the time zone of the MSSQL database by executing a query that used a Microsoft SQL routine to read the windows registry to get the current time zone. The error was not due to security within the SQL Server, but instead was caused by Microsoft Windows security related to the permissions on the registry keys for the users under which specific SQL Server processes were running. To resolve this, an update has been made to call a different query which will get the time zone for the SQL Server.
INC-172849 · Issue 665983
SortPageList method updated for Obj-Sort
Resolved in Pega Version 8.7
Sorting page lists backed by a node level datapage using Obj-Sort was causing a ConcurrentModificationException. This has been resolved by updating the SorterImpl.sortPageList method to use java7CollectionsSort instead of collectionsSortWithInferenceEngineDisabled.
SR-B35963 · Issue 292315
pyID displayed in Show relevant Records
Resolved in Pega Version 7.3
Class keys were not displayed on select picker when accessing relevant records. This was due to an misplaced 'when' condition, and has been fixed.
SR-B35963 · Issue 292466
pyID displayed in Show relevant Records
Resolved in Pega Version 7.3
Class keys were not displayed on select picker when accessing relevant records. This was due to an misplaced 'when' condition, and has been fixed.
SR-B11441 · Issue 280633
Connect-SOAP jar recompiled with JDK 1.7 for greater compatibility
Resolved in Pega Version 7.3
After upgrade, an error was generated by Connect-SOAP calls on systems using JDK 1.7. This was caused by the Pega jar having been compiled with JDK 1.8, which lacks backwards compatibility. To resolve this, the jar has been recompiled using JDK 1.7 as it has forward compatibility and will work with the higher version.
SR-B14129 · Issue 284313
JSON mapping updated to support page list class given as string value
Resolved in Pega Version 7.3
Connect Rest was not parsing the value of the Boolean property "isEligible" returned as part of a JSON response or mapping it on to the clipboard. This was traced to the unexpected scenario of the string "$ANY" being used as class for a page list and inside a pagelist Boolean property. To support this use, the JSONMappingUtils.java file mapObjectToPage method has been modified to handle the Boolean property before the generic else if condition.
SR-B15749 · Issue 289752
Enhancement for capturing SOAP envelope of Async SOAP Service
Resolved in Pega Version 7.3
The SOAP service request envelope has been available for service activity using the 'pxRequestor.pxReqSOAPEnvelope' property in synchronous execution mode, but that envelope was not available in asynchronous execution mode due to asynchronous execution using a different requestor. In order to support this information in asynch mode, an enhancement has been added to allow the service activity to perform a look-up for the pxReqSOAPEnvelopeinformation in the parameter page.