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.
SR-A8236 · Issue 217418
Removed default overriding threads per node setting of Topology page
Resolved in Pega Version 7.2
The number of threads per node specified in Decision->Simulation Settings->Topology landing page was not being taken into account by the data flow execution, leading to the inability to configure vertical scalability per PRPC node and/or exclude certain nodes from data flow execution. This was traced to a default value overriding the setting from this page, and the code has been updated to correctly reflect the setting being used.
SR-A8099 · Issue 216453
Null/empty values removed from propagation instead of being set to 0
Resolved in Pega Version 7.2
Numeric properties without a value set were being propagated as value 0 during data flow execution. This was due to a clipboard page error in the Data Flow batch run execution, and this has now been updated to to ensure null or empty properties will not be propagated in the data flow.
SR-A10599 · Issue 221392
Privilege handling added for PAD split-scheme database setup
Resolved in Pega Version 7.2
in the "Predictive Analytics Director Settings" landing page, designating the internal Database to an external database rule caused the landing page to hang and an error was logged. This was caused by a lack of privileges for the Database user associated with PAD. PAD needs privileges to create, update, delete, select and insert. In cases where the user is associated with no privileges, PAD failed to create tables in the first instance. if the config was changed, PAD tried to check if any open projects were present and would fail again because of privileges and lack of tables. To correct this, additional handling has been added: A user who has insufficient privileges will generate an exception and the user will not be able to make any PAD operations. A user switching from an insufficient privileged user to a privileged user will need to re-login. Newly granting privileges to a insufficient privileged user and relaunching the portal will not allow user to create projects: the server will need to restarted to take the changes into account.
SR-A9936 · Issue 222962
Handling added to check for Snappy library for DNodeBootstrap
Resolved in Pega Version 7.2
The initialization of DNodeBootstrap at PRPC startup was generating an error if Snappy (a native library for Linux OS and ppc64 arch) was not present. To resolve this, handling has been added to check whether the Snappy library can be initialized.