SR-A7256 · Issue 218467
Flow image resolution now set by default
Resolved in Pega Version 7.2
In some flows with widely spaced shapes, the resolution of the flow image was insufficient- i.e., the text inside the flow shapes is not legible. The flow image is captured at a user defined zoom level, causing the captured flow images to have non-uniform resolution. The image capture now is done at a default origin and zoom level. The image capture will then restore the user selected zoom level after the capture happens.
SR-A9615 · Issue 218861
Resolved NPE in batch processing Decision data flows
Resolved in Pega Version 7.2
A null pointer exception was being thrown when accessing the batch processing function for Decision data flows if the 'initservices/dnode' dynamic system was set to false. This was traced to a failure of the Flow Action pre-processing activity attempting to call DNodeServiceListener to initialize it, and a check has been added so the Data flow run manager will now try to initialize each time it is asked for an instance if it was not initialized already.
SR-A733 · Issue 207631
Edited Propositions retain format
Resolved in Pega Version 7.2
When updating a Proposition using the "Edit" button, the format was lost, however updating the proposition using the "Bulk Edit"-> 'Edit in Excel' button preserved the formatting. This has been addressed by making the default UI control for the text values a Text Area, which maintains the multi-line format.
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.