SR-A619 · Issue 205442
Page Messages displayed on dropdown after render
Resolved in Pega Version 7.1.9
When submitting a flow action that contains a dropdown control and which is configured to load its values after the screen renders, Page Messages were not displayed when the flow action was re-displayed. This was caused by "pzKeepPageMessages" not being set to "true" while sending the ajax request to fetch drop down options (for render after screen/load on hover), and has been corrected.
SR-A642 · Issue 206621
Enabled section autogeneration from HTML to JSP
Resolved in Pega Version 7.1.9
Effective with Pega7, section generation was changed from HTML(pyJavaGenerateAPIVersion = 04-01) to JSP(pyJavaGenerateAPIVersion = 04-02). This caused an issue with some migrations from earlier versions that were not able to make the mandatory switch from HTML to JSP generation due to a missing option in the section ruleform. The option to upgrade from HTML to JSP had been configured from within "pyAutoHTML = false", meaning that this option appeared only for non-autogenerated sections. To resolve this, the option "Generate for" in the section Rule-HTML-Section.pzRuleFormHTML is now available irrespective of whether pyAutoHTML is set to true or false.
SR-A681 · Issue 205448
Added handling for empty section name in reload
Resolved in Pega Version 7.1.9
A Null message was sporadically displayed when hovering over a row instead displaying the SmartInfo section or a loading icon. This was caused by an empty section name in the reload section ajax, and handing for this has been added to the SmartHarness API.
SR-A833 · Issue 204781
Fixed Google Chrome 43 population of Dynamic Select and Menu control
Resolved in Pega Version 7.1.9
When using Google Chrome Version 43.0.2357.81 m, no values were shown in the Dynamic Select drop down list or in the Menu control. This was due to an uncaught exception for this browser in the JavaScript code which has now been addressed.
SR-A91 · Issue 205459
Added expand on click logic to check for layouts collapsed on open
Resolved in Pega Version 7.1.9
The ?Expand/Collapse? click event was not working on the first click if all layouts/sections were initially collapsed on open. This was due to the logic used to determine the state of the layouts, and an additional check has been inserted to handle scenarios where the layouts/sections are collapsed on-load.
SR-A2640 · Issue 207012
Corrected field limit size on mobile
Resolved in Pega Version 7.1.9
When using an Android mobile device, the max number of characters for an input field was not being honored. This has been corrected.
SR-A3072 · Issue 204300
Attachment visibility fixed for mobile devices
Resolved in Pega Version 7.1.9
When attachments were uploaded to a mobile device, they were not immediately visible and required a refresh to be displayed. This was found to be an issue in the signature control and Attach content control where the data page referred to in the attachments display was not removed when a new attachment is added. For this release, the data page removal part has been moved to the saveattachment activity. In the next release, all attachment controls will call an API designed for that purpose.
SR-A3072 · Issue 204019
Attachment visibility fixed for mobile devices
Resolved in Pega Version 7.1.9
When attachments were uploaded to a mobile device, they were not immediately visible and required a refresh to be displayed. This was found to be an issue in the signature control and Attach content control where the data page referred to in the attachments display was not removed when a new attachment is added. For this release, the data page removal part has been moved to the saveattachment activity. In the next release, all attachment controls will call an API designed for that purpose.
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.