INC-191674 · Issue 681575
Cosmos Stakeholders menu updated to prevent loss of work party change
Resolved in Pega Version 8.5.6
The Stakeholders menu for adding work parties to cases available in Cosmos Utility panel was not saving work party changes as expected when the case was also open for performing assignments. When the assignment was completed, the work parties were reset to the values present when the case was opened. The list of stakeholders is saved as a property in work page. When an assignment is opened there are two threads, and any stakeholder added is then added only in the first thread. Because it was not added in the second thread (acprimary Ajax container - processing assignment) the stakeholder addition was lost due to the second thread overriding the first thread. To resolve this, if an assignment is being processed while trying to open the stakeholders model, an additional modal will be displayed with the following options: - resign from opening stakeholders modal and continue process assignment or, - rresign from processing assignment (all unsaved changes will be discarded) and open stakeholders modal
INC-191785 · Issue 680929
Edit Validate Rule works after mobile section collapse
Resolved in Pega Version 8.5.6
It was possible to collapse a section of the UI on the mobile app and then proceed to the next page without entering valid data. This has been resolved by updating the validation condition to handle the mobile sections edit validate rule correctly.
INC-192075 · Issue 680776
Required field error message shown for Anypicker control
Resolved in Pega Version 8.5.6
Certain Anypicker controls set to required were not showing the expected error message "Value cannot be blank" in the UI when the field was submitted as blank. This has been corrected.
INC-192813 · Issue 684734
Corrected unexpected page refresh
Resolved in Pega Version 8.5.6
When a value was changed in a section where the source of the section was defined as a property, the page refreshed without any announcement and focus was disrupted. Investigation showed this happened when using paragraph control where an anchor tag was used without any Name attribute. An update has been made to explicitly set the gFocusElement property after the processAdditionalFields activity to resolve this issue. Because the Name attribute is needed to query the particular element from the DOM to focus back, there were also intermittent issues when using the Microsoft Edge browser with Windows OS even after adding Name in the paragraph control link. A setTimeout has been added before focusing the element to resolve this.
INC-193650 · Issue 687902
Corrected focus for changing optimized table density
Resolved in Pega Version 8.5.6
After selecting an option on the density filter button inside of an optimized table, the focus was set to the top of the browser rather than remaining inside the table layout. This has been resolved.
INC-194239 · Issue 685734
JAWS reads characters limits in grid text area
Resolved in Pega Version 8.5.6
A text area in a grid with a character limit was not reading the maximum characters and remaining characters when using JAWS. This has been resolved by adding the necessary aria attributes to the non-template text area control.
INC-194408 · Issue 686451
Resolved security error for new portal tab with BAC
Resolved in Pega Version 8.5.6
After configuring Show-harness in a popup window, a 403 unauthenticated error was seen on the activity pzTransformandRun even though the activity was registered. This has been resolved by ensuring the proper portal name is passed to new tabs when BAC is used.
INC-194446 · Issue 691353
Mobile app validates collapsed layouts
Resolved in Pega Version 8.5.6
Validation did not fire in the offline app when the fields were in collapsed layouts. This has been resolved by removing the validateHiddenFieldsInOffline flag for Offline.
INC-195321 · Issue 684970
Check added for readonly header control
Resolved in Pega Version 8.5.6
After configuring an optimized grid and adding a checkbox control in the header with editable options, when the control in corresponding column was configured as Auto, the checkbox in the header was rendered as read-only. When the control in the corresponding column was configured as "Read-only always" or displayText control was used, the checkbox was rendered as editable control. This was traced to a missing check for pyEditOptions = "Read-only", and has ben resolved.
INC-195581 · Issue 691841
Control menu code minified
Resolved in Pega Version 8.5.6
Minification has been turned on for control menus.