SR-117606 · Issue 173816
Fixed portals enhanced for IE10 and IE11
Resolved in Pega Version 7.1.7
An enhancement has been added to the system to ensure portals will render accurately in IE10 and IE11.
SR-117674 · Issue 170571
Smart Shapes use properly limited to work class
Resolved in Pega Version 7.1.7
An error in the code made Smart Shapes visible when creating a data-class flow. Attempting to include them by dragging them into the flow design pane resulted in an "empty" utility shape that was missing many of the options normally offered. Because Smart Shapes are designed only for work classes, Smart Shapes will not be visible in shape menu when a flow is created in data class.
SR-117923 · Issue 171578
Remedied spurious size alert from the attachments viewer
Resolved in Pega Version 7.1.7
When listing attachments from History & Attachment display, the work object was re-read for each attachment. If the work object had many attachments, the alert "PEGA0004 alert (50MB DB threshold)" would appear regardless of the actual attachments' size. This has been adjusted so the RUF attachment access makes use of the existing WorkPage instead of re-reading it from the database.
SR-118061 · Issue 175102
CorrNew activity can send email in sync or batch
Resolved in Pega Version 7.1.7
When attempting to send email correspondence in synchronous mode i.e. not via the agent processing, the activity always queued it to the agent even when the Activity CorrNew SendNow param was set to true. To correct this, the system will pass the value of a BatchSend param based on the value of the SendNow param: email will be sent immediately If SendNow is set to 'yes', or will be queued for batch processing if SendNow is set to 'no'.
SR-118077 · Issue 170104
Excessive logging addressed in Pega Mobile 4.3
Resolved in Pega Version 7.1.7
In PegaMobile, the oLog debugging statements were generating excessive log files. This has been addressed in Pega Mobile 4.3.
SR-118170 · Issue 171859
Property History TaskName field expanded
Resolved in Pega Version 7.1.7
Previously, the TaskName field was limited to 32 characters. This has been expanded to 128 characters.
SR-118190 · Issue 172520
Drag and drop work reassignment corrected
Resolved in Pega Version 7.1.7
An error was found that prevented the ability to drag and drop a request from workbasket to worklist or from worklist to workbasket in the Case Manager portal. This has been corrected.
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-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.