SR-C35967 · Issue 404321
Updated parameter handling for SECU0001 alert for accuracy
Resolved in Pega Version 8.2
In the SECU0001 alert, some fields contained incorrect values pertaining to a previous HTTP request, not the one that caused the alert, causing misleading information to be logged and sent to PDC. This was found to be an issue where when unexpected properties were found, the alert was being thrown from an early stage of processing, i.e, during inputProcessing where the current activity had not yet been set to the requestor state and therefore the current activity was not there in the stack frame. This has been addressed by getting the activity name from the HTTP request parameters and updating the diagnostic information with it so the alerts will be accurate.
SR-C71043 · Issue 411254
pzSendEmail returned to revious behavior of sending separate emails to work parties
Resolved in Pega Version 8.2
After upgrade, a change in behavior was seen when using the pzSendEmail activity. When pzSendEmail was called to send emails to work parties, a single email is sent to all recipients instead of separate emails to each recipient as it did in earlier versions. The SendSimpleEmail activity accepts a SendDiscreteMails parameter, the pzSendEmail activity has 'Pass current parameter page' checked so the default value for the SendDiscreteMails parameter was not used. This was a backwards compatibility error, and has been corrected by setting the SendDiscreteMails parameter to true by default in the pzSendEmail activity.
SR-C68500 · Issue 411293
Node ID correctly transmitted for PEGA0066 Alerts
Resolved in Pega Version 8.2
The PEGA0066 alert containing information about synchronization errors or connection lost did not contain the correct value in the Node ID field, causing PDC to not be able to handle the alerts on mobile. This has been corrected.
SR-C66283 · Issue 411633
Report Usage updated to always fully populate statistics regardless of page source
Resolved in Pega Version 8.2
After creating a report under the Log-ReportStatistics class, it was seen that reports under report usage were not reflecting the exact data. The inconsistency observed with embedded reports was due to grids being sourced by virtual RD, for which the report page had already been loaded elsewhere. In this case it was assumed that the statistics were already populated because the report page was already loaded. To ensure that reports are consistently accurate, pxRetrieveReportData has been updated to always call pzPopulateStatisticsInfo.
SR-C70757 · Issue 411813
Added null check to resolve error when using datapage as dropdown source
Resolved in Pega Version 8.2
The user application was hanging with the browser console error "Uncaught SyntaxError: Unexpected end of JSON input" when using Dropdown controls with Datapage as a source in conjunction with parameterized datapages to create a cascading second dropdown. This did not happen when using any other data sources for the same control dropdown. This has been resolved by adding a null check at the reloadcell response.
SR-C70539 · Issue 412234
Open API passes 'true' for aUnlockOnCommit parameter to minimize pr_sys_locks table filesize
Resolved in Pega Version 8.2
The Archive/Purge Wizard was not removing the locks acquired during the execution from the pr_sys_locks table, resulting in locks remaining in the table for up to three days. This could potentially cause an enormous filesize and lead to other processes failing to acquire locks due to contention on the table. To resolve this, the system will pass 'true' for aUnlockOnCommit parameter on the open API so that the lock is released on commit of the deferredDelete on purged instances.
SR-C72114 · Issue 413597
Updates to controls and labels
Resolved in Pega Version 8.2
Issue 413604:When configuring a button with a disable condition, the condition was not returned in the readonly field. The PegaAPI has now been updated to support "disable". Issue 413597 / 413598: While calling the API to get the view of the screen as a JSON format, button type controls were not returning the label of the field using the OOB pxButton control. This has been fixed. Issue 413625: The PegaAPI section was missing when using clipboard page or data page with the rest method. To correct this, support for Embedded page has been added in the pyWorkPage for PegaAPI.
SR-C65438 · Issue 406709
Added SAML parameter page generation for local use to bypass null auth object
Resolved in Pega Version 8.2
After defining any step which used parameters in the Post authentication activity of a SAML authentication service, the authentication failed with a java.lang.NullPointerException at com.pega.pegarules.session.internal.mgmt.Executable.putParamValue(Executable.java:3030). This was traced to local logic inserted to iterate through the SAML attributes that used a null parameter page. To resolve this, code has been inserted that will generate a new parameter page for the iteration rather than getting it from the authentication object.
SR-C69302 · Issue 407177
Support added for local datacenter only keyspaces for Cassandra
Resolved in Pega Version 8.2
In order to support multi-datacenter system (one Pega system) that spans two data centers but avoids the latency of attempting to connect from a node in data center 1 to a Cassandra node in data center 2, an enhancement has been added by way of the system setting dnode/cassandra_local_datacenter_keyspaces which allows specifying only local datacenter keyspaces as comma separated string. The default behavior is not changed.
SR-C71290 · Issue 410122
Removed automated cleanup of old DSS entries to resolve memory issue
Resolved in Pega Version 8.2
VBD was issuing an expensive query while attempting to clean up old DSS entries. The old entries were dynamically created with node ID as part of the setting key (vbd/pulse/{nodeid}, and vbd/cluster/{nodeid}). The cleanup logic attempts to get the list of all matching keys to delete by iterating the list of system settings and grabbing the ones that match these patterns. On some systems, there are enough system settings in the DB that it resulted in a memory issue. To avoid this issue, the automated cleanup process has been removed.