SR-A21830 · Issue 244836
Improvements made to History Compare
Resolved in Pega Version 7.2.1
The SMS treatment rule full history provided by Pega Marketing was not reflecting the actual changes that were applied in each revision and the compare differences functionality was not showing expected differences. The handling of the comparison has been updated to correct this, and the logic has been further improved to include the "initial creation" version when appropriate.
SR-A21830 · Issue 246779
Improvements made to History Compare
Resolved in Pega Version 7.2.1
The SMS treatment rule full history provided by Pega Marketing was not reflecting the actual changes that were applied in each revision and the compare differences functionality was not showing expected differences. The handling of the comparison has been updated to correct this, and the logic has been further improved to include the "initial creation" version when appropriate.
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-A22067 · Issue 243520
Corrected passing Current Parameter Page in Collections
Resolved in Pega Version 7.2.1
When attempting to call a rule in a Response Actions entry on a Collection flow, the configuration panel would not submit when "Pass Current Parameter Page" was checked and there were required parameters on the rule being called. This was traced to an unneeded validation being performed, and has been resolved.
SR-A22090 · Issue 243573
Activity method loading works with encryption
Resolved in Pega Version 7.2.1
Activity method loading was not working with URLEncryption enabled. This was a problem with populating the parameters with the encryption function in use, and has been fixed by making use of SafeURL to prepare the querystring of the URL.
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-A22234 · Issue 243871
Resolved CME error for case withdrawal
Resolved in Pega Version 7.2.1
When withdrawing a case, pxForceCaseClose was throwing Concurrent Modification Exception. This has been fixed.
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.)