SR-118415 · Issue 172879
Ensured Application Document wizard captures all subflows
Resolved in Pega Version 7.1.7
The Application Document wizard was documenting only some of the flows that were expected to be included. This was caused by an incorrect null check on the input parameters which treated the subflows as duplicate flows, and has been updated.
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-119030 · Issue 172922
Clipboard privileges tightened to enhance security
Resolved in Pega Version 7.1.7
Using standard browser development tools, it was possible to insert a client-side modification into a Pega-served HTML page to allow a customer to access partial clipboard inspection functionality. To correct this, starting activity privileges have been tightened.
SR-119095 · Issue 174195
TagCloud rendering corrected
Resolved in Pega Version 7.1.7
When opening pxTagCloudViewGadget it generated the error: 'Unable to open an instance using the given inputs: pxObjClass = "Rule-Obj-Report-Definition", pyClassName = "", pyStreamName = ""' . The tag cloud gadget reported "Can not render @baseclass.pxTagCloudInit", and when run or included in a section, it did not render any tags. This was found to be a design time error in Obj-Open of the report definition, and has been fixed.
SR-119538 · Issue 177397
Detection added for custom work history tables
Resolved in Pega Version 7.1.7
In order to fully embrace mobile capabilities, columns were added to the work history tables to allow actions to be tracked as a geographical map where each history event is a numbered locale indicator on a map instead of a row of entries. From lat/long it is also possible to call a Google service and get the street address as well. However, this functionality caused some issues post-migration with if there were customized pc_history_work tables mapped to custom classes. To remedy this, a check has been added to only query for pxlatitude/pxlongitude if columns are exposed and shown, and that will detect if the columns aren't present.
SR-119869 · Issue 176176
Access Role Editor link errors fixed
Resolved in Pega Version 7.1.7
When using IE11 or Google Chrome, clicking on the hyperlink to a privilege associated with a class in Access Role Editor created issues that prevented changes from being made or saved. In some cases, after clicking 'Remove Checked' in the popup dialog, the developer portal loaded in the popup. This was caused by the forms-based role selection not being converted for cross-browser support, and has been fixed.
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.