INC-177104 · Issue 666334
Resolved-by field reflects queue processor close
Resolved in Pega Version 8.7
When a case was resolved by the queue processor, for example when the SLA ended and a case was automatically Resolved-Withdrawn by the system, the "Resolved by" field was blank. This was caused by the pyOperatorInfo control looking for the system account user data in the application users pool, and has been resolved by updating the control to display the localizable "System" name in this scenario.
INC-166444 · Issue 642114
FlexModalTemplate Modal window size consistent
Resolved in Pega Version 8.7
The FlexModalTemplate modal window size was changing on second click. This was a missed use case for dirty dialog CSS implementation, and has been resolved by moving the CSS necessary into the isDirtyDialogOpen if condition.
SR-D74921 · Issue 551787
Error condition will close WebSocket connection
Resolved in Pega Version 8.2.7
An async listener has been added that will close the WebSocket connection when an error condition is encountered.
INC-144851 · Issue 604481
Date Time picker works with locale es_US
Resolved in Pega Version 8.3.5
When an Operator had the locale es_US (Spanish) set on the Profile, the Date Picker on the application was throwing validation errors when a date or time was chosen from the out-of-the-box Date Time Control. Investigation showed the date-time format for locale es_US was not supported, and the getDateTimeFormat API has been updated to support this format (11:00 a.m.).
INC-197243 · Issue 687412
Locking up+E975dated for EmailLink
Resolved in Pega Version 8.7
After clicking a work link from email and opening the work object in a new window, opening the work object in the perform harness and performing a browser refresh by way of Actions -> Refresh resulted in a locking error when trying to submit the case. This was traced to the handling in the Ajax container: when an assignment is opened from the todo list, it will open it in primary Ajax container. If the complete web page was refreshed, the contents in the Ajax container were cleared and loaded back to previous state. While doing this process the lock of the Work Object was released and not added back. In order to achieve the lock after the refresh, the doUIAction activity has been updated to lock the case when the case is opened and reloaded.
INC-198484 · Issue 689007
Tab error message localized
Resolved in Pega Version 8.7
Localization has been added for the message that is shown at a tab when a section in tabbed layout contains errors.
SR-D84122 · Issue 547966
Added min INT comparison for BrowseByKeys
Resolved in Pega Version 8.2.7
Running the dataset with the Browse option worked as expected, but running it using BrowseByKeys operation and giving a negative value caused results to not be populated. To resolve this, a minimum INT value comparison has been added.
INC-173505 · Issue 657024
Error message updated for data page with REDUX
Resolved in Pega Version 8.7
A WrongModeException was generated when a runtime activity was trying to access a missing property in a data page with REDUX enabled. To clarify the issue, the error has been modified to be a MissingPropertyException. In addition, property information for a page group property was inferred on the top level page when it should have been inferred on the embedded page. This has been changed to infer the correct property information for mode-based processing to work as expected.
INC-198021 · Issue 686630
Corrected blank areas on maximized view
Resolved in Pega Version 8.7
A blank section was displayed when maximizing the reply screen. Investigation showed that when the editor was inside a positioned container with overflow hidden and the editor had a scrollbar with its body height greater than the document, the scrollIntoView would scroll to grey spaces which were originally hidden by overflow. This has been resolved by commenting out scrollintoview, since it is not necessary and scroll position/cursor will be retained without it.
INC-144600 · Issue 599916
Skip links enabled for all users by default
Resolved in Pega Version 8.3.5
In order to improve the UI experience, the isAccessible check for skiplinks has been removed. This allows users to navigate the content of the page using skip links without having to have their access group be set to accessible mode.