SR-130269 · Issue 197947
SmartInfo call updated for Listview in standards mode
Resolved in Pega Version 7.1.8
After upgrade, instances of SmartInfo configured on listview showed improper styles. This was due to the older version of the SmartInfo control being used when the document was in standards mode. The listview function has been updated to use the updated SmartInfo control for proper rendering.
SR-130363 · Issue 200006
Dynamic decimal place value setting added
Resolved in Pega Version 7.1.8
Previously, the 'pxNumber' control had Decimal Places set to 2. This setting became Auto in ML7, which resulted in no decimal values being displayed for whole numbers in some installations with custom settings after upgrade. To facilitate overriding this out-of-the-box function, a dynamic setting has been added: create a dynamic system setting rule with purpose "DecimalPlacesforpxNumber" in the ruleset "Pega-UMicrosoft Internet Explorerngine" with a given value from -1 to 10, and it will override the Auto value in the pxNumber control decimal places setting.
SR-130563 · Issue 201651
Resolved script errors for dynamic container refresh
Resolved in Pega Version 7.1.8
When a screen designed with Tab Group and Dynamic Container was refreshed through Button/ModalWindow/f5, a JavaScript error was generated and the buttons were not clickable. To correct this a null check will be performed while initializing tabs.
SR-130604 · Issue 198248
Improved handling of load balancer cookies
Resolved in Pega Version 7.1.8
When going through the load balancer and custom authentication, two Pega-RULES cookies were being added to the requests as the user progressed through using the application and errors were displayed on the login screen for subsequent sessions. One of the Pega-RULES cookies was from the previous user session, and a file cookie was being added at the browser level that contained the Pega-RULES cookie. This was an issue where if the responseheader object had a iac-nongateway string in lower case when run through load balancer (like webseal or cisco f5), it collected the second cookie due to the case mismatch in the API. The system has been updated to shift the case of the responseheader object name to better handle differences related to various load balancing applications.
SR-130655 · Issue 198806
Validation handling improved for date value
Resolved in Pega Version 7.1.8
When a value was provided from the Calendar Icon, the value was not going to the clipboard automatically from pxDateTime control when the "Enable client side validation" checkbox was not checked in the advance tab of the harness. The pxDateTime control should not have been relying on the client side validation, and this has been corrected.
SR-130671 · Issue 198217
Sort and filter check added for embedded sections in repeat grid columns
Resolved in Pega Version 7.1.8
In a repeat grid where sort and filter options were enabled on all the columns and one of the columns contained an embedded section, the sort and filter functions were not working on the column with the embedded section if the name of the embedded section was the same as the name of any property used for other column in the repeat grid. This issue was due to an incorrect call to pzGenerateControl for the cell containing the section include, and has been fixed by adding a check for section includes.
SR-130713 · Issue 200675
getComputedStyle API issue in Microsoft Internet Explorer 8 resolved
Resolved in Pega Version 7.1.8
A JS error was appearing when using the Microsoft Internet Explorer 8 browser to complete the verification steps to submit a Smart Dispute, and clicking on the Submit button on the dispute screen showed no response. This was an issue with the updateHeaderCellsWidth API, and has been resolved.
SR-130796 · Issue 197804
Enabled restore of persisted Application requestors
Resolved in Pega Version 7.1.8
Prior to this change, service requestors could not be restored from their passivated state because of a code change introduced in PRPC 5.4. This was generally not a problem for most customers, as service requestors tend to be stateless and short-lived. Stateful, long-lived service requestors such as Verizon do need to be restored to their previous state, however. This change retracts the prior fix that prevented that from occurring.
SR-130815 · Issue 199482
Updated API for 'Find' gadget
Resolved in Pega Version 7.1.8
The 'Find' gadget was not opening the existing WO in a new window as desired. This issue has been fixed by changing the strItemID location so that it will be passed to createFromEncryptedURL API.
SR-130959 · Issue 201417
Resolved stack overflow error on click close
Resolved in Pega Version 7.1.8
If a local action is configured on click of button in a section and a flow action is opened in the modal dialog, checking the option "Hide the default Action Section buttons?" in the action tab of flow action caused a stack overflow error when the X button was clicked to close the modal dialog. This has been fixed by adding a condition in focusOnModalDialogFirstElement to avoid refocusing on container_close when the modal does not have focusable elements.