SR-118528 · Issue 175205
Fixed server error alert generated by portal logout
Resolved in Pega Version 7.1.7
A "Server Error " error was being generated when logging off from "List views/Summary Views" in the Portal Dashboard. This occurred when the request to unload the page reached PRPC after the endsession completed and the request to unload was unable to find the associated session on the server as it has been already invalidated. The Wizard_MainWindow HTML rule has been modified to smooth the timing and clear the clipboard properly.
SR-118722 · Issue 175625
Excessive length of filter window corrected
Resolved in Pega Version 7.1.7
In work object Audit window, the History table -> Description column filter window is appearing very long. This was caused by an inadvertent change to the listview function in conjunction with the Time column filter, and has been fixed.
SR-118738 · Issue 172565
Handling corrected for drag and drop image attachments from Outlook
Resolved in Pega Version 7.1.7
If a document containing an image was added to a work object from Outlook via drag and drop, it would be corrupted when opened. This was caused by an encoding/decoding mismatch - the encoding differed depending on whether the file was first saved to the desktop or not, but the decoding did not take that into account. This has been corrected.
SR-82384 · Issue 93497
Fusion now shows tooltips for stacked data points of the same value
Resolved in Pega Version 7.1.7
Previously, FusionCharts did not support the feature of showing all the series names and values in tooltip if all the series have same value for a single category. While there was a workaround of providing the all series names with values as text in the "toolText" attribute of the element of the XML Data or by using stacked bar charts, FusionCharts now displays the tooltip for a single category series with the same value.
SR-94370 · Issue 119519
AddChildWork updated to allow child case creation from step flows
Resolved in Pega Version 7.1.7
When attempting to create nested sub cases for rows in a page list with a Split for Each sub flow by calling the pyCreateSubCases flow, an error was generated. There was a workaround of using a utility shape to call pxAddChildWork instead of a split for each calling pyCreateSubCases, but pxAddChildWork has been updated in order to allow creating child cases using the step page as the primary page and not always defaulting to pyWorkPage.
SR-113396 · Issue 162534
Smoothed background Bulk Processing processing
Resolved in Pega Version 7.1.7
If the setting for BPUnitsToProcessForeground is given as 0 in all cases, attempting to run Bulk Processing in the background failed and logged an "Index out of bound" exception in the system logs. To cover this condition, a check has been added to handle zero items in the foreground processing when running background Bulk Processing.
SR-113919 · Issue 170809
Made page displays consistent between Java versions
Resolved in Pega Version 7.1.7
"pxflow" pagegroup values in pywork page were being placed differently depending on the version of Java used in the environment. This was caused by a handling error in situations where there is no classname, and has been fixed.
SR-114882 · Issue 164513
Validation error display corrected for screen flow harness
Resolved in Pega Version 7.1.7
Inconsistencies were appearing in the error display on the harness of the screen flow. The issue was due to the "Allow errors" value being set to true even when "Save on last step" was unchecked. While there was a workaround of unchecking both "Allow errors" and "Save on last step" options, this has been fixed.
SR-115166 · Issue 169266
Embedded list views enabled in IAC
Resolved in Pega Version 7.1.7
While using IAC to render a PRPC harness via a gadget, the embedded list view was not being displayed and autocomplete was not functioning. This was traced to a rule defect that failed to carry over the "Web Enabled" checkbox for the content tab shortcut listview.
SR-117855 · Issue 171394
Resolved NPEs during case creation
Resolved in Pega Version 7.1.7
If a null pointer error was generated during the case creation process, all subsequent records being processed also generated the error. This issue occurred when adding and later removing work party data, and was found to be related to a stack trace not being generated for the reported issue and an attempt to index a change to a page that's no longer available. To correct this, a code change now handles the condition which caused the NPE (writes an index for a non-existent page and then skips it) then logs information for analysis.