SR-B4548 · Issue 275330
Class Data-Admin-Connect-MQServer now cached
Resolved in Pega Version 7.3
The rule instance cache has been updated to include the type Data-Admin-Connect-MQServer.
SR-B45613 · Issue 302956
Fixed query for RD using dependent classes
Resolved in Pega Version 7.3
A runtime exception was generated when running a summary report due to an incorrect query being built for RD when dependent classes was checked. This was caused by pyGetDistinctRecords being set to true even for summary reports, and has been corrected by ensuring pyGetDistinctRecords is set to false for summary reports.
SR-B45640 · Issue 302810
Resolved ConcurrentModification exception in getclass name
Resolved in Pega Version 7.3
Attempting to getclass name while iterating over values of mPageProperties in expandAllToProperties (in the putPropertyOntoClipboard call) was causing a ConcurrentModificationException that resulted in queues being blocked and loss of synch to the server. In order to more cleanly set the pxObjClass for the classless page-properties, pxObjClass has been added to the lookupDictionaryDefinition.
SR-B45640 · Issue 303222
Resolved ConcurrentModification exception in getclass name
Resolved in Pega Version 7.3
Attempting to getclass name while iterating over values of mPageProperties in expandAllToProperties (in the putPropertyOntoClipboard call) was causing a ConcurrentModificationException that resulted in queues being blocked and loss of synch to the server. In order to more cleanly set the pxObjClass for the classless page-properties, pxObjClass has been added to the lookupDictionaryDefinition.
SR-B45744 · Issue 302814
Debug logs Response XML
Resolved in Pega Version 7.3
The InvokeAxis2 activity was logging the Request XML to the debug log, but was not logging the Response XML. Code has been added to the InvokeAxis2 Activity to print the SOAP Response in the log file when debug is enabled.
SR-B45917 · Issue 302415
DisplayReport date made consistent between report and exported PDF
Resolved in Pega Version 7.3
When exporting a report to PDF, the "Generated on" date did not match the format on the report. This was caused by the system using different controls for date in pzDisplayReportSectionForPDF and displayReportSection, and has been resolved by changing the date format specified in pzDisplayReportSectionForPDF to match that in displayReportSection.
SR-B46050 · Issue 302190
Corrected DateTime corruption
Resolved in Pega Version 7.3
If "Display value using read-only formatting" was selected for a Date field, entering an invalid value caused the resulting HTML DOM to be displayed incorrectly when the page was refreshed. This was traced to missing handling for the exception resulting from the invalid data, and has been fixed.
SR-B46173 · Issue 302359
Improved HTTP thread handling
Resolved in Pega Version 7.3
During the execution of a performance test (SOAP service, RBS application), several exceptions were generated relating to the attempt to use a 'recycled thread'. In order to resolve this, the HTTP thread locking and ownership have been improved.
SR-B46173 · Issue 296360
Improved HTTP thread handling
Resolved in Pega Version 7.3
During the execution of a performance test (SOAP service, RBS application), several exceptions were generated relating to the attempt to use a 'recycled thread'. In order to resolve this, the HTTP thread locking and ownership have been improved.
SR-B462 · Issue 271962
Event Late triggers expanded
Resolved in Pega Version 7.3
If "Limit passed deadline events" was not set to any value and the enqueue item was still in defer-save and not committed to DB, 'Event Late' was not triggered. Code has been added to properly check and trigger the late notice based on this scenario.