SR-118159 · Issue 174990
Improved handling for Case notes when spellchecker is active
Resolved in Pega Version 7.1.7
If a lot of content was added for a case Note, clicking on the Notes tab caused the text to display in a big yellow box which could not be dismissed. This was traced to the spell checker not properly handling RTE's hidden textarea field, and the code has been modified to correct this.
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-118174 · Issue 173341
Sorted Report Definition drill downs corrected
Resolved in Pega Version 7.1.7
For some configurations, the Report Definition drill down did not work when it has been sorted. This manifested as either no results returned by the drill down report or an error message related to invalid filter values. This was caused by an error in calling the page sort in cases where 'do not display group headers' was checked, and has been corrected.
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-118194 · Issue 170594
Declarative refresh now working for IE
Resolved in Pega Version 7.1.7
When using IE, property changes on the clipboard did not trigger a declarative refresh. This was traced to a duplicate refresh section list that was not getting cleared properly with addition of cross thread change tracking, and has been corrected.
SR-118259 · Issue 173287
LookupList opened to unauthenticated requests
Resolved in Pega Version 7.1.7
When a list lookup was called from an unauthenticated service, it failed due to the lack of required authentication. The activity RULE-CIRCUMSTANCE-DEFINITION LOOKUPLIST has been modified to allow its execution by an unauthenticated requestor.
SR-118305 · Issue 171562
Report definition reference columns expanded to include data type smallint
Resolved in Pega Version 7.1.7
Report definitions with reference columns of data type SmallInt in their database were not able to run as expected after migration due to missing support for that data type. This support has been added.
SR-118307 · Issue 172330
Integers with embedded spaces now prompt screen edit during validation
Resolved in Pega Version 7.1.7
If an Integer property was populated with a number with spaces ("12345 67890"), it generated the validation error "** PropertyValueInvalid null .pegaToInteger() Invalid number format (was 12345 67890)". A numeric value with embedded spaces will fail during conversion to Integer, but this will now be caught with a screen edit in the same way a non-numeric character would be during screen validation.
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-118512 · Issue 175817
Improved error handling for iFrame XSS
Resolved in Pega Version Pega Platform, Resolved in Pega Version 7.1.7
When using cross-site scripting with iFrame, attempts to use auto-complete did not populate data and an 'Access Denied' error was raised when keywords were entered for searching. While the system cannot access or modify iFrame content from another domain, the javascript for the autocomplete function has been modified to correctly handle any exceptions thrown while accessing iFrame from a different domain.