SR-117827 · Issue 183888
Improved condition handling for complex harnesses
Resolved in Pega Version 7.1.8
If a Review Harness had multiple embedded tab sections with includes, a read-only condition in the parent section was not being honored in a sub-section if the 'when' condition became false. This happened when a SectionIncludeInCell RUF passed an unquoted null value as a 3rd argument while invoking stream reference, and has been resolved.
SR-118213 · Issue 184519
Refresh When' behavior fixed for portal tabs
Resolved in Pega Version 7.1.8
When a 'Refresh When' was active on a portal tab, the system would become unresponsive while trying to refresh it. This was caused by an incorrect element call resulting in a JavaScript error and has been corrected.
SR-118602 · Issue 178489
Corrected flow action dropdown execution
Resolved in Pega Version 7.1.8
For certain work objects, selecting a flow action from the pyAction area resulted in an error message and the flow action did not execute. A sample error message might be "The FlowAction ... could not be added to this assignment." This was caused by a flaw in the code which assumed that simple integer IDs in the DOM are unique. The code that handles 'Take Action' input has been re-factored to be more robust.
SR-118827 · Issue 179258
Work object reloading added to SFA portals
Resolved in Pega Version 7.1.8
When a work object in an SFA default portal (such as SFA SalesManager and SFAAdministrator) was opened by multiple users, modifications made by one were not seen by the other unless the other completely logged out and back in again. This was a function of the way the work object was opened and held in a thread, and has been modified with an API to reload the work object each time it is opened so that any saved changes are immediately available.
SR-119090 · Issue 179954
Progressive Paging Header Alignment Issue corrected
Resolved in Pega Version 7.1.8
On page load, the column headers for repeat grid with expand details did not align with the data when using Progressive Pagination. The root cause of this problem was with the design of Repeat Grids with 'Pagination' and Expand Details involved: the headers for Repeat Grid were created as separate table which failed to synchronize size with the table containing the data. To resolve this, changes were made in the GenerateGridHTML Function.
SR-119090 · Issue 175018
Progressive Paging Header Alignment Issue corrected
Resolved in Pega Version 7.1.8
On page load, the column headers for repeat grid with expand details did not align with the data when using Progressive Pagination. The root cause of this problem was with the design of Repeat Grids with 'Pagination' and Expand Details involved: the headers for Repeat Grid were created as separate table which failed to synchronize size with the table containing the data. To resolve this, changes were made in the GenerateGridHTML Function.
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-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.