SR-D49507 · Issue 521413
Support added for Oneof/AllOf association prefix in ABAC policies
Resolved in Pega Version 8.4
The Report browser was freezing when attempting to save a report with an association rule where ABAC policies prevented access to one of the classes in the association. This has been resolved by updating the system to append the correct prefix in cases where the ABAC rule has Oneof/Allof Functions so the association is resolved correctly.
INC-145939 · Issue 606898
Updated handling for ID value change during REST connection creation
Resolved in Pega Version 8.4.4
When using the REST Connector Wizard to create a connector, if the ID was changed on the 4th (last) step of the Wizard and then the Create button was pressed, the screen would freeze and a display a javascript error. Investigation showed that when the ID was changed on the screen, the new value was not updated properly and subsequent function calls threw errors. This has been resolved.
INC-148115 · Issue 605423
Autocomplete results list position scrolls inside a table
Resolved in Pega Version 8.4.4
Given a row editable table with a fixed height and freeze grid header, when autocomplete was included in a row of a table and the down-arrow was pressed to get the list of options in dropdown, this drop-down popup was not moving along with the row during scrolling. This was due to scroll handler not being triggered for popover when inside a hierarchical table, and has been resolved.
INC-150407 · Issue 605842
Validation error messages correctly cleared in nested markup
Resolved in Pega Version 8.4.4
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-153109 · Issue 611354
Validation error messages correctly cleared in nested markup
Resolved in Pega Version 8.4.4
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-153555 · Issue 612228
Validation error messages correctly cleared in nested markup
Resolved in Pega Version 8.4.4
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-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-145535 · Issue 600787
Corrected layout group overlapping content
Resolved in Pega Version 8.4.4
When an editable Table with Master Detail Edit has a section that contains a Layout group (Tab) inside the Master Detail Flow Action, if there are more layout group headings than that can be contained in the screen, a left and right arrow are displayed to toggle between headings in the layout group heading bar. However, timing issues sometimes caused the contents of the layout group to overlap on top of the content below the layout group and the screen was freezing with a loading icon. This was traced to console errors, and has been resolved by adding an 'undefined' check to prevent those errors.
SR-D52144 · Issue 515673
When no active document is available on login, first document will be marked active
Resolved in Pega Version 8.4
After logging into the user portal, attempting to perform operations like (opening a case/work object, opening reports etc.) caused the browser request to spin or freeze. The only way to recover was to close and re-launch the browser window/session and re-login. This issue occurred when there was an active reportdefinition document before the browser/node crash in the tabless dynamic container(DC) portal. After recovery, the dynamic container did not recreate the report definition document but instead tried to activate the first document in the portal, which in this case was the default harness configured in the Dynamic Container. As it was not yet loaded, exceptions were thrown. To resolve this, when no active document is available, the first document will be marked as the active document.