SR-B48598 · Issue 305742
Fixed exported PDFs of scheduled email reports in DS
Resolved in Pega Version 7.3.1
Scheduled email reports that were converted to PDF were not readable, appearing as a list of rules in a very small font in white over a very light grey. This happened when the "export to pdf" command came from the designer studio; pzDesignerStudio was being picked and using a skin with new CSS features like font-size: inherit, color: inherit etc., which were not supported by the PD4ML library. As a workaround, it was possible to ignore the skin while exporting the PDF via enabling the "Ignore application skin when exporting to PDF" data access tab of the report, causing the system to consider the styles from the pyReport_ExportToPdfStyles available rule instead of skin. As a permanent fix, the system will avoid encountering parsing errors with PD4ML by loading "pyReport_ExportToPdfStyles" and automatically removing the skin file whenever export to PDF via designer studio is triggered.
SR-B51844 · Issue 312363
Carriage return characters escaped in automated JSON data
Resolved in Pega Version 7.3.1
Automated JSON data received from the system containing carriage return characters such as \n, \r, \t caused parsing issues. To resolve this, changes have been made in the webwb-pzPega_ui_roboticAutomation-js file such that all carriage return characters such as \n,\r,\t will be handled using an escape sequence.
SR-B37374 · Issue 309750
null-pointer exception fixed for missing rule class
Resolved in Pega Version 7.3.1
After upgrade, a null-pointer exception was generated when the class on which a rule was defined no longer existed and there was a withdrawn rule in the hierarchy. This has been fixed.
SR-B44095 · Issue 318443
Re-indexing modified with check for FTS reinitialization
Resolved in Pega Version 7.3.1
Using the Designer Studio 'Search Landing Page' to initiate a re-index of approximately 12 million work items never seemed to complete. This was traced to an unnecessary reinitialization call; the API used to reconfigure the Search node (initialized from the FullTextIndexer command line utility) uses the configure node API to remove the index directory information on the index node. This API has logic to reinitializeFTS because it is the expected behavior in normal scenarios. However, in cases using the full text indexer command line utility, we do not need to reinitalize the FTS instance as the node is a standalone node. This has been updated.
SR-B48161 · Issue 311806
Pega0001 alert honors parameter page inclusion setting
Resolved in Pega Version 7.3.1
The setting was not being properly honored, causing sensitive information to be available in the ALERT logs. This has been revised so the system will honor the above setting and if it is set to false, the parameter page will be disabled in the alert lines.
SR-B64805 · Issue 318491
Change tracking added for emptied properties for BLOBs
Resolved in Pega Version 7.3.1
In a configuration where Property value was set from the output of a Decision Table which was called on Declare Onchange Frequently, a properly later set to null was only updated in the exposed property. This caused BLOB inconsistencies. To correct this, change tracking has been implemented for emptied properties.
SR-B65652 · Issue 315008
Corrected datasource used to update pr_extract_time
Resolved in Pega Version 7.3.1
If the "use last updated time as start" filter was used for a class which mapped to a table in an external database, a database permission error was thrown when trying to access the pr_log table in the PegaRULES database. This has been corrected by updating pr_extract_time using the connection from Pega-Extract-Time instead of the extract class.
SR-B69133 · Issue 317298
Carriage returns stripped from ExtractIdentifier value
Resolved in Pega Version 7.3.1
If the pzInskey value in the extract rule xml file had extra carriage returns, the pxExtractIdentifier was generated with extra carriage returns in the value. Downstream processing was failing because of these extra carriage returns. To correct this, all carriage returns will be stripped from the pxExtractIdentifier value.
SR-B70051 · Issue 324690
Enhanced Dnode Pulse logging
Resolved in Pega Version 7.3.1
Enhanced pulse logging has been added for DNode errors
SR-B76502 · Issue 325128
BIX extract exceptions and missing XML fixed
Resolved in Pega Version 7.3.1
StringIndexOutOfBoundsException and ClassCastException were being generated during BIX extract and some tags were missing in the extracted XML. This has been fixed.