SR-D51555 · Issue 516494
Resolved system hang after changing input field value post note
Resolved in Pega Version 8.1.8
After upgrade, a session was hanging in a Non-Member Search Phone interaction after navigating back from "Add or edit attachments" window. The same code worked as expected in the Member Search Phone interaction. Investigation showed that changed values (transaction ID, pzFromFrame) were being sent to the client twice, once in the popup window after attaching the note and again to the parent window. When the changed values were consumed and used in next actions, a mismatch resulted in pzFromFrame. To resolve this, the system has been updated so the Client will not consume the pxThread.pxClientExchange value if pxThread.pxClientFrame is different from what the current tracker is using.
SR-D51601 · Issue 516703
Hover logic updated
Resolved in Pega Version 8.1.8
When using a dropdown in a grid layout configured with a smartInfo to be displayed on Hover, the smart tip was sometimes not displayed when the hover moved from the top to point to the dropdown. If the hover was done quickly, it was displayed. Previously, the hover was calculated only by cursor x, y positions and elements boundaries: to resolve this issue, the logic has been updated to also consider cases where the element is still hovered without meeting these conditions.
SR-D52144 · Issue 515671
When no active document is available on login, first document will be marked active
Resolved in Pega Version 8.1.8
After logging into the user portal, attempting to perform operations like (opening a case/work object, opening reports etc.) caused the browser request to spin or freeze. The only way to recover was to close and re-launch the browser window/session and re-login. This issue occurred when there was an active reportdefinition document before the browser/node crash in the tabless dynamic container(DC) portal. After recovery, the dynamic container did not recreate the report definition document but instead tried to activate the first document in the portal, which in this case was the default harness configured in the Dynamic Container. As it was not yet loaded, exceptions were thrown. To resolve this, when no active document is available, the first document will be marked as the active document.
SR-D53488 · Issue 520015
Tab layout group handling improved
Resolved in Pega Version 8.1.8
A difference in scrolling speeds between left and right arrows and an issue with the cursor correctly being redirected to mandatory fields were traced to errors in the tab layout group handling. The right scrolling issue was due to the calculation for right tab movement being incorrect in certain resolutions with relatively positioned elements, and has been corrected. The cursor redirect was caused by an error in the layoutgroup focus when used inside a screen flow where the first focus goes to the screenflow navigation on load, and has been resolved by adding a try catch for an invalid selector in case of a div error.
SR-D53757 · Issue 523128
JSON parsing error on export resolved by ensuring parameter encoding
Resolved in Pega Version 8.1.8
Menu items like "PDF" and "Excel" were not loading on click of the "Export" Button, and an "Exception in parsing JSON" message was logged. The export worked as expected when the menu rule actions of each menu item were modified to remove the openurlinwindow actions. This was traced to the Response JSON being broken due to a invalid format created when the "propositionName" was passed as an unencoded parameter when the report was exported. This has been resolved by ensuring the input parameters are encoded before creating the URL.
SR-D54594 · Issue 521633
Enhancement added to customize the clearing of error messages when performing modal actions
Resolved in Pega Version 8.1.8
Opening any modal dialog, for example adding a row in Table/Grid layout, cleared any existing validation error messages on UI screen. In order to make this behavior customizable, a flag has been introduced to control the clearing of error messages from primary pages on grid actions. Updates have been made in the ui_grid, ui_grid_dragdrop and ui_repeatlayout JS files to include this flag in activity parameters and the pzdoGridAction activity has been modified to consider the flag.
SR-D54785 · Issue 524802
Corrected grey area seen when dragging tabbed layout Smartinfo scroll
Resolved in Pega Version 8.1.8
When using Show Smartinfo in a tabbed layout group, a grey area was seen in the harness while scrolling. Scrolling up so that Smartinfo was out of view port caused another scroll bar to seen: one scrollbar was attached to the workarea div and the other to the body, and the gray area issue was only reproducible when explicitly dragging the (second) scrollbar attached to the body. To resolve this, if the popup is below the viewport using Smartinfo and the height calculated is negative, then the popup's height will be set to 0px.
SR-D54920 · Issue 518272
Extra checks added for pasting Excel content to rich-text editor
Resolved in Pega Version 8.1.8
Copying content from Excel into rich-text editor pasted an image of the content either instead of the actual content or in addition to the actual content. This was traced to the handling of the isHTML flag: the flag should be set to true when there is HTML content in the datatransfer item or while pasting images (!isHTML is the condition in if). However, the sequence of the data items in the datatransfer can change depending on the browser/OS, causing isHTML to sometimes not be set to true before it is used in the condition while pasting images. To resolve this, changes have been made to the pasteHandler in the pzpega_ckeditor_extras file so proper checks are made to figure out the type of data from the clipboard that is being pasted.
SR-D55294 · Issue 517216
Work List loads as expected in IE
Resolved in Pega Version 8.1.8
After upgrade, the Work List was not loading in IE. This was an unintended side effect of work done to handle resizing the Recents list when another tab was open, and that change has been reverted to resolve this issue.
SR-D57610 · Issue 518694
Last X Days and Next X Days removed from displayTimePeriod
Resolved in Pega Version 8.1.8
Last X Days and Next X Days removed from displayTimePeriodWhen the date filtering value of "Last X Days" was selected in a report definition, the error "An invalid comparison value or an invalid column has been entered for the right-hand side of a filter condition. Enter a valid column, calculation, or literal value" appeared if any value was entered other than the predefined (like last 8 days, last 31 days etc). This was traced to the control pzdisplayTimePeriod List view returning all field values (getFieldValues) under the class name "Embed-ReportingPeriod" with FieldName as "pySymbolName". This has been resolved by modifying pzdisplayTimePeriod to remove Last X Days and Next X Days.