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.
INC-182986 · Issue 668829
Property Rule Form refreshes after discarding changes
Resolved in Pega Version 8.7
After updating from Pega 8.2 to Pega 8.6 and migrating the properties, modifying any property rule and then discarding the change did not refresh the Property Rule Form. Investigation showed that the LOG-SYSTEM-PROPERTYOPTIMIZATION instance created during property optimization was not getting deleted when a property was deleted. As this was not getting deleted, the property was shown as optimized when adding the property back, causing confusion. This has been resolved by cleaning up the LOG-SYSTEM-PROPERTYOPTIMIZATION instance when the property is deleted and there is an optimization entry.
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.
INC-173505 · Issue 657024
Error message updated for data page with REDUX
Resolved in Pega Version 8.7
A WrongModeException was generated when a runtime activity was trying to access a missing property in a data page with REDUX enabled. To clarify the issue, the error has been modified to be a MissingPropertyException. In addition, property information for a page group property was inferred on the top level page when it should have been inferred on the embedded page. This has been changed to infer the correct property information for mode-based processing to work as expected.
INC-197112 · Issue 689260
Corrected unnecessary Severe Warnings for MSGraph account
Resolved in Pega Version 8.7
After configuring an email account with MSGraph settings and saving the the email account instance, three unneeded severe guardrail warnings were generated related to using D_pxGetApplicationSettingValue instead of a constant value. This has been resolved.
SR-117020 · Issue 167867
Cookies only generated if IAC enabled
Resolved in Pega Version 7.1.7
IAC cookies were being generated in environments where IAC was not deployed, causing the application be flagged in a security audit due to missing Secure attributes. To correct this, the system has been updated to bypass cookie generation if IAC is not in use.
SR-119030 · Issue 172922
Clipboard privileges tightened to enhance security
Resolved in Pega Version 7.1.7
Using standard browser development tools, it was possible to insert a client-side modification into a Pega-served HTML page to allow a customer to access partial clipboard inspection functionality. To correct this, starting activity privileges have been tightened.
INC-191033 · Issue 684370
Security updated for viewing data tables
Resolved in Pega Version 8.7
In order to improve security related to viewing data table instances, the privilege pxListClassRecords has been created in @baseclass and added to the "may start" activity ListEditor. Please add the privilege pxListClassRecords to access groups using ListEditor.
INC-187750 · Issue 675635
Error message removed for adding a new datatype to a branch
Resolved in Pega Version 8.7
Clicking 'add data type' for an application when no unlocked rulesets were available resulted in the error message "No unlocked Rulesets/Versions found that are valid for this record. Unlock at least one Ruleset/Version that can contain records of this type.". However, it was possible to create a data type by choosing branch. Investigation showed this message was added by the activity pzLoadTypeToBeAdded and is not needed: it has been removed from the step that appended the message when validating on click of submit.
INC-175672 · Issue 655809
ServicePackage thread handling improvements
Resolved in Pega Version 8.7
Work recently done to improve the release of requestor pool threads for the ServicePackage has been further enhanced by adding an explicit status notification to the thread waiting for Data Pages to be loaded in background and added support for the use case of a missing object handler.