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-B50434 · Issue 317985
Struts mapping updated to compensate for behavior change
Resolved in Pega Version 7.3.1
The expectation was that after system startup in a zOS multi-servant environment where each servant has two JVMs which are running at any given point of time, launching SMA after adding a primary node should cause the servant node to show up in the edit page and upon submit the servant nodes should be listed under the primary node under left navigation links. However, after upgrade new nodes added to the cluster in the SMA were not visible due to behavior change between struts releases. This has been addressed by modifying the mapping in struts.xml and tuning some JSP syntax issues in AddNodeIDs.jsp.
SR-B56125 · Issue 317516
WebLogic deployment guides updated for dual user setup
Resolved in Pega Version 7.3.1
The WebLogic deployment guides have been updated to specify that dual user setup requires the addition of the jdbc/AdminPegaRULES datasource with entries added to prconfig.xml. This is similar to the method used for the Tomcat app server.
SR-B56437 · Issue 317515
Schema handling enhancement added for Alternate database option in list view
Resolved in Pega Version 7.3.1
A List view configured to use the Alternate Database setting generated an error when the report was run, due to the schema used by the Reporting Database (defined in the Sandbox-Work database table rule) having a different name than the default Pega database. The main Pega database schema is PEGA721, and the Reporting Database in this case was a schema called PEGA721REP in the same database, causing the table to not be found. As support for the reporting database being located on an alternate database with user specified schema is not available, an enhancement has been added to provide a prconfig that takes the schema for an alternate database and provides the support for ReportDefinition to use it.
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-B65744 · Issue 315671
Repaired use of custom case ID search
Resolved in Pega Version 7.3.1
After upgrade, custom search criteria for case IDs generated an error when pulling data from the database. This was traced to a change that removed CommonTLP as a fallback, and that default has been restored.
SR-B66204 · Issue 316885
XSS sanitizing added to clientID field
Resolved in Pega Version 7.3.1
During the time of construction of a ServiceRequest in the engine , the clientID field will be sanitized with the StringUtils.crossScriptFiltering API to avoid XSS attacks.
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.