SR-133388 · Issue 203251
Fixed space overrun display issues for localized text in Designer Studio
Resolved in Pega Version 7.1.9
If the localized non-English text length was lengthy, it was overrunning its space and crossing into adjacent sections of the Explorer tab of Designer Studio. This has been corrected by adding style code to handle the left and right orientation of tabs, which is especially critical for Japanese and Arabian characters.
SR-133501 · Issue 202754
Error icons and localization corrected for repeating tabs headers
Resolved in Pega Version 7.1.9
The error message indication was not appearing on the tab header of repeating tabs. In addition, the tooltip of that icon was not being correctly localized. These issues have been corrected.
SR-133545 · Issue 205543
Removed cleartext password in Operator password change URL
Resolved in Pega Version 7.1.9
The Change Password dialog in the Operator Full Profile provided cleartext of passwords as parameters in URL. The form method has been changed to POST in the HTML for the operator password reset popup to resolve this.
SR-133549 · Issue 203775
Added localization for "next" in new work item tab
Resolved in Pega Version 7.1.9
In the Case Manager portal, the 'next' label of a newly opened work item tab was not being localized. That has been fixed.
SR-133556 · Issue 206065
Corrected dropdown value reset following OnChange
Resolved in Pega Version 7.1.9
When a Clipboard page populated through an activity that retrieves data from an external table was used as a source for a drop-down, any validation errors would cause a return to the same screen but the selected value was not retained in the drop-down even though it appeared to be present on the clipboard. This was an issue with the drop-down option having leading/trailing spaces, and has been corrected.
SR-133611 · Issue 205327
Newline conversion added to enable search Autocomplete
Resolved in Pega Version 7.1.9
Despite results being present on the clipboard, Autocomplete was not displaying matching results during a search. This issue was due to newline characters present in the response JSON causing exceptions while calling eval() on the response string. To fix the issue, new line characters will be converted to
before parsing the results.
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.