INC-148303 · Issue 606795
doRDLAction activity registered for BAC validity
Resolved in Pega Version 8.5.2
Users were unable to see more than the 10 most recent pulse posts because of a security alert (SECU0019) being thrown when the 'Show More' link was clicked. Investigation showed the error was coming from the PegaGadget-Feed.pyRDLPaginator section: "pzdoRDLAction" is part of non-template rendering, and pagination will use "pzdoRDLAction" activity whenever paginator is used in a non-template section. Because of this, it must be registered for BAC security to accept it and pass through, and this has now been done to resolve this issue.
INC-148375 · Issue 607796
"Today" will set date-time in the respective operator timezone
Resolved in Pega Version 8.5.2
When a Date was entered using the "Today" option in Datetime control, the Date set used the system date and Time was taken from Timezone specified for the operator. This created issues for a scenario such as operator being set to America/New_York/ EST while the application was accessed in another country such as India or Japan. This was a missed use case and has been resolved by adding code to get the date-time in the respective operator timezone and setting it on click of date-time controls.
INC-148552 · Issue 607367
Added ability to disable dirty form browser alerts
Resolved in Pega Version 8.5.2
In order to add support for those who do not want to see a browser alert pop-up when cancelling a work item after making changes but do want the out-of-the-box Dirty popup to be displayed, an update has been made to add a configurable flag. If pega.u.d.bUseNativeDirtyConfirm is set to false, only Pega dirty dialogs will be shown. Setting it to true will show the Pega dirty dialog or else the browser dirty dialog for an event object.
INC-150407 · Issue 605840
Validation error messages correctly cleared in nested markup
Resolved in Pega Version 8.5.2
A UI Freeze issue was seen whenever mandatory input was missed and the form was submitted. Continuing was possible after browser refresh, but a new Next>> button appeared. This was an unintended side effect of work done to correctly clear validation messages when areas had captions, and has been resolved by modifying that work so it performs as expected on nested markup.
INC-150472 · Issue 607392
Sorting works after selecting a view on GRID
Resolved in Pega Version 8.5.2
After configuring an optimized table with personalized view, saving a view and toggling to the new view, the sorting on the grid did not work anymore. Returning to the default view did not fix the problem, but sorting was reenabled after a browser refresh. This was traced to duplicate removeinstance calls of the grid which deleted the click event listeners for sort, and has been resolved.
INC-150189 · Issue 608911
Handling added for new doc.write with Google Chrome 85
Resolved in Pega Version 8.5.2
Document.write was not working as expected on Google Chrome 85 due to the DOM elements not being updated. This has been resolved by updating the code to do doc.write by checking the if the document body has no child nodes in a time out.
SR-C49664 · Issue 435310
Updates made for usage validation utility Run report checkbox and buttons
Resolved in Pega Version 8.1.5
The 'Review mode only' checkbox wasn't working for any browser, and the 'Run Report' button wasn't working in IE. This has been resolved by updating the javascript used to invoke the Run Report button to be better integrated with IE, and by adding additional handling to set the ID for the checkbox.
SR-C74677 · Issue 418339
ADM pulse timing changed to inprove performance on very large clusters
Resolved in Pega Version 8.1.5
ADM uses a pulse that checks if any models need to be updated. This uses a Cassandra query which has no "where" clause, causing poor performance for very large clusters. For immediate relief of this issue, the pulse configuration has been updated to increase the timing from 30 to 300 seconds so it fires less often. Model updates typically happen every x hours and often the pulse will not detect any models that would need to be updated. Further improvements in this process will be available in a future release.
SR-C77730 · Issue 437101
Resolved case lock release improved
Resolved in Pega Version 8.1.5
Cases created through the create work object were unnecessarily holding onto locks for up to two hours. This was traced to a defer-write scenario for mobile devices which did not return the correct status needed for "no further assignments". In order to resolve this issue, a new parameter "returnNextActionInfo" of type boolean has been added to svcPerformFlowAction. This parameter will be always set as false when calling this activity from sync up so all locks will be closed and released.
SR-C80622 · Issue 424876
GenerateContainer updated to prefer icon given in skin over hardcoded icons
Resolved in Pega Version 8.1.5
When trying to change the Expand/Collapse icon for dynamic layout by defining a custom format in the app skin, changes made in the Expand icon image and Collapse icon image were not reflected. This was due to the CSS selector being overriden with a hardcoded arrow icon instead of automatically taking the icon from the skin rule. To resolve this, the selector and conditions used in GenerateContainer.java have been modified such that the icon added in the skin should be picked automatically instead of any hardcoded icon available.