INC-218234 · Issue 734687
DSS added to skip 'Has Purge Happened Since Startup'
Resolved in Pega Version 8.8
The Purge Agent did not finish execution, exiting with the error "skipping purge because HasPurgeHappenedSinceStartup == false". This was traced to the local site policy of restarting their nodes every week, which was not aligned with the system default purge policy. To address this, a new DSS "skipHasPurgeHappenedSinceStartupCheck" has been added to the Pega-RulesEngine ruleset. When set to true, the check for 'Has Purge Happened Since Startup' will be skipped.
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.
INC-150367 · Issue 606030
Double quotes escaped in entity mapping
Resolved in Pega Version 8.4.4
A usecase where the BOTS created the triage cases from the emails and pushed it to the Workgroup had an intermittent problem where the screen would freeze and no actions could be performed. perform any action on the same. Investigation showed this occurred when the entity text contained double quotes which is caused JSON to break on the client side. This generated an exception during rendering, and other onload scripts failed on load and blocked the entire thread. To resolve this, the system will now avoid the JSON break by escaping double quotes in entity mapping.
INC-146595 · Issue 604791
Initialized entryName for light weight inventory instance
Resolved in Pega Version 8.4.4
When running deployment on a new pipeline created for the next minor version, once the deployment process got to the point of showing aged updates, the “view aged updates” came back as blank screen. Viewing the logs showed the aged update elements come back but were missing the pyName associated with them. Investigation showed that the system did not have support for setting the mEntryName for LightweightInventoryInstance objects. This has been resolved by adding a junit to ensure that getEntryName() doesn't return as null and should be equal to pzInsKey.
INC-136188 · Issue 604864
Icon focus indication made more consistent
Resolved in Pega Version 8.4.4
The focus on some main icons across the header in Designer Studio was inconsistent when tabbing through the header. Some icons showed a dotted border, for others the icon opacity changed on focus, and others had no focus style at all. An update has been made to ensure consistent dotted outlines on all header and footer icons on focus. The dotted outlines have also been added for all tabs on the application landing page for Dev Studio for icons such as the delete/ gear on all Repeating Dynamic Layout rows.
INC-212896 · Issue 711190
Resume Flow will print Flow Action Label in audit history
Resolved in Pega Version 8.8
After calling Resume Flow for processing the assignments, when the Assignment was processed the Flow Action Name was printed on the Audit History instead of Flow Action Label. Investigation showed that in the Complete assignment activity, there was no code in the 'if' loop to set the value of actionLabel. If the value was null, the property set in the next step sets actionLabel to flowActionID and the audit history result is FlowAction ID instead of FlowAction Label. To resolve this, logic has been added in the CompleteAssignment Activity step 5 to set ActionLabel with Flow Action Label.
INC-202480 · Issue 699081
Resolved report filter section freeze
Resolved in Pega Version 8.8
When opening a report with a count column, changing the order of one of the report columns resulted in the report freezing and requiring the report to be closed and re-run. This was traced to a double filter popup appearing that did not close after the column sorting, which happened if the report definition was configured as a summary with an aggregated column such as "Count” combined with a "Do not display group headings" setting on the Report Viewer tab. To resolve this, a new step has been added in the Activity pzPopulateSortOrder to call the pzCancelFilterLogicChanges activity.
INC-222791 · Issue 721370
GET API will skip case locking
Resolved in Pega Version 8.8
After update, performing a GET call on an assignment was unexpectedly locking the case. This was traced to a difference in handling: Pega 8.3 performed an Obj-Open-By-Handle of the workobject without acquiring a lock, while Pega 8.6 calls Assign-.acquireWorkObject which acquires a lock on the work object thereby affecting the other requestors from accessing the case. An initial fix for this issue enabled optimistic locking, however this did not resolve the issue in scenarios where there were concurrent calls and optimistic locking was not used. This additional update will skip locks on the work object for V1 GET assignments/{id}, GET assignments/{assignmentId}/actions/{actionId} and GET cases/{caseId}/actions/{actionId} and corresponding action refresh APIs.
INC-233513 · Issue 741983
Validation warning flag appearance made more consistent
Resolved in Pega Version 8.8
The warning "Please correct flagged fields before submitting the form!" was appearing inconsistently across the flow actions. Investigation showed that from the Todo Widget > Click on Link > Click on Go button. the assignment opened in an Ajax container so validations were triggered because it called the webwb • pzpega_ui_doc_submit • js file doFormSubmit() method which leads to the alert message. However, using Todo Widget > Go button caused the assignment to open in a Dynamic Container so no validations were triggered. This has been resolved by adding a new flag to skip field validation in certain cases to produce consistent behavior.
INC-153692 · Issue 620243
Added accessibility to Report view context menu
Resolved in Pega Version 8.4.4
When on the My Reports screen and a Summary report is selected, the Report Viewer displays a Summarized Reports table with a column header that opens a command menu upon right-click of the mouse. This functionality is enabled in the Report Definition rule by selecting the checkbox Enable column command menu under the Report Viewer tab. Although keyboard users can open the menu via Shift+F10, keyboard users who cannot see the screen were not informed that this functionality is available as the screen reader did not announce this. This has been resolved.