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.
INC-144358 · Issue 601014
Localization added for "Automatically" and "Manually" field values
Resolved in Pega Version 8.4.4
The Dutch translation of "Child case [Case_type] [Case_id] has been [Instantiation_mode] instantiated" used the hard-coded English expression "manually". This has been resolved by adding the "Automatically" and "Manually" field values to localization.
INC-146174 · Issue 602868
Chevron vs Back button in screen flow made consistent
Resolved in Pega Version 8.4.4
When using the TabbedScreenFLow7 harness with the "Enable navigation Link" and "Only allow navigating back to step" settings for the flow along with client-side validations, the validations were ignored when using the back button but using the chevron displayed a validation error. Investigation showed that the case action area buttons and bread crumb navigation were out of sync during the back button operation. This has been resolved by updating the ProcessStep function in BreadCrumbTrial library to pass skipValidations while calling gotoprevioustask.
INC-146339 · Issue 600745
ViewID parameter passed as part of DX API response payload for level 5 applications
Resolved in Pega Version 8.4.4
Recent work to not consider production level and always pass 'viewID' parameter as part of DX API response payload was not working for cases where the APIProductionLevel was 5. This was a missed use case based on a condition that remained on the ViewID parameter, and the condition has now been removed.