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.
SR-A6547 · Issue 217014
Updated handling for empty keys in DataSet-Execute
Resolved in Pega Version 7.2
When executing a 'delete by keys' operation in a DataSet-Execute method, passing empty keys would intermittently cause the whole dataset to be truncated or deleted. To create a more robust execution environment, when a Dataset-Execute is called and no key is passed it will trigger a delete statement matching the key value to null.
SR-A6629 · Issue 216162
Updated group authentication for populating Batch Processing landing page
Resolved in Pega Version 7.2
pyApplication and pyApplicationVersion were not getting populated when running a data flow from the Batch Processing landing page that used information from system pages. This was an issue with the system pages not being included in the proper authentication group, and has been resolved.
SR-A8103 · Issue 216452
DSM thread CPU consumption resolved
Resolved in Pega Version 7.2
In certain installations, a DSM thread that was not properly sleeping after the system was upgraded caused degraded performance. This has been corrected.