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.
INC-138348 · Issue 599772
Added parameter skipPropertyEvaluation to handle CSS in email HTML
Resolved in Pega Version 8.4.4
While sending an email with custom HTML appended to the email body, a "+" sign in the body was causing the correspondence generation to fail. Investigation showed that if there were CSS classes with braces in the message body, the braces were being removed and replaced via "+" symbol in step 21 of CorrCreate activity. To resolve this, a new Boolean parameter skipPropertyEvaluation has been added in the CorrCreate activity to handle the decision to either evaluate the logic or not, and the pre-requisite will be to resolve all the property references before calling this activity so custom CSS braces { } will be honored when the message body is sent.
INC-140266 · Issue 602076
Search made consistent across environments
Resolved in Pega Version 8.4.4
Search was behaving differently based on whether the user was launching the search by clicking the search icon or hitting enter directly. The search icon passed the classes list and fetched cases based on that, whereas hitting enter performed the search without the classes list unless it was a multi-tenant environment. This has been resolved by updating the pyWorkIDSearch activity to pass application classes list in any environment.
INC-143025 · Issue 600611
API performance improvements
Resolved in Pega Version 8.4.4
Performance improvements have been made for running the get assignment action details API.
INC-144265 · Issue 609287
Updated timestamp handling for duplicate key issue with PyCompleteAutomation
Resolved in Pega Version 8.4.4
Occasionally a robot failed to complete a case due to a duplicate key exception. This was an issue with the History record creation due to duplicate key erlated to the timestamp, and has been resolved by updating the timestamp handling so that the REST API will use 'getCurrentTimeStampUnique' and for other cases 'pxGetCurrentTimeStampThreadUnique' will be used.