INC-174468 · Issue 650946
Delegated rules search considers localized text
Resolved in Pega Version 8.7
The search / filter box used to look for particular delegated rules on the configuration tab did not consider localization via field values, where the on screen name and description of the delegated rule was localized. This resulted in the search text being compared against the original text (.pyAdviceText and .pyDescription) used for the name and description at the time the rule was delegated, but not with the localized text that actually appeared on the screen. This has been resolved by updating the pzPopulateDelegations activity to filter by localized values of pyAdviceText and pyDescription.
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-A19986 · Issue 244104
getAppHashForApplication API updated
Resolved in Pega Version 7.2.1
When logged in from an end user portal, editing a decision table and clicking on the gear icon to add a function would show the Function's headers (Example, Activity, string, etc.), but the functions list would not be loaded. This was traced to a timeout resulting from having numerous functions running on the portal combined with a configuration that returned an unowned AppHash when calling a ruleset from the production layer rather than the application layer, and has been resolved by adding logic to write out the AppHash when the appInfo is created from opening the application.
SR-A14562 · Issue 231191
Enhanced logging to debug Composite Portal Menu rendering errors
Resolved in Pega Version 7.2.1
In order to better diagnose exceptions generated when trying to render a Section from Composite Portal Menu, more debug logs have been added when DatabaseImpl.open is called on any particular instance. The debug logs will print the authorization related information - the ruleset list, the current thread, current access group etc.
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.
INC-184800 · Issue 685685
Handling updated for switching between concrete and abstract class types
Resolved in Pega Version 8.7
After configuring a non-templatized table with source as page list, with the page list property sourced to abstract class, a runtime exception was seen when loading the table that indicated "database.BadInputException: Cannot open or save instances of class Data-Orders-OrderDetails--the class might be abstract, or it might have no defined keys, or it might descend from Code-". When a class is created and saved as concrete, there is a checkbox "Automatically generate a unique ID for records of this type" which when checked will set pyAutogeneratedKey to false on the clipboard. If the Class is then later changed to abstract without unchecking the checkbox first, then the BadInputException error will manifest on the table at runtime. Investigation of the Edit Class ruleform found some scenarios where clipboard properties which have previously been set while Class type dropdown is set to Concrete can persist and cause the BadInputException seen when the class is switched to Abstract. This has been resolved.
SR-A20675 · Issue 243568
Repaired encrypted remote tracing
Resolved in Pega Version 7.2.1
Remote tracing was not working when URLEncryption was enabled due to an error calling SafeURL. This has been fixed.
SR-A19219 · Issue 237911
RACache performance improved
Resolved in Pega Version 7.2.1
Pega0005 alerts were appearing during system startup, and queries were taking an excessive amount of time. Bind variables are now used in the RACache loading query at server start up to improve performance.
SR-A20287 · Issue 235728
Corrected refresh results for filtered propositions
Resolved in Pega Version 7.2.1
A refresh error related to filtering performed with the propositions using a certain business issue & group in PegaMarketing caused a list refresh that automatically brought back all the propositions after selecting one. This has been fixed.
SR-A19652 · Issue 246778
BIX filter failure alert added
Resolved in Pega Version 7.2.1
A warning has been added to issue an alert when filters are not being added while generating a BIX query.