SR-120809 · Issue 180066
Clarified clipboard API mapping of "null" JSON values
Resolved in Pega Version 7.1.8
In order to support JSON where optional properties with unknown values are included and set to null (rather than being omitted), the API method ClipboardPage.adoptJSONObject has been updated to omit occurrences of null in the JSON source rather than setting them to a text value of "null" for that property on the clipboard.
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-120899 · Issue 183642
Work object history corrected for failed flow action submissions
Resolved in Pega Version 7.1.8
If a a flow action is submitted which encounters errors and generates Page-Messages, correcting the errors and re-submitting the flow action created duplicate entries in the work object history that included entries for the failed flowaction submission. This was caused by improper rollback of the addhistory when the commit of the WO is rolled back, and 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-120951 · Issue 179944
Improved system performance when logging errors in PUI framework
Resolved in Pega Version 7.1.8
When using the PUI framework (Pega Underwriting for Insurance), errors generated when trying to execute a Declare Expression were causing system slowness. The logic has now been modified to more efficiently match and log any errors.
SR-120977 · Issue 180096
File extension type now visible in the audit trail for attachments
Resolved in Pega Version 7.1.8
After files were uploaded and attached, it was seen that only the file name itself was found in the audit trail and there was no extension given. In order to pass the attachment file type extension, the pynote value will be passed as a parameter to the pyHistoryMemo FileAttached field value, and written to the audit.
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-121050 · Issue 179650
Corrected double results from Property-Map-DecisionTable
Resolved in Pega Version 7.1.8
When using a Property-Map-DecisionTable method in an activity, the generated java contained two calls with the keyword and resulted in an empty entry as well as the desired entry. This was caused by the introduction of optimized property set logic in the expression parser, but certain expressions partially bypassed the optimization. While there was a workaround of refactoring the activity to use a Page-New step with the tag in a method step before the Property-Map-DecisionTable and then changing the PropertyName for the from to to prevent the extra page from being created, this defect has been resolved.