INC-189933 · Issue 677798
Corrected deleting a ruleset with the refactor wizard
Resolved in Pega Version 8.7
In the case of Access Whens applied for the modification and deletion of any rule and data instance, the haveAccess() function was executed on a null page and resulted in a PRRuntimeError that caused Ruleset refactor to fail. This has been resolved.
INC-140789 · Issue 597799
Added handling for validation after inactivity
Resolved in Pega Version 8.4.4
A Validate rule was configured to add an error to a field if MyPageList had any page where MyProperty was not empty. The rule worked correctly if there was no pause in using the UI, but if the UI was left for a few minutes and then the field was changed, the Validate rule always evaluated the expression to true. This has been resolved by adding a null check in Utilities.countInPageList() function.
INC-143193 · Issue 595938
Handling added for UI overlap issue
Resolved in Pega Version 8.4.4
Elements of the window "Test Case Record Configuration" were shifted into one another when the Application name was too long that it overlapped with the other UI Elements. This has been resolved by adding a style sheet with overflow hidden.
SR-D43402 · Issue 509972
ValueList/Group correctly appears on clipboard
Resolved in Pega Version 8.2.5
After upgrade the property of type ValueList/Group was missing from the clipboard. This was traced to an extra 'when' rule applied on the visibility of Layout-2 in final section pzProperty (Pega-Desktop:08-02-01), and has been corrected.
SR-D49792 · Issue 515982
Corrected property mismatch in Create Eligibility condition builder
Resolved in Pega Version 8.2.5
A parameter mismatch in Create Eligibility condition builder was resulting in properties not being offered in the dropdowns as expected when the top level page was not CaseTypeStages or this page did not exist on clipboard. This has been resolved by changing CaseTypeStages.pyClassName to ConditionsParamterPage.pyClassName in the pzSelectValues_FieldType section.
INC-167037 · Issue 650991
SmartpromptType classes shown in Rule-Admin-Skill
Resolved in Pega Version 8.7
Some class instances were not showing in SmartpromptType list. This was traced to the activity LookUpList, which is called from Rule- class in Rule-Admin-Skill, using pyClassName as one of the filter criteria in Java Step1. Therefore Rule-Admin-Skills did not show in SmartpromptType list. This has been resolved by overriding LookUpList for Rule-Admin-Skill class so it will not consider pyClassName as a filter criteria.
INC-165256 · Issue 657037
Improvements for Offer Eligibility rules loading time
Resolved in Pega Version 8.7
After opening the Proposition filter/Action rule and clicking on Add Criteria, the pxAnyPicker drop down load was taking an excessive amount of time. Performance improvements have been made by adding a precondition at step 2 to avoid data page refresh for specific scenarios when it is not required.
INC-176542 · Issue 668478
Removed unused function to improve Class rule save performance
Resolved in Pega Version 8.7
Clicking save on the Policy Class rule was not working correctly or was taking an excessive amount of time to respond. Adding property mapping in the External Mapping tab of the Class rule exhibited the same behavior. Investigation showed there was an infinite loop being invoked in the class ruleform, which was traced to the disableKeyEntries() function. As this function is no longer used, this has been resolved by updating the RF_RuleObjClassScript.js to remove disableKeyEntries and any function calls to it.
INC-178872 · Issue 668306
Added handling for silent save fail with invalid cache
Resolved in Pega Version 8.7
When Commit threw an exception, the Save button from rule form did not catch it and returned no errors even though the save failed. Investigation found this could occur on systems with invalid caches, and a try-catch has been added to handle an exception occurring in a Java step that should not stop future processing.
INC-182152 · Issue 667396
Special character handling updated for export MapValue to Excel
Resolved in Pega Version 8.7
The Excel download was failing when the Row/Column definition or column configuration of a map value contained an equals sign (=) or < > brackets inside quotation marks. This has been resolved by adding an update that will evaluate the comparator value at the start of the row condition value, and row condition value and row condition operator will be set separately.