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-146752 · Issue 602935
File Listener made more resilient
Resolved in Pega Version 8.4.4
When file listener encountered a FileNotFoundException as a consequence of sporadic AmazonS3Exceptions, the listener was disabled and no retries were made. In order to make the file listener more resilient, FileMatchConcentrator has been updated. While file listener is running and trying to get the next set of files, if the isDirectory() method returns false due to a non-existent directory or some other intermittent issues, instead of throwing an exception and shutting down the file listener, the system will now log the exception and continue.
INC-147856 · Issue 607134
Description input for new reports restricted to 64 characters
Resolved in Pega Version 8.4.4
After saving a report with a description containing more than 64 characters, trying to delete the same report generated error messages saying the report description exceeds 64 characters. There was no maximum character limit set on the description input when creating/editing/save as a report. The delete modal shows any page-level warnings, so the guard rail warnings show up at that time. This has been resolved by disallowing the creation of a description greater than 64 characters in length.
INC-141940 · Issue 601543
Revoke Access Token check removed from OAuth Client Registration
Resolved in Pega Version 8.4.4
When client credentials were implemented, the OAuth 2.0 Client Registration form was designed such that once the instance was created and a token issued, the access tokens were deleted on save. Process changes now indicate that it should be possible to save the form because it may only have History Description/Usage changes made to it and Revoke Token and Regenerate Secret buttons are already available. To address this, the Revoke Access Token check has been removed from the validate activity of Client Registration.
INC-148552 · Issue 607369
Added ability to disable dirty form browser alerts
Resolved in Pega Version 8.4.4
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-142145 · Issue 594915
Resolved 403 error for refresh of incognito window with CSRF
Resolved in Pega Version 8.5.2
Opening the simpleurl in a fresh incognito window opened the work object in a standard thread, but on refresh of the window a 403 error appeared and the screen went blank. This was a missed use case for the recently-added CSRF validation for non-ajax get requests which are redirected post requests. The CSRF token was being validated if pzPostData was in the request, but once the original request was complete the request map was cleared and the pzCtkn value in the request map was empty, resulting in the 403 error. To resolve this, the system will skip CSRF validation for a refresh scenario where the post data request map is empty after the original request, and validation has been added for the blank pyActivity in the request.
INC-144888 · Issue 603616
Custom rich-text editor plugin support updated
Resolved in Pega Version 8.5.2
At runtime, two rich-text editors were used in the same harness under two different sections, one regular and one hidden till clicked. A custom plugin was implemented for rich-text editor at the harness level. After upgrade, the custom plugin was not getting displayed in the hidden rich-text editor. Investigation showed that if plugins were added to pega.ctx.customrich-text editorPlugins, then the plugin manager discarded plugins from pega.u.d.customrich-text editorPlugins. To resolve this, the rich-text editor plugin manager has been modified to merge the plugins from pega.ctx.customrich-text editorPlugins and pega.u.d.customrich-text editorPlugins.
INC-144888 · Issue 603618
Custom rich text editor plugin support updated
Resolved in Pega Version 8.4.4
At runtime, two rich text editors were used in the same harness under two different sections, one regular and one hidden till clicked. A custom plugin was implemented for rich text editor at the harness level. After upgrade, the custom plugin was not getting displayed in the hidden rich text editor. Investigation showed that if plugins were added to pega.ctx.customrich text editorPlugins, then the plugin manager discarded plugins from pega.u.d.customrich text editorPlugins. To resolve this, the rich text editor plugin manager has been modified to merge the plugins from pega.ctx.customrich text editorPlugins and pega.u.d.customrich text editorPlugins.
SR-A79678 · Issue 254551
Rule-Parse forms in SI converted to harness based
Resolved in Pega Version 7.2.2
When opening an instance of the class Rule-Parse-Infer or Rule-Parse-Transform in the Smart Investigate for Payments application, the data was not rendered in the form but instead displayed as an XML page. This was due to rule forms being form-based, and an enhancement has been added to convert them to harness-based. In addition, the rule types Rule-Parse-Infer and Rule-Parse-Transform are no longer marked as deprecated so they may be fully utilized with the Pega SI Framework 7.11 and Pega engine releases going forward.
SR-A23701 · Issue 257746
Archive/ Purge JVM dependence removed
Resolved in Pega Version 7.2.2
If the JVM was shut down in the middle of the purge and archive process, some SLA queue items remained in a 'now-processing state' and were not automatically picked up by the SLA agent for rescheduling when the JVM was brought up again. This has been fixed by redesigning the the Archive/ Purge flow to run in the background in queue batches so SLA queue items will be updated immediately with their next goal. With this approach, updates of SLA queue items will not depend on purge and archive process duration, and SLA queue items will always be in a scheduled state.