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.
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-121112 · Issue 179088
Step names localized in Stage and Steps display
Resolved in Pega Version 7.1.8
Previously, Step names in the Stage and Steps display were not localized under the ButtonLabel Field Value rules in the same way as the Stage names. This was due to the title being derived from the control "StageProcessLink", which is a non-auto generated control being directly fetched in the HTML markup instead of querying the getLocalizedText method. This has been changed to allow Step names to be included in localization as expected.
SR-121115 · Issue 183812
Added optional setting for handling blank localization settings
Resolved in Pega Version 7.1.8
Previously, a blank localization value was carried forward as a blank value. This behavior was changed in Pega7 to have the localization API Executable#getLocalizedText return the Label itself. In order to maximize usability going forward, an API has been added that allows either behavior based on local settings. This is accessible as PublicAPI.java getLocalizedTextForString (String aRef, String aString,boolean aReturnEmptyForLocalisedString) To use the API to carry the empty value, pass "true" to aReturnEmptyForLocalisedString parameter. The API will then return the localized string in the field value as-is i.e it will return an empty string if the localized string is empty.
SR-121115 · Issue 182793
Added optional setting for handling blank localization settings
Resolved in Pega Version 7.1.8
Previously, a blank localization value was carried forward as a blank value. This behavior was changed in Pega7 to have the localization API Executable#getLocalizedText return the Label itself. In order to maximize usability going forward, an API has been added that allows either behavior based on local settings. This is accessible as PublicAPI.java getLocalizedTextForString (String aRef, String aString,boolean aReturnEmptyForLocalisedString) To use the API to carry the empty value, pass "true" to aReturnEmptyForLocalisedString parameter. The API will then return the localized string in the field value as-is i.e it will return an empty string if the localized string is empty.