SR-119245 · Issue 178510
Local List now supports '+'
Resolved in Pega Version 7.1.8
The '+' character was not being supported in Local List. This was traced to the Ajax post request converting the '+' character to a space, and code has been added to preserve the '+' character.
SR-119246 · Issue 178467
Localization improved for Lithuania
Resolved in Pega Version 7.1.8
If the localization was set to Lithuania, using a property of type Date with a control pxDateTime and configuring its display mode to Dropdown Lists only allowed 'month' to be selected rather than the whole date. In addition, the three letter month abbreviations were ambiguous, using "Rug" for both Rugpjutis (August) and Rugsejis (September) rather than Rgp and Rgs. These issues have been fixed.
SR-119297 · Issue 183495
Dynamic container enhanced for harness sections
Resolved in Pega Version 7.1.8
In some situations, tab visibility conditions were not functioning as expected. For example, in a portal with a harness that has 2 sections, the click of an enable/disable button in the top section was configured to refresh the bottom section as well as call an activity. The bottom section had a tab layout containing harness rules with conditions specified for the tab visibility based on the above "Enable/Disable" button. For the above features, the data model got created when the Dynamic Container was being rendered for the portal's harness, and the data model was updated with the dynamic tabs' meta data. However, the data model was not being created while rendering the harness, and the lower section did not confirm to expectations. To resolve this, the code has been updated to handle the section refresh which has a Dynamic Container.
SR-119376 · Issue 179579
Resolved checkout conflicts with discarded rule edits
Resolved in Pega Version 7.1.8
After a private edit of a work flow rule in the tenant layer, discarding that rule and then trying to do another Private Edit on the same rule generated the error "Status: **Check out failed. A checked out version with the same keys already exists. Please check-in that record first. This was traced to an issue with the clipboard retaining the discarded rule, and has been corrected.
SR-119444 · Issue 179227
Updated sorting and filtering icons to work with JAWS
Resolved in Pega Version 7.1.8
As filtering and sorting did not use labels, JAWS was not announcing icon names without labels. This resulted in JAWS not announcing the filter list, that a column was sortable, the presence of a filter icon, or whether a column was sorted ascending or descending. This was due to the "ARIA" attributes not being generated without PegaWAI ruleset1, and the system has been updated to enhance the accessibility.
SR-119601 · Issue 176925
ParseXmlObjectWrapperAssembler updated to handle embedded pages
Resolved in Pega Version 7.1.8
Parse XML rule compilation was failing if the Pages and Classes tab of Parse XML rule included an embedded page. This was traced to an assembler issue and ParseXmlObjectWrapperAssembler has been updated to resolve compilation issues in case of named pages.
SR-119648 · Issue 177559
JavaMAIL version updated for GMail compatibility
Resolved in Pega Version 7.1.8
A third-party product integrated with PRPC was causing mail and attachments to not appear properly when using Gmail due to an incompatibility with Gmail's interpretation of IMAP. To correct this, the provided JavaMAIL version has been updated from 1.4.1 to 1.5.2.
SR-119657 · Issue 184258
Apostrophe no longer causes truncated values in MutliSelectList controls
Resolved in Pega Version 7.1.8
If an option in a MultiSelectList control contained an apostrophe, the option would be truncated at the apostrophe when the work item was saved. This meant that when the item was reopened, the selected value was not highlighted in control. This was caused by the system building the MultiSelectList control with the standard HTML Select tag and its options elements, which do not encode the special characters like apostrophe while preparing the multi select list control with the values, leaving the browser to take the option value as' till apostrophe' instead of the whole value. To correct this, the value is now encoded using the crossScriptingFilter String API.
SR-119705 · Issue 185469
Removed automatic upgrades for deprecated buttons
Resolved in Pega Version 7.1.8
Some deprecated buttons were being upgraded after migration, causing confusion. To avoid this, the logic to determine whether a button control should be upgraded has been updated.
SR-119707 · Issue 178023
All results shown by default for database searches
Resolved in Pega Version 7.1.8
Previously, when performing a database search by using the "old:" keyword prefix and some of the results were removed by the pyTransform activity due to the number of matches exceeding the Initial Results Limit, the "Show All Results" option would not appear in the footer information. This behavior has been changed and such commands will automatically search and display all results.