SR-C61277 · Issue 402763
GRS values supported for pxTestEmailConnectivity activity
Resolved in Pega Version 8.2
After upgrade, the global parameter reference did not work in email accounts. This was an unintended consequence of recent email refactoring: although GRS values were being resolved in the activity and shown in the components tested section of the test connectivity gadget, they were not being passed to the pxTestEmailConnectivity activity. This caused the test connectivity to fail if the inputs configured in email accounts were in GRS syntax. To fix this, the SMTPConnectivity and POPorIMAPConnectivity activities of Data-EmailAccount class have been modified to add the GRS resolved values to an emailAccountPage which is passed as a parameter to pxTestEmailConnectivity activity.
SR-C25514 · Issue 392195
Special character handling improved to ensure MTOM binary contains all data
Resolved in Pega Version 8.2
The presence of special characters was causing the data to be truncated when moving XOP elements in the SOAP envelope and encoding them into multi-part binary elements (MTOM). This was traced to Connect SOAP With MTOM Option missing some content in the Response data particularly in conjunction with Websphere using a specific JDK version, and has been resolved by modifying the setOptimizeOnChildren method in PRServiceUtilsPriv class to to get all the content.
SR-C33657 · Issue 401228
Connector and Metadata wizard skip of renaming classes works for very large metadata in Chrome
Resolved in Pega Version 8.2
When using the Connector & Metadata wizard to generate Data mapping rules for Java Bean metadata with an imported jar containing a large number of metadata (over 5000 classes and properties), clicking on the option to skip renaming of classes and properties caused the browser to hang. This was traced to legacy code which was not efficient enough to handle this volume, and modifications have been made to avoid unnecessarily overloading the DOM and triggering onclick addEventListener events multiple times. This reworked skip function works smoothly with Chrome, but as yet does not work with the IE browser due to legacy coding and browser incompatibility issues.
SR-C56744 · Issue 402693
Activation function of RadialBasis now supported in the PMML engine
Resolved in Pega Version 8.2
An enhancement has been added to extend the scope of the neural network evaluator to support RadialBasis Activation function.
SR-C82749 · Issue 419557
Improved security for XXE
Resolved in Pega Version 8.2
Several updates have been made to improve security against External Entity Injection.
SR-C53056 · Issue 398514
Bulk delete updated and NPE handling improved to resolve deadlock when loading data flow landing page
Resolved in Pega Version 8.2
A large number of data flow objects on the data flow landing page were making the system unresponsive, and bulk delete activity would sometimes fail on a null pointer exception when progress could not be retrieved. To resolve this, the bulk delete activity provided in [Data-Decision-Service] pyDeleteByStatusAndTime has been modified to be more flexible by allowing deletions based only a date or a status, and the documentation for the activity itself has been improved. Additional handling was added for a potential null pointer exception, and the activity will continue trying to delete other runs if a null pointer exception does occur. The system will not load a data flow run object anymore (which can cause issues when rules do not exist), and will instead load the run progress directly from the database.
SR-C53650 · Issue 407317
Pega_validators JS updated to resolve popup issue with IE11
Resolved in Pega Version 8.2
A browser popup was not displaying as expected in IE11. This was caused by IE11 not supporting the "startsWith" method, and has been resolved by replacing if (errorElementClass.startsWith("Radio")) with if (errorElementClass.indexOf("Radio") == 0) in the pega_validators.js file.
SR-C53659 · Issue 414799
Location paramter passing corrected to resolve portal switch/refresh error
Resolved in Pega Version 8.2
Switching the portal and refreshing the browser was generating a system administrator error due to the location parameter not being passed correctly. This has been fixed by passing location parameter from pxCaseMgrHeader.js instead of forming it in the activity.
SR-C53719 · Issue 402222
DateTime date format inherited from locale to present in expected format
Resolved in Pega Version 8.2
Section pxStatusQueueItems from System Operations > Queue Management landing page were defaulting to the USA month-day-year order instead of using the format for the assigned locale (or windows locale if empty) of day-month-year. This was caused by the DateTime controls on the Admin Studio using the specific format to display the DateTime properties: this has now been modified to use 'control inherited from property' to display as per locale.
SR-C53820 · Issue 401241
DateTime control updated to handle invalid date entry when validation is turned off
Resolved in Pega Version 8.2
After turning off client side validation, trying to update a date in a date time control using the wrong format resulted in that day's date being used. If the client side validation is turned on, entering the date in the wrong format results in a validation message. This was caused by a missed use case for an invalid date entry not being validated, and has been corrected.