SR-A168 · Issue 203378
Enhancements added to ensure visible 'when' after upgrade
Resolved in Pega Version 7.1.9
After migration using systems upgraded in place, all pre-existing Default controls no longer showed the "Required" option in the cell properties, and the validation no longer functioned correctly (the form submitted successfully with previously required fields empty). The root cause was that pyAutoHTML was not set in XML, so the Visibility condition expression evaluated to false. This has been resolved by adding a check for empty visible-when conditions and by inserting pzNonAutoHTML, a newly created when rule which checks for empty or false values of pyAutoHTML for required checkbox visibility.
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.
SR-A1848 · Issue 206991
Added handling to retain checkbox value on harness reload
Resolved in Pega Version 7.1.9
Clicking on 'Save Draft' was causing a checkbox in the work object screen which was checked (i.e. value is true) and disabled to have its value removed. This was traced to logic for disabled checkboxes that did not submit the corresponding hidden value if the reload harness ajax was missing. Checkbox value handling has been added to the form submit to resolve this.
SR-A1852 · Issue 209275
Resolved error on tab switching in DS portal
Resolved in Pega Version 7.1.9
After logging into Pega Designer Studio and launching a portal, performing a switch role/portal in the opened portal and then clicking on the Designer Studio tab closed the secondary portal tab. This was resolved, but an additional problem arose with an error being generated for the tab that was opened previously before switching applications when trying to save or modify the availability of already opened rules in the dev portal. This had to do with the API used to clean up the threads, and has been corrected.
SR-A1959 · Issue 209485
Corrected checkbox behavior with freeze header
Resolved in Pega Version 7.1.9
In repeat grids where freeze header was checked throughout the application and data was populated by page list, running the flow on selecting a check box for a single row resulted in all the check-boxes of the grid getting selected. This was an issue where the API "checkAllIfInHeader" incorrectly assumed that the checkbox was in the header for each row, which caused all the checkboxes of the row to change according to the checkbox that had been changed. To prevent this, a condition has been added to "checkAllIfInHeader" to exit if it is inside a row and not in the header.
SR-A2009 · Issue 206469
Fixed inconsistent tab 'visible when' behavior
Resolved in Pega Version 7.1.9
In a section with a tabbed repeat using 'body visible when', invoking a list which changed the when condition so that the tab becomes visible in the tabbed repeat created various issues after checking the visibility including invisible data, empty tabs, and duplicate tabs. This was traced to the placement of visible when conditions in the RUF causing the DIVs to be closed incorrectly, and has been fixed.
SR-A2107 · Issue 206837
Updated Reloadharness Activity to correctly render older menus after upgrade
Resolved in Pega Version 7.1.9
When menus were rendering with old menu generation code, the required parameters were not properly generating. This was caused by a missed Primary page name parameter in the update process for menu generation originally done under older versions of the software. While there was a workaround of regenerating the menus within the updated system, the transitional parameter has now been added for the reload harness action.
SR-A2125 · Issue 208860
Fixed scrolling for Autocomplete dropdown
Resolved in Pega Version 7.1.9
After opening a new harness with a button in the fixed div of the harness, the Autocomplete dropdown was detaching from the control and sticking to the screen when the browser scrolled. This was due to an inline style tag that interfered with repositioning the Autocomplete results popover. To fix this issue, a condition has been added to the style tag triggered on a harnessContent div to call an API for repositioning pop overs.
SR-A2141 · Issue 205867
Refined refresh focus logic for radio buttons using on OnChange
Resolved in Pega Version 7.1.9
In a list of Radio Buttons, using the Down Key caused focus to move to the corresponding Radio Button for a split second but immediately shift back to the first Radio Button. This was caused by the OnChange of the radio button having a refresh-this-section, so ReloadSection was being called and the focus was shifted to the first radio button irrespective of the option which was selected. This was confusing behavior, so the system has been modified such that after refresh, focus() element will be called to set focus on the element which caused the refresh.