SR-130526 · Issue 200786
Modified 'save as' to update workgroups across nodes
Resolved in Pega Version 7.1.8
On a multi-node environment, 'Bulk Actions' was not showing all of the workbaskets after a product rule with a workbasket data instance was imported to one node and not others. This was a lookuplist cache issue caused by 'save as' not updating the workgroups, and has been resolved.
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-130696 · Issue 199065
Updated config query for VBD date/time support
Resolved in Pega Version 7.1.8
When following the recommendation to add required date-time columns on VBD configuration tables for Oracle Golden Gate set up, the VBD configuration could not be saved to a database table from PRPC. This has been resolved by adding an updated configuration query to support replication.
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-130731 · Issue 198828
HTTPS support added to DSM applications
Resolved in Pega Version 7.1.8
If the PRPC instance is accessed via HTTPS and the DSM applications (ADM & VBD) are installed on the same Tomcat configurations, the DSM services landing page did not provide the ability to say if the services were accessible via HTTPS. This is now possible through an added configuration option on the landing page to enable secure connection.
SR-130751 · Issue 198798
Clarified handling of unlocked work objects in multinode environments
Resolved in Pega Version 7.1.8
Release lock was not working correctly on a multinode environment. When trying to release the lock from same operator different requestor from different nodes, the error "Unable to unlock this work object" was generated. In a multinode environment, system pulse takes time to update the cache across the nodes, hence the option is not effective immediately. Messaging has been updated to reflect this delay. Once System pulse executes then other requestor will be able to work on this item.
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.