SR-125254 · Issue 188703
Added Finish Assignment check for old harnesses
Resolved in Pega Version 7.1.8
After upgrade, a failing post flow action validation created the inability to correct the errors and resubmit using a pxButton which performed an out of the box "Finish Assignment." When trying to do so, a busy indicator was displayed and the application froze. This was caused by an incorrect legacy harness pointer for the Action section. A check for old harnesses has been added, and the submit API now sets the target of form submit for finish assignment to the parent window.
SR-125268 · Issue 188000
Added ownership check for DeleteModalHeader process
Resolved in Pega Version 7.1.8
When closing a modal dialog, the dropdown in the parent window became disabled and did not allow further selection. This was caused by the modal js throwing an error while attempting to remove an element that was not its child. To avoid this, the deleteModalHeader js API has bene modified to check the parent/child relationship before proceeding with the delete.
SR-125548 · Issue 195950
Corrected masking of screen by busy indicator
Resolved in Pega Version 7.1.8
Only a portion of the screen was being masked by the busy indicator, allowing modifications to be made on the other visible portions of the screen. This has been corrected.
SR-125568 · Issue 188832
Data transform checkbox handling fixed
Resolved in Pega Version 7.1.8
A data transform configured for 'Refresh When' on a section include property panel was not being executed. This was caused by the data transform checkbox not being honored properly inside the Refresh action.GenerateClientWhenDiv and picking the wrong child item. This has been fixed.
SR-125586 · Issue 188563
Drag and drop fixed for RDs with "SUM" functions
Resolved in Pega Version 7.1.8
If a report definition with 'SUM' function applied on one of the columns was included in a tree grid, the error "Exception when trying to execute dropOnSectionFromExternal" was generated. If the same report definition was used as a tree grid and the grid was dragged from the layout panel and dropped in a section, the columns in the repeat definition configured after the column having 'SUM' function were not displayed as tree grid columns. To correct this, changes have been made to the "populateSummaryReportColumns" method defined in "pzpega_ud_section.js".
SR-125590 · Issue 189717
Refresh context retained when switching tabs in repeating layouts
Resolved in Pega Version 7.1.8
When a repeating tabbed layout is configured to include "Refresh other section" functionality to refresh sections within the tab, it worked correctly when the operator created a new tab and performed all the work in that tab. However, if the operator switched to another tab and then returned to the original tab, the refresh other section and any associated activity used the context of the previously opened tab and it appears to the operator as if the action they have just performed has not worked. This was caused by the Refresh Other section not supporting multiple section refresh if the section is in a repeating layout (i.e. the same named section appears multiple times, once in each tab). The system has been updated to refresh ALL the occurrences of the same section in UI to resolve this issue.
SR-125649 · Issue 188834
Error messages displayed in user portal for operator availability
Resolved in Pega Version 7.1.8
In the user portal, there was no place to show errors in the section that were related to user availability. This has been added.
SR-125710 · Issue 190028
PegaWAI updated to retain Dynamic Select value
Resolved in Pega Version 7.1.8
When PegaWAI is included in a stack, the dynamic select has a button "Select" after it. When choosing a value and pressing the select button, the on-change event fired without an issue. However, when the submit button is pressed on the form, the property lost its value and a validation message (checking the property for value of " " and displaying a message if true) was presented. This was traced to a hidden input field associated with the DynamicSelect when using PegaWAI and DynamicSelect configured with an OnChange event to support the implementation of the 'Select' button. When the DynamicSelect is read-only and disabled, the hidden input remains hidden but is not disabled, and as a result the hidden (blank) input value was being submitted and used to trigger the validation. To prevent this problem, RULE-FILE-TEXT WEBWB PEGA_UI_DYNAMICSELECT has been updated to handle this situation and to ensure the hidden input is disabled if the dynamic select is disabled / read-only.
SR-125727 · Issue 188306
Information added to browser compatibility mode pop-up
Resolved in Pega Version 7.1.8
The popup that appears when attempting to log in to developer portal using the Microsoft Internet Explorer browser set to compatibility mode has been modified to be more informative. The new text is "You appear to have Internet Explorer Compatibility View enabled. The Designer Studio is designed to work in standards mode. Switch your browser mode by going to the 'Tools > Compatibility View Settings' menu and unchecking the 'display intranet sites in compatibility view' and 'display all websites in compatibility view' settings. In addition, make sure the node you are connecting to is NOT listed in the "Websites you've added to Compatibility View" section."
SR-125851 · Issue 194660
Amended SmartInfo pop-up for auto-dismiss function
Resolved in Pega Version 7.1.8
A SmartInfo pop-up for the "Auto-dismiss on hover away" checkbox contained the message "When this is unchecked a close icon is added to the SmartInfo to explicitly dismiss it. Clicking outside the SmartInfo also dismisses it.", but clicking outside the window did not dismiss it. This pop-up contained incorrect information, and has been modified to remove the information about dismissing the window by clicking outside of it. If the checkbox is unchecked, the close icon will appear and must be used to dismiss the window.