INC-148154 · Issue 602922
Hot Fix Manager updated to use installation order for schema import
Resolved in Pega Version 8.4.4
Schema changes were not being imported during the hot fix manager DL import process. Investigation showed this was due to hotfixes in the DL being iterated over from newest to oldest, causing older hotfixes to replace the value added to a map by the newer. To resolve this, the system has been updated to use hotfix install order, which considers selected and dependent hotfixes, rather than ordering newest to oldest. This ensures that newer table representations will override older rather than the other way around.
INC-132500 · Issue 602634
Updated class name resolution for runtime with after-screen render load
Resolved in Pega Version 8.4.4
Rule Resolution was not working as expected with the dropdown property “.ErrorType”, if the load behavior was configured as “After screen renders”. This was traced to the Class name resolution not happening at runtime, and has been resolved by moving the code related to class names to runtime.
INC-133951 · Issue 584147
Try catch added for templated refresh when
Resolved in Pega Version 8.4.4
After configuring a refresh when condition on a dynamic layout triggered by changes on D_worklist.pxResults, a component stack mismatch error was generated if client side UI template is enabled. Without templatization it worked as expected. This has been resolved by adding a try catch block to DynamicLayoutGenerator.java.
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-136563 · Issue 607420
Tenant Switching updated
Resolved in Pega Version 8.4.4
When working on new “tenant switching” implementations in a multi-tenant environment, the API itself seemed to be working as expected (case details from another tenant were shown correctly in review mode), but clicking on the assignment unexpectedly opened the case in a new window that contained the same review view of the case rather than the perform view. Clicking the assignment link again caused yet another review window to open with the same issue, over and over. This has been resolved by adding a UI-side update to send the requests on proper sub-domain URL instead of using the parent domain, and by ensuring the document threads are properly deleted for multitenant usecases.
INC-137100 · Issue 604060
Added predictive text handler for Japanese on iOS
Resolved in Pega Version 8.4.4
The autocomplete function was not working well in MobileView when using Japanese IME on iOS. This has been resolved by adding a new input handler for IOS mobile, which will be triggered when predictive text is selected in mobile.
INC-137757 · Issue 600491
Primary page setting updated for micro DC container
Resolved in Pega Version 8.4.4
In Cosmos, a "Cannot Render Section" error displayed on submit of modal dialogue. This was caused by a primary page calculation error for the micro DC container, and has been corrected.
INC-137875 · Issue 608104
Update for special characters in operator name
Resolved in Pega Version 8.4.4
Handling has been added for encoding an operator full name field which contains special characters.
INC-137915 · Issue 604618
App Studio compliance tool shows category results
Resolved in Pega Version 8.4.4
After upgrade, results were not displayed categorically while running the app studio compliance tool: only the number of total issues was available. Investigation showed that pzLPApplicationGuardRailsInnerTable was not resolved correctly, and since there was no object class defaulted there was an issue in creating the results in the correct class. This has been resolved.
INC-137966 · Issue 597738
Embed-ReportFilter supports pyDateproperties
Resolved in Pega Version 8.4.4
After creating a report definition with Date time filter values where the 'from' date and 'to' date are input and propagated as “pyStartDateTime” and “pyEndDateTime” in the clipboard, opening the pyDate properties from clipboard resulted in a 'rule not found' exception. No properties of other data types generated the error. This has been resolved by creating the pyStartDateTime,pyEndDateTime and pyDisplayTimeperiod properties in Embed-ReportFilter to support this use.