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.
SR-A1604 · Issue 206062
Other Actions submit API updated
Resolved in Pega Version 7.1.9
When using the out-of-the-box Other Actions button, selecting 'Refresh' caused a blank page to display and resulted in an 'ERR_CONNECTION_RESET' script error. This happened when a form submit URL including all input parameters exceeded the max length expected. The API used for the submit function has been updated as of this release along with the Ajax engine call, and the problem is no longer seen.
SR-A2323 · Issue 206066
Other Actions submit API updated
Resolved in Pega Version 7.1.9
When using the out-of-the-box Other Actions button, selecting 'Refresh' caused a blank page to display and resulted in an 'ERR_CONNECTION_RESET' script error. This happened when a form submit URL including all input parameters exceeded the max length expected. The API used for the submit function has been updated as of this release along with the Ajax engine call, and the problem is no longer seen.
SR-A2323 · Issue 206125
Other Actions submit API updated
Resolved in Pega Version 7.1.9
When using the out-of-the-box Other Actions button, selecting 'Refresh' caused a blank page to display and resulted in an 'ERR_CONNECTION_RESET' script error. This happened when a form submit URL including all input parameters exceeded the max length expected. The API used for the submit function has been updated as of this release along with the Ajax engine call, and the problem is no longer seen.
SR-A9615 · Issue 218861
Resolved NPE in batch processing Decision data flows
Resolved in Pega Version 7.2
A null pointer exception was being thrown when accessing the batch processing function for Decision data flows if the 'initservices/dnode' dynamic system was set to false. This was traced to a failure of the Flow Action pre-processing activity attempting to call DNodeServiceListener to initialize it, and a check has been added so the Data flow run manager will now try to initialize each time it is asked for an instance if it was not initialized already.
SR-A5110 · Issue 214245
Fixed exception generated by 'getclassname' used with autocomplete
Resolved in Pega Version 7.2
An issue was found in some new installations using autocomplete where trying to set and execute 'getclassname' after a name change caused a conflict between the old and new values. The problem was traced to a function that set the new value and then repeated a call to the old one, nullifying the change. This did not effect upgraded systems due to a difference in the storage stream versions, and the conflict has been resolved by updating the logic
SR-A13963 · Issue 227442
Dropdown control updated for Apple mobile Safari
Resolved in Pega Version 7.2
The Apple mobile Safari webview displayed a problem with updating the state of selection in a dropdown, creating scenarios where two values were shown as selected or previously selected values were lost. This was traced to the DOM selector "option:selected" selecting multiple options by accumulating all of the selections done by the user up to that point in time. The databinder function has been modified to handle this specific environment for dropdowns.
SR-A14151 · Issue 244440
Autocomplete select updates as expected
Resolved in Pega Version 7.2.1
An intermittent problem was found with autocomplete that selected a previously set value if text was typed in the autocomplete box and the value was selected instead of the search text. This was traced to a press of the capslock key being interpreted as an unprintable character, causing an abort of the request and change tracker not having the correct update. The function processkey of autocompleteag.js has now been updated to not abort the request when a non-printable character is typed.
SR-A16938 · Issue 232832
Hardcoded DDL date replaced with dynamic string for Postgres compatibility
Resolved in Pega Version 7.2.1
The PostgreSQL DDL generator for install and upgrade in PRPC 7.1.9 created a PL/pgSQL containing the direct date value "01/01/1990". In some versions of Postgres 9.3, this caused a datestyle mismatch execution error when datestyle was set to "iso, ymd" on the postgresql.conf side. This has been resolved by replacing the hardcoded date value with a to_date function that uses an appropriate format string.
SR-A21017 · Issue 239317
Parameter label mismatch corrected for import
Resolved in Pega Version 7.2.1
During upgrade, activities or functions which had Parameter type 'Double' were automatically converted to String data type upon Import into the target Environment even when the XML indicated DOUBLE. This was an issue with rendering the value in the UI: the pyLabel for double parameter type was "Double" not "DOUBLE" in the Data Transform rule pyLoadDataTypes, which didn't match. The activity has now been updated to use DOUBLE.