INC-177263 · Issue 655829
isFutureDate edit validation fires correctly
Resolved in Pega Version 8.7
The date value entered was not getting converted to the user-specific time zone and resulted in an incorrect value for validation when using isFutureDate. This has been resolved by adding an update which will convert the date value to the specific time zone before comparing it with the current date.
INC-182726 · Issue 677530
CORS DSS settings corrected for Constellation
Resolved in Pega Version 8.7
After moving to the new HIPPA edition, the developer work area in Constellation appeared as blank under Channel-Portal-Landing Pages. This was traced to a DSS setting issue when using cross-origin resource sharing (CORS), and has been resolved.
SR-133684 · Issue 206669
Enhancement added to support border color change on expand/collapse
Resolved in Pega Version 7.1.9
There was a desire to add highlighting to the borders of a text area when it was collapsed in order to indicate it was not editable. This color change was not previously possible because the same class was being called when the text area was expanded and collapsed and therefore no demarcation existed to hang the color change on. An enhancement has now been added to populate the class name for parent span of text area differently on expand or collapse to allow the use of custom CSS styles.
SR-A1732 · Issue 206294
Corrected mixed character autocomplete for JSON data
Resolved in Pega Version 7.1.9
Autocomplete was not populating values If a field used a mix of alphanumeric and special characters. This was an issue caused by exceptions generated when the field "PlantName" contained new line characters in the response JSON. To fix the issue, new line characters are converted as
before parsing the results.
SR-A1732 · Issue 206388
Corrected mixed character autocomplete for JSON data
Resolved in Pega Version 7.1.9
Autocomplete was not populating values If a field used a mix of alphanumeric and special characters. This was an issue caused by exceptions generated when the field "PlantName" contained new line characters in the response JSON. To fix the issue, new line characters are converted as
before parsing the results.
INC-180482 · Issue 661513
Browser compatibility update for setActivityAction
Resolved in Pega Version 8.7
After update, the Parameter Configuration popup was blank when using Microsoft Internet Explorer. This was traced to security updates that utilized the SafeURL.prototype.setActivityAction containing the startsWith API which is not supported by Internet Explorer. To resolve this, startsWith has been replaced with indexOf for cross-browser compatibility.
SR-A2641 · Issue 207208
ActionAutoSubmit functionality updated for AJAX calls
Resolved in Pega Version 7.1.9
The ActionAutoSubmit functionality was not working when used in HTML due to the "Go Back" action only reloading a section (AJAX call) and not the whole page which would have called the doSubmit() function. This has been fixed by changing the submit implementation in order to force the function to be called even on AJAX reloads.
INC-184311 · Issue 667270
Time value handling updated for IW locale
Resolved in Pega Version 8.7
The error -"0undefined/0undefinedundefinedundefinedundefinedundefined is not valid time of day value" appeared when using the 'IW' operator locale and the time field was changed. This was traced to a missed condition check for the IW locale while preparing the selected time value from the dateTimeFormatString, and has been resolved.
INC-184443 · Issue 668437
Time value handling updated for IW locale
Resolved in Pega Version 8.7
The error -"0undefined/0undefinedundefinedundefinedundefinedundefined is not valid time of day value" appeared when using the 'IW' operator locale and the time field was changed. This was traced to a missed condition check for the IW locale while preparing the selected time value from the dateTimeFormatString, and has been resolved.
INC-162426 · Issue 638771
Regex handling updated for Rich Text Editor spellcheck
Resolved in Pega Version 8.7
When using the Rich Text Editor and performing a spell check, the spell checker was adding additional CSS to the property. This was traced to the presence of a unicode newline character causing the existing regex to fail to strip the style tags. To resolve this, regex handling for the unicode newline character in the style tag has been added.