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.
SR-B57614 · Issue 322754
PegaMobile honors prompt for password check
Resolved in Pega Version 7.3.1
The Pega Mobile App option to 'Always prompt for password on start' was not saving the selected choice. This was caused by a conflict with "Do not save property data" in the persistence section of the property advanced settings, and has been fixed.
SR-B67236 · Issue 325268
Resolved infinite loop in offline app
Resolved in Pega Version 7.3.1
Pressing "Next" was causing an offline app to go into an infinite loop. This was found to be caused by two issues: there was a problem with back processing when deeply nested subprocesses were configured, and the handling was not working with a subprocess that had more than one 'from-connectors'. This has been addressed by modifying the implementation logic in process_flow.
SR-B69404 · Issue 320544
Map include enhanced with fallback "Show user location" function
Resolved in Pega Version 7.3.1
When Map was included in a section by checking the "Show user Location" option, the pxRequestor.latitude and pxRequestor.longitude options were empty in the clipboard. Also, in Microsoft Internet Explorer the user location was not shown and the default Boston location was given. This was traced to a null pum.GeolocationMarker.position in Microsoft Internet Explorer, and a fallback approach has been inserted to set the position from the existing previous value.