SR-120781 · Issue 177810
Changed close modal icon text for JAWS
Resolved in Pega Version 7.1.8
If focus is given to the X icon on the modal dialog, JAWS was reading "Unlabeled 2 Button." In order to indicate that it is the Close modal icon, the title="close modal" has been added to the modal dialog's X button.
SR-120876 · Issue 185865
Required date properties now working correctly in modal windows
Resolved in Pega Version 7.1.8
Marking a date property as required in a modal window was not actually setting the property as required. The problem was traced to a missing comma between 'date' and 'required' in the validationtype attribute on the field when there is an edit input associated. This datetime issue has been corrected.
SR-120876 · Issue 183543
Required date properties now working correctly in modal windows
Resolved in Pega Version 7.1.8
Marking a date property as required in a modal window was not actually setting the property as required. The problem was traced to a missing comma between 'date' and 'required' in the validationtype attribute on the field when there is an edit input associated. This datetime issue has been corrected.
SR-120946 · Issue 180460
Ensured custom formats for dynamic layouts appear consistently
Resolved in Pega Version 7.1.8
Custom formats for Dynamic Layouts in an application skin were not appearing after upgrade. This was caused by stale code related to alignment issues, and has been resolved.
SR-121016 · Issue 179993
JMS handling enhanced for complex custom environments
Resolved in Pega Version 7.1.8
When a JMS message is created, a temporary JMS response queue is also created on the fly. The JMS response queue has a timeout parameter associated. After PRPC has consumed a message from the destination, it retrieves the response parameters from the message header and posts a JMS message to the temporary response queue to complete the cycle. In some complex custom environments, PRPC was not able to send a response message before the response queue timed out and an error was generated. In order to handle these situations, the JMS Listener has been modified to always close MDB response connection before continuing.
SR-121048 · Issue 192690
Corrected dynamic select refresh behavior
Resolved in Pega Version 7.1.8
When a Dynamic select with "OnChange + refresh" was configured, the values in dynamic selects were not retained after a refresh in the Google Chrome and Firefox browsers. This occurred most often when selecting a value for a second dynamic select box caused a refresh and forced the previously selected value to be lost from the first box. The values were reset to "Select.." and the drop values were also not populated. The root cause of this problem was trailing white spaces in the values returned by the service that populated the dynamic select. While Microsoft Internet Explorer automatically trimmed these spaces, Google Chrome and Firefox did not. This has been corrected by trimming results when getting data from xml in the DynamicSelect JavaScript file.
SR-121104 · Issue 184148
Enhanced security for SQL exceptions errors
Resolved in Pega Version 7.1.8
In order to avoid a potential security vulnerability, the error messages generated by database exceptions have been made consistent for DB2 and Oracle and do not display SQL information in the log.
SR-121105 · Issue 180175
Corrected text wrapping for attached notes
Resolved in Pega Version 7.1.8
When using out-of-the-box functionality for attaching a note, the text was not wrapped and showed in one long line. The root cause of this problem was the "pre" tag in the HTML not breaking the lines and not wrapping, and styles have been added to fix the attachment issue.
SR-121126 · Issue 184375
Corrected handling for properties in XML rule
Resolved in Pega Version 7.1.8
When using properties mapped on the root element of an XML SOAP rule, the attributes were mapped properly but the element value was not. In a related error, after giving ParseXML rule invocation values for Type Substitution for Parse XML, the XML was not mapped to the clipboard for the type substituted elements. There was a workaround of using DSS 'switchtooldassembler', but this has been fixed by updating parsexmlsaxrulewrapper.
SR-121200 · Issue 184842
DB2 DateTime conversion fixed
Resolved in Pega Version 7.1.8
After inserting date values in DB2, using the select command and retrieving the above date values using RDB-List returned the date as one day earlier. The root cause of this issue was the logic used for reading and writing date columns in DB2. The logic was implemented in order to ensure that the values in the column were both saved and retrieved in GMT time zone. However, when a java.sql.Date object was retrieved from the JDBC metadata, it was returned as the date value at the time of Midnight, and the time zone was set to the local time zone by the metadata (instead of the expected GMT time zone). When preparing to return this value, the Date object was formatted with reference to GMT, which causes the Date object to have an hour subtracted and report a date value that was one day less than expected. To fix this, the datetime logic for the Date columns has been modified to use a DateFormat object in the system's local time zone.