INC-144399 · Issue 599716
Custom dropdown controls updated for classnames
Resolved in Pega Version 8.4.4
After upgrade, a customized format for Dropdowns was not picked up. This was due to recent changes made to Class name attributes to ensure they are populated for all controls, and was caused by the CSS selector not picking the necessary DOM element. This has been resolved.
INC-144462 · Issue 601370
Added logoff check for requestors
Resolved in Pega Version 8.4.4
After upgrade, the error "java.lang.InterruptedException. Requester has been destroyed" was appearing in the logs. Investigation showed this was related to unregister requests being submitted after logoff, and has been resolved by updating the system to check for logout before sending unregister requests.
INC-144522 · Issue 612322
Portal primarythread copied to workprocessing thread to establish proper class
Resolved in Pega Version 8.4.4
Attempting to add a new item/row in a table configured in a modal dialog in the home page of the Cosmos portal was not working, and the error "Section 'TestSection' execution error on page 'pyWorkPage' of class 'CosmosApp-Work-TestCaseType'. : For input string: "" appeared. This was a missed use case for pyPortalHarness, and was caused by the primarypage not getting copied to the workprocessing thread which led to some actions failing as classless. This has been resolved.
INC-144543 · Issue 600086
Keyboard accessibility added to Cosmos buttons
Resolved in Pega Version 8.4.4
Focus states were missing on the standard and icon buttons in Cosmos. These have been added to facilitate keyboard navigation.
INC-144572 · Issue 600758
Corrected mobile tab layout highlighting
Resolved in Pega Version 8.4.4
When switching between three tabs in a layout group (Other – Mobile Tabs) in a section, the highlight was appearing on the active tab and the inactive tabs. This has been resolved by updating the CSS generation to not consider hover styles for touchable devices.
INC-144709 · Issue 608797
Removed unnecessary decoding from GetDropdownOptions
Resolved in Pega Version 8.4.4
When using a dropdown sourced by a data page with parameters in the section, passing multiple values as the parameters of the data page resulted in the error "pzGetDropdownOptions:Invalid JSON Stream for data page params" and the parameter values were not resolving at runtime. This was traced to unnecessary decoding in the process, and has been resolved.
INC-144851 · Issue 604482
Date Time picker works with locale es_US
Resolved in Pega Version 8.4.4
When an Operator had the locale es_US (Spanish) set on the Profile, the Date Picker on the application was throwing validation errors when a date or time was chosen from the out-of-the-box Date Time Control. Investigation showed the date-time format for locale es_US was not supported, and the getDateTimeFormat API has been updated to support this format (11:00 a.m.).
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-144924 · Issue 614769
System improvements related to ActiveDocumentType
Resolved in Pega Version 8.4.4
Alerts were seen for unexpected properties in HTTP requests related to pyActiveDocumentType, and system slowness was seen when the request was trying to update the properties. This was traced to a condition where a page remove cleared property registration, and has been resolved.
INC-145119 · Issue 601713
Client side validation works with Reference page property
Resolved in Pega Version 8.4.4
A reference page property in a 'when' rule was not evaluating properly for checking a Date field when client side validation or Client side template UI was checked on the Harness level. This was traced to pyRequired being boolean: the boolean being compared to a string false value yielded a wrong comparison, leading to the wrong validation type required. To resolve this, the system will use the === comparator to compare boolean false in datetime to remove the required validator.