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.
INC-139054 · Issue 598151
PD4ML library updated
Resolved in Pega Version 8.4.4
When generating a PDF, lines were broken up for the content boxes. This was an issue with the included version of PD4ML, and has been resolved by updating the version from 4.0.6 to 4.0.9fx1.
INC-139086 · Issue 597144
"Show next error" correctly displayed on user portal
Resolved in Pega Version 8.4.4
In the Case Worker user portal, the Show Next Error link was not shown when the layout group had a validate rule in the flow action. The same configuration worked as expected in Case Manager. This was a missed use case, and has been resolved.
INC-139790 · Issue 607416
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-139966 · Issue 606844
JAWS announces popup error message
Resolved in Pega Version 8.4.4
When a form is submitted without giving value to required field, a browser pop up appears. The expected behavior is that the screen reader (JAWS) should move the focus to the field that has error and read the error message However, JAWS was not announcing the error "Value cannot be blank". This was traced to a scenario where if pega.u.d.fieldErrorType === "ERRORTEXT" is true, the class on the span within the error div will be set to "inputSpans", and this resulted in the return of an empty array for document.querySelectorAll("span.iconError.dynamic-icon-error"). To resolve this, support has been added for the "inputSpans" class.