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-B11741 · Issue 285895
Tenant ID check added to Ruleset Wizard for MT
Resolved in Pega Version 7.3
Attempting to deleting a ruleset in a multi-tenant environment using the Ruleset Wizard resulted in the error message 'Getting records from the database' and the application would hang. This was due to a missing tenant ID in the SQL statement, and a check has been added to the query generation to ensure the prepared values for "pzTenantID" are included.
SR-B11927 · Issue 280995
pyContentType column populated in recents table
Resolved in Pega Version 7.3
After upgrade, the new column "pyContentType" was visible in the pr_data_recents table, but data was not getting populated into this column when work objects or rules were opened. This was due to the recents tab missing the pyContentType column query from the custom population queries, and this has now been added.
SR-B12215 · Issue 281902
Cancel button fixed for pzTabbedScreenFlow7 harness
Resolved in Pega Version 7.3
The Cancel button was visible on the modal template of the Data import Wizard but was missing on the pzTabbedScreenFlow7 harness. This has been fixed.
SR-B12474 · Issue 282553
BIX extraction config documentation updated
Resolved in Pega Version 7.3
When using command-line BIX 7.1 to extract records and write them to a secondary database, it appeared that some of the records got skipped. This was actually expected behavior: 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 eliminate this confusion, the log message has been clarified. In addition, the information in the Guide indicated that if bix/useHistoryClasses was set to true, the generated query should always use the history table and not the actual work object table. However, it was not made clear that the BIX code does not use this option for explicit command line arguments. Therefore, the following text has been added to the BIX documentation under "Configuring the extraction environment" -> "Configuring optional prconfig.xml settings": Including class instances added during a batch run To ensure that class instances added to the Pega Platform database after a batch run begins execution are included in the extract, add the following property:
SR-B12783 · Issue 285395
Performance improvements for Data Designer Visualizer
Resolved in Pega Version 7.3
In order to improve performance of the Visualizer feature of the data designer, the loading behavior has been changed. Previously, the RD being executed for each node in the graph to get the reference properties was defer loaded; this potentially caused issues if the data was still being loaded in the background for the visualizer and an attempt was made to open BodySite. To fix this issue, the defer loading has been removed and the data will load on click of the "visualizer" button.
SR-B12857 · Issue 285462
Repaired REST Connections with proxy
Resolved in Pega Version 7.3
After upgrade, connections to external internet websites/services were failing when using a proxy. This has been fixed.
SR-B13040 · Issue 293380
Improved reliability for GetReference API
Resolved in Pega Version 7.3
A sporadic issue with the OOB getReference API caused a failure in obtaining the absolute reference for a parameterized data page. This was caused by a race condition in the page handler, and synchronization has been improved to ensure the proper name will be set into the data page.
SR-B13040 · Issue 293526
Null DPI check added for async page load
Resolved in Pega Version 7.3
A null pointer exception was being generated when a data page was being loaded from the asynchronous cache and some exception occurred while switching the access group or getting a definition. To avoid this, a check has been added for a null DPI.
SR-B13929 · Issue 289408
Instances Count updated to better handle external DB checks
Resolved in Pega Version 7.3
Opening the Data table list from the Designer studio DesignerStudio > Data Mode > Data Tables > Data Tables generated an exception related to obtaining a count of instances from an external DB. This has been resolved by adding a check which modifies the activity based on whether the call is to an internal or external DB.