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-A8445 · Issue 220085
Ensured display of empty user worklist section in hybrid client
Resolved in Pega Version 7.2
The user worklist section was not being displayed in the hybrid client if the login had no assignments (the WL(D_pyUserWorkList pxresultcount is zero) and the crewleaderworklist harness had a repeating dynamic layout. This has been corrected.
SR-A8217 · Issue 223611
Added server retry for push notifications in Sales Automation 7.14 / SFADevelopment for Android
Resolved in Pega Version 7.2
Push Notifications were not working on Sales Automation 7.14 / SFADevelopment for Android. This was traced to an error returned by the GCM server during registration, and the code has been modified to re-try the registration process if a failure is encountered.
SR-A12537 · Issue 224733
Optimistic locking honors OfflineEnabled function
Resolved in Pega Version 7.2
After upgrade, if a top level case type rule was checked out through the Case Explorer by opening the Case Designer and then changing the locking mode to Optimistic, the value reset back to Default after check-in. This was an issue with the pyOfflineEnabled setting being honored, and has been corrected.