SR-133622 · Issue 205914
Localization timing shifted for "Currently open" tooltip on tab control
Resolved in Pega Version 7.1.9
Previously, the "Currently open" tooltip on tab control used to fetch any localization upon save of the section if it had a dynamic container. The generateTabbedSectionLayout RUF has now been enhanced to get the updated value of the Currently Open tool tip value at run time for a better user experience.
SR-133622 · Issue 205694
Localization timing shifted for "Currently open" tooltip on tab control
Resolved in Pega Version 7.1.9
Previously, the "Currently open" tooltip on tab control used to fetch any localization upon save of the section if it had a dynamic container. The generateTabbedSectionLayout RUF has now been enhanced to get the updated value of the Currently Open tool tip value at run time for a better user experience.
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-133709 · Issue 205980
Validation message remains on hover
Resolved in Pega Version 7.1.9
Whenever a post validation message was present at harness level and an icon was configured to display a smart info on hover, hovering on the icon caused the error message at the harness level to disappear. Opening a smart info internally triggers reload section which clears out the messages by default, so this has been resolved by sending the KeepPageMessages parameter as true in sendRequest under these conditions.
SR-133734 · Issue 205290
Added handling for remaining character count inconsistency with Microsoft Internet Explorer 8
Resolved in Pega Version 7.1.9
In ie browser, new line is interpreted as "\r\n". This caused the remaining character count of a text area control to be inconsistent in the Microsoft Internet Explorer 8 browser due to the browser sometimes calculating the size of a new line character as one instead of two(\n\r). To handle this, the logic for remaining character count has been updated in the text area JS.
SR-A1190 · Issue 205299
Corrected highlight alignment for Alt+ Key button selection
Resolved in Pega Version 7.1.9
If a button is clicked using hot keys (Alt + Key), a blue line is wrapped around the button to highlight its selection. However this blue line was expanded below the button and misaligned. This was caused by a margin-left of 0.3 mm on access key styles which has now been removed.
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-A1616 · Issue 205609
Fixed section refresh issue in Google Chrome
Resolved in Pega Version 7.1.9
When using the Google Chrome browser, a section that was included inside a repeating dynamic layout and configured to refresh based on the value of a radio button control which itself was included in another section and configured to post its value on change was refreshed as expected in dev portal but not in IAC. This was due to changes in the value list not populating properly in Google Chrome on IA, and the logic for parsing change tracker div has been modified to correct this.
SR-A1647 · Issue 205606
Removed duplicate special character encoding on FieldValue validation
Resolved in Pega Version 7.1.9
A recent change was made to the "Validate" activity of the Rule-Obj-FieldValue class to improve security by performing a filterRichText (intended to remove unsafe tags like script tag). However, this broke a reported use case where field values used as the source for the controls dropdown, checkbox, or radio buttons displayed the encoded values of quotes due to double encoding. To fix this, the filterRichText step has been removed from Rule-Obj-FieldValue!validate activity.
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.