SR-A21741 · Issue 248725
Fixed drilldowns and filtering with encrypted property
Resolved in Pega Version 7.2.1
After encryption of a property, filtering and drill down reports stopped working. "TAB" space is added as first character along with encryption data to store a textencrypt property type in the database, but while performing the drill down the TAB key is not appended. Instead "/t" character is added which does not fetch the results. To fix this, the JavaScript has been modified to ensure "\t" isn't added so drill down activity will get the proper results.
SR-A21756 · Issue 244285
defined-on class error resolved
Resolved in Pega Version 7.2.1
A defined-on class error was being generated when attempting to add strategies to the overlay that referenced a decision rule defined on an SR class with a space in the name. This has been fixed.
SR-A21756 · Issue 243206
defined-on class error resolved
Resolved in Pega Version 7.2.1
A defined-on class error was being generated when attempting to add strategies to the overlay that referenced a decision rule defined on an SR class with a space in the name. This has been fixed.
SR-A21844 · Issue 241153
VBD enhancements
Resolved in Pega Version 7.2.1
The following enhancements have been added to the Visual Business Director feature of PRPC Decisioning: - Support added for changes in field sizes after partitions load - Partitions will be loaded immediately on VBD server startup - Data expiration based on inactivity is disabled to reduce query latency - Timeout added to VBD queries to handle latency when Partitions initially load - Code that processed Actuals query JDBC resultset is optimized
SR-A22147 · Issue 244096
Autogenerated prconfig sets v6 or v7 based on detection
Resolved in Pega Version 7.2.1
The autogenerated prpcUtils prconfig.xml file was setting the database/storageVersion to 6. In order to facilitate other setups, a flag has been provided in prpcUtils.properties as pega.storageVersion which will set the value in generated prconfig.xml to an empty string so the engine handles setting this to 6 or 7 in the same way that is possible when running the system.
SR-A22263 · Issue 242102
Improved error reporting for PE install
Resolved in Pega Version 7.2.1
In order to facilitate debugging, attempting to install Pega Express from a directory with a space in the name will generate an error on the screen reiterating the installation instructions requiring that the directory name not contain a space.
SR-A22354 · Issue 245861
prpcUtils honors 5.4 compatibility checkbox
Resolved in Pega Version 7.2.1
Pega deployment using prpcUtils was failing due to the 5.4 compatibility checkbox being ignored: the product rule being exported still included schema changes in the exported RAP file. This has been corrected.
SR-A22672 · Issue 243213
Use Pega Log Analyzer in place of Alerts.xls Excel Template
Resolved in Pega Version 7.2.1
A documentation error incorrectly referred to the Alerts.xls Excel template as being available on the PDN. That file is no longer available, and the Pega Log Analyzer should be used instead: https://pdn.pega.com/community/pega-exchange/pegarules-log-analyzer
SR-A22841 · Issue 245073
All Data Flow keys considered for filtering
Resolved in Pega Version 7.2.1
When a Data Flow containing a Filter was run , the filter step showed incorrect results in the "Successful records" column even though previewing it from the Data Flow rule it showed the correct result. The algorithm that queries a secondary source shape in the data flow was ignoring all but the first key, and has been updated to properly process all of the keys before displaying any results.
SR-A23035 · Issue 245109
Enabled bulk delete of ADM models
Resolved in Pega Version 7.2.1
In order to support the deletion of ADM models in bulk, an enhancement has been added to remove the unwanted models from the database provided a list of them is given as input. The activity pxDeleteModelsByCriteria has been created; "Used to delete ADM models in bulk. Models to be deleted are determined by the criteria selected by this Activity's parameters; a model is deleted if it matches all selected criteria." PLEASE NOTE: activity is not constrained by Application, only by the criteria provided as parameters. Therefore in most cases you will probably want to constrain by 'applies to' class in addition to the other criteria. Please see the tooltip / description of each parameter for more info on their usage. Integer output parameter 'NumberDeleted' returns the number of models that were successfully deleted."