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-A21935 · Issue 247142
Corrected data page Lookup logic
Resolved in Pega Version 7.2.1
While trying to source a Datapage with Lookup, a "No records found" error was generated by the fetch using the pyClassName from parameter and considering that as primary page class instead of the data page page class. This has been corrected by using the pxObjClass from the parameter page, which is an actual data page class.
SR-A22152 · Issue 247716
Report Def Filter using .pxObjClass returns all results
Resolved in Pega Version 7.2.1
Using .pxObjClass as a filter in Report Definitions resulted in different and/or incomplete Class arrays being built depending on how the Value field was populated. This was traced to an incorrect "if" check in objClassOptimizer causing class names to be missed, and has been fixed.
SR-A22200 · Issue 241230
Bulk actions filters refresh corrected
Resolved in Pega Version 7.2.1
The values entered into the right side column of the bulk processing filters were not getting submitted to the clipboard when default filter conditions were changed. The refresh action has been updated to correct this.
SR-A22458 · Issue 243317
Plus '+' sign encoding corrected in connect-HTTP
Resolved in Pega Version 7.2.1
Using connect-http get to send an encrypted string to the external endpoint was not working due to missing encoding for the plus '+' string. The encoding has now been fixed.
SR-A22722 · Issue 246998
pxDereferenceEndpoint Activity can be overridden by the customer
Resolved in Pega Version 7.2.1
The generic pxDereferenceEndpoint Activity that applies to the Rule-Connect-REST class was not the functionality desired by the customer, so they wanted to be able to change it, but it was set to ?Final? and couldn?t be changed. The availability of the pxDereferenceEndpoint Activity has now been set to ?Available? so that customers may override it in any RuleSet. (No logic changes have been made to this activity.)
SR-A22794 · Issue 245278
parseXML able to map multiple values
Resolved in Pega Version 7.2.1
In order to present more information for custom use, parseXML as been updated with a new pagelist property that can map multiple attribute values.
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."
SR-A23050 · Issue 244774
Rule generation updated to handle related JSONs
Resolved in Pega Version 7.2.1
The system was failing to parse inbound JSONs when the corresponding Pega Data Model was generated using the same JSON, and was unable to use valuelist or pagelist properties for generating JSON to pass to connect-Rest Method. This generation and runtime of rest connector was failing when the same name property existed in multiple places with different modes and same levels. To support this use, the rule generation has been updated to correctly populate the qualifier name along with modified run time code to support mapping when same properties are there in the same class.