SR-130345 · Issue 199748
Added qualification to validation queue page creation
Resolved in Pega Version 7.1.8
After migration, executing custom business logic validation generated the error "There was a problem getting a list". This was due to the JS code generating an unqualified QueuePage, and has been resolved.
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-130401 · Issue 201418
Fixed listview filtering header shift
Resolved in Pega Version 7.1.8
When using a list view in a section with filtering enabled, applying any filter criteria caused the header to shift down vertically and create a gap. This was a display div error, and has been fixed.
SR-130401 · Issue 200029
Fixed listview filtering header shift
Resolved in Pega Version 7.1.8
When using a list view in a section with filtering enabled, applying any filter criteria caused the header to shift down vertically and create a gap. This was a display div error, and has been fixed.
SR-130421 · Issue 200325
Corrected double firing after copying trigger to superclass
Resolved in Pega Version 7.1.8
After copying a commit trigger from PegaSample-CustomerRequest to PegaSample and withdrawing the original, the new version fired twice on commit. This was caused by the RuntimeDeclarativeClassCore not properly handling the duplicate, and has been corrected.
SR-130429 · Issue 197603
Digitally signed legintwincapture.cab made available
Resolved in Pega Version 7.1.8
The use of legintwincapture.cab to install image capture on client workstations required "register server = yes" for PegaJpegLibrary15.dll, and the installer and components needed to be digitally signed and timestamped. The *.INF file in the installer has been modified to register PegaJpegaLibrary15.dll, and each Pega component has been signed and timestamped.
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.