SR-A10768 · Issue 224245
Delegated rules open from portal favorites
Resolved in Pega Version 7.2
After upgrade, a custom portal containing favorite rules (similar to the previously available "MyRules" in the operator menu) was not able to open the rules due to changes in the 'when' rules visibility conditions of the rules delegation feature for dynamic layouts. To resolve this, the system now contains the new 'when' rule "@baseclass.pyDelegateHeader" to be used in conjunction with the 'when' rule for the visibility condition in dynamic layout 1 2 and 3 in the "@baseclass.pzRuleFormKeysAndDescription" section.
SR-A13028 · Issue 229030
History snapshots include upgrade information
Resolved in Pega Version 7.2
After migration, snapshots of a rule's history showed without any preconditions and transitions. Expanding the When/Jump portions of a step and selecting "Enable conditions" would display the rules that were there. This was an issue with UpgradeonOpen activity not being called when opening a snapshot, and a conditional call to UpgradeonOpen activity from DisplayOldVersion has been added to set the correct properties and display the ruleform in the correct state.
SR-A6369 · Issue 214289
Excel Macro for Decision Tables and Map Values certificates updated
Resolved in Pega Version 7.2
The digital signature associated with Macros of Declare table and Map value rule for Excel have been resigned with latest certificates to extend the expiry date. The respective rules(Excel Template rules) are 1) Rule-Obj-MapValue ? Edit Default 2) Rule-Declare-DecisionTable ? Edit Default
SR-A2578 · Issue 216798
Edit in Excel updated for Microsoft Internet Explorer 11
Resolved in Pega Version 7.2
When using Microsoft Internet Explorer 11, clicking on the "edit in Excel" feature of a decision table rule form allowed the editing but then did not pass on the changes from Excel to back to the rule form. This was a browser version issue: previous versions of Microsoft Internet Explorer did not require explicit event listeners for openauthoring, but Microsoft Internet Explorer 11 made them mandatory. The listeners have now been added for use with Microsoft Internet Explorer 11.
SR-A1140 · Issue 215419
Edit in Excel updated for Microsoft Internet Explorer 11
Resolved in Pega Version 7.2
When using Microsoft Internet Explorer 11, clicking on the "edit in Excel" feature of a decision table rule form allowed the editing but then did not pass on the changes from Excel to back to the rule form. This was a browser version issue: previous versions of Microsoft Internet Explorer did not require explicit event listeners for openauthoring, but Microsoft Internet Explorer 11 made them mandatory. The listeners have now been added for use with Microsoft Internet Explorer 11.
SR-A7948 · Issue 219750
Edit in Excel updated for Microsoft Internet Explorer 11
Resolved in Pega Version 7.2
When using Microsoft Internet Explorer 11, clicking on the "edit in Excel" feature of a decision table rule form allowed the editing but then did not pass on the changes from Excel to back to the rule form. This was a browser version issue: previous versions of Microsoft Internet Explorer did not require explicit event listeners for openauthoring, but Microsoft Internet Explorer 11 made them mandatory. The listeners have now been added for use with Microsoft Internet Explorer 11.
SR-A7205 · Issue 218612
Rule history included in save-as
Resolved in Pega Version 7.2
After upgrade, using "save as" on a rule from a particular version was not maintaining the rule history correctly. Information was not included about the version from which it was being saved (previous version and ruleset, but did display the check-in comments. This was traced to an error with passing the History Memo as parameter when calling the SaveAs activity, and has been fixed.
SR-A7205 · Issue 219651
Rule history included in save-as
Resolved in Pega Version 7.2
After upgrade, using "save as" on a rule from a particular version was not maintaining the rule history correctly. Information was not included about the version from which it was being saved (previous version and ruleset, but did display the check-in comments. This was traced to an error with passing the History Memo as parameter when calling the SaveAs activity, and has been fixed.
SR-A12345 · Issue 224099
Improved visibility for roles associated with objects
Resolved in Pega Version 7.2
Issues were encountered while attempting to access roles associated with objects on the access role name rule form if 'Rule-Access-Deny-Obj' was used. Not all of the ARO and ADO definitions for the Access role were visible and the error "Failed to find a 'RULE-OBJ-FLOWACTION' with the name 'PZADDMODIFYROLE' that applies to" was generated. This has been corrected by adding and updating the required rules to support displaying both Access role objects and access deny objects on access role name rule form: the grid will be updated to display both RARO and RADO, but to simplify, the add-a-row functionality at the bottom will be limited to RAROs only.
SR-A8289 · Issue 218291
Improved visibility for roles associated with objects
Resolved in Pega Version 7.2
Issues were encountered while attempting to access roles associated with objects on the access role name rule form if 'Rule-Access-Deny-Obj' was used. Not all of the ARO and ADO definitions for the Access role were visible and the error "Failed to find a 'RULE-OBJ-FLOWACTION' with the name 'PZADDMODIFYROLE' that applies to" was generated. This has been corrected by adding and updating the required rules to support displaying both Access role objects and access deny objects on access role name rule form: the grid will be updated to display both RARO and RADO, but to simplify, the add-a-row functionality at the bottom will be limited to RAROs only.