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-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-A4314 · Issue 210533
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-131132 · Issue 205659
New 'when' rule added to enhance visibility conditions for embedded sections
Resolved in Pega Version 7.1.9
After upgrade, only the OK and Cancel buttons were displayed when editing a navigation rule. This was caused by a "pzShowPropertyPanel" section included in a "pzNavigationMain" section with a visible 'when' that was configured with both || and && causing exceptions while executing the expression. To handle this scenario, a new 'when' rule Embed-Rule-Navigation-Element.pzShowVisibleCondition has been created to be used in the pzNavigationMain section.
SR-131228 · Issue 202735
Local template use corrected for 'add item' in repeating grid
Resolved in Pega Version 7.1.9
In repeat grid with options "Expandable rows" and "Override default template", adding a row by action "Add item" resulted in the local template being replaced by the standard "pyGridRowDetails" template. In other cases (e.g. when use action "Edit item") user's custom template was used. To resolve this, templateName generation has been added for expanded pane configuration to check for local templates first before defaulting to the ones provided.
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.
SR-A2141 · Issue 205271
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.
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.