INC-137168 · Issue 588708
Documentation updated for Ajax container refresh
Resolved in Pega Version 8.5.1
The documentation for adding an Ajax container has been updated to reflect the proper configuration for adding a refresh within the container.
INC-128970 · Issue 583294
Post value in grid works after clicking on modal submit
Resolved in Pega Version 8.5.1
The row submit on the grid of the modal dialogue worked when the value was updated and there was a click outside the grid. However, when the value was auto-populated, after clicking on the submit and going back to edit the value in the grid, the row submit did not work. Investigation showed that when a modal was submitted with some server errors, the system replaced the DOM and a new grid is initialized: since some of the listeners related to grid are attached to body, on submit of modal with server errors, these old listeners were getting fired. To resolve this, a safe check has been added for modalDetailsDiv before accessing it in event listeners.
INC-127719 · Issue 571778
Text area count correct for special characters
Resolved in Pega Version 8.5.1
The text area character count was showing negative numbers when using special characters. This was due to Cross-site scripting encoding that caused the text length to be incremented by 4. To eliminate this, the text length will now be calculated before encoding.
INC-134891 · Issue 589869
Logoff set to use root context
Resolved in Pega Version 8.5.1
The thread name was changing from Standard to DSCPA_DemoStudio on click of log-off, resulting in unexpected behavior if the user logged in again. To resolve this, an update has been made to trigger logoff in root context.
INC-136057 · Issue 587164
Modal dialog close for date/time works as expected
Resolved in Pega Version 8.5.1
When a date/time property was used in a modal screenflow in Google Chrome, changing the date property on the pop up calendar and then clicking the modal close caused the screen to freeze. This was caused by the plf.handleModalClose() being called a second time for a container close event that was not available in window.event. This has been resolved.
INC-137276 · Issue 585298
Arrow key navigation updates for layout grid tabs
Resolved in Pega Version 8.5.1
When a layout grid was configured as Tab mode, the up and down arrows allowed navigation between tabs. This has been modified to meet W3 standards of using left/right arrow keys to navigate between tabs and up/down arrow keys to scroll the page.
INC-128805 · Issue 579164
Timing corrected for modal dialog window height
Resolved in Pega Version 8.5.1
When creating a modal dialog with text area inputs, the height style attribute of the text areas appeared to use the width of the previous modal dialog window. If a small modal dialog was opened and then a large one, the text areas in the latter were oversized. Creating the same dialog twice caused the text areas to return to the intended size. This was traced to a timing issue with updating the modal dialog height, and has been resolved by adding a delay of 300ms to ensure the window height is updated properly.
INC-129984 · Issue 584552
Templated Sections render on first open when no height given
Resolved in Pega Version 8.5.1
When opening a section rule based on a template (like pyCaseMainInner), the contents did not load on first open. A browser refresh and/or rule refresh caused the contents in the section to appear. This was traced to a logic skip introduced as a resolution for the live preview being jumpy when changing between tabs, which did not take into account the initial load of the preview when it has no height. To resolve this, an update has been made to triggerReflow in the pzpega_ui_dynamiccontainer js to use an 'or' condition for resetting the height if live preview is not being used.
INC-133944 · Issue 586016
Future DateTime Property picks operator timezone
Resolved in Pega Version 8.5.1
When selecting the DateTime in a property field configured to accept future data input, the input failed validation due to the DateTime field being compared with the System time zone (IST instead of the operator time zone. This has been resolved by adding a condition to honor the operator timezone in isFutureDate validation, and to fall back to the browser timezone if necessary.
INC-134634 · Issue 584946
FSM Mobile app correctly starts phone call after closing Google
Resolved in Pega Version 8.5.1
When two controls were configured in the FSM Mobile app, one for Get Directions and one to handle a phone call, clicking on the phone call control worked correctly when it was used first, but clicking on the Get Directions control and opening and closing Google Maps before clicking on the Phone call control caused the phone call control to not work. Investigation showed that after the Get Directions control was used, the # in the href attribute was automatically prepended with window.location. To resolve this, a check has been added that will compare the attribute with the completely formed {URL}# so that entire window.location will not be prepended.