SR-123663 · Issue 184330
Multi-cell paste supported for Excel Map Value edits
Resolved in Pega Version 7.1.8
When trying to paste multiple rows into a Map Value using the 'Edit in Excel' feature, a runtime error was generated. The root cause was a refactoring code snippet that assumed only one cell for a change / paste, and the logic failed for multi-cell paste. The property used in the original logic becomes nonexistent (Target.Value) when multiple cells are being pasted. To resolve this, a different property (an array called Target.Value2 ) has been incorporated to populate and adjust the target cells.
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-126679 · Issue 197204
Tree grid alignment resolved for Google Chrome and Firefox
Resolved in Pega Version 7.1.8
When using the Google Chrome and Firefox browsers, tree grid rows were not properly aligned. This was due to legacy code in GenerateGridHTML which was running in quirks and used a different document model in different browsers. The model was no longer necessary due to a change in the generation method, and has been removed.
SR-126679 · Issue 197617
Tree grid alignment resolved for Google Chrome and Firefox
Resolved in Pega Version 7.1.8
When using the Google Chrome and Firefox browsers, tree grid rows were not properly aligned. This was due to legacy code in GenerateGridHTML which was running in quirks and used a different document model in different browsers. The model was no longer necessary due to a change in the generation method, and has been removed.
SR-129722 · Issue 197103
Removed extra white space in Microsoft Internet Explorer 8
Resolved in Pega Version 7.1.8
When using the Microsoft Internet Explorer 8 browser, extra white space appeared above the 'next' button when declare expression was fired in a screen flow which grew with each declare firing. This has been corrected by updating the last condition to check for the 'display' property.
SR-117877 · Issue 178627
Report on implementation classes corrected for descendant class
Resolved in Pega Version 7.1.8
Report definition was not using implementation class even when 'report on descendant class' was checked. This was caused by an access group changed in RAQ not being reflected into DAQ. When a Data-Admin-Requestor has a Access group which isn't the default, the default authentication doesn't occur and as such the application data page isn't created for the requestor. The lack of an application page causes the code to not determine the associated implementation class for the report definition. This has been changed to use the access group from DAQ only if it is newer than RAQ.
SR-117877 · Issue 175972
Report on implementation classes corrected for descendant class
Resolved in Pega Version 7.1.8
Report definition was not using implementation class even when 'report on descendant class' was checked. This was caused by an access group changed in RAQ not being reflected into DAQ. When a Data-Admin-Requestor has a Access group which isn't the default, the default authentication doesn't occur and as such the application data page isn't created for the requestor. The lack of an application page causes the code to not determine the associated implementation class for the report definition. This has been changed to use the access group from DAQ only if it is newer than RAQ.
SR-122108 · Issue 182692
Fixed linking for work objects in CalendarViewGadget
Resolved in Pega Version 7.1.8
Using CalendarViewGadget to show calendar with work objects generated a Javascript popup with message "undefined" when clicking on the link of a work object. This "undefined" alert was added for situations where there is no handle passed to the openWorkByHandle desktop API, but there was an incorrect key in the hashtable of strings used to get the localized value. This has been fixed.
SR-128102 · Issue 193767
Resolved RD filter prompt not showing
Resolved in Pega Version 7.1.8
The Report Definition filter prompt was not displayed even when 'Prompt for filter changes' was checked. This was an issue with PXSHOWREPORT not using the correct step page, and has been fixed.
SR-125934 · Issue 190270
Adjusted modal dialog height functioning with repeating grid
Resolved in Pega Version 7.1.8
When using a repeat grid to open a modal dialog to add rows, the modal dialog height was getting increased by scroll adjustment always, which should be done only when its scrollHeight is greater than offsetHeight. Code changes have been made in the setModalDialogHeight function to correct this.