INC-211018 · Issue 707524
Number control correct when IME is Japanese
Resolved in Pega Version 8.6.4
The Microsoft Windows Input Method Editor (IME) allows developers to enter complex characters in four different East Asian languages using the standard keyboard. When IME was in Japanese mode, entering a number resulted in the input happening twice with the result of an entry such as 12345 becoming 124512345. This has been resolved by updating the code to ensure there is no duplicate IME keyboard event.
INC-204256 · Issue 701948
Helper Text displays for radio buttons with 'when' condition
Resolved in Pega Version 8.6.4
The helper text overlay was not displaying on radio button fields that were conditionally visible using a 'When' rule, though it displayed as expected if a visible expression had "Run visibility condition on client" checked. This has been resolved by adding support for a helper text overlay on radio button with visibility condition (when rule).
INC-212509 · Issue 708358
Support added for Checkbox control for property with declare expression
Resolved in Pega Version 8.6.4
The checkbox control was not displaying the true/false text configured for the control in section when using a property with declare expression. This has been resolved by adding the logic necessary for this use case.
INC-215582 · Issue 712286
Cosmos calendar icon handles allow entry set to no
Resolved in Pega Version 8.6.4
When using the Cosmos theme, the Calendar icon became disrupted when "allow text entry" option was set to "no". This has been resolved.
INC-199469 · Issue 707513
PDF margins made available as parameters
Resolved in Pega Version 8.6.4
After update, margins were different in exported PDFs. This was due to upgraded jar files: PD4ML v3 used setPageInsets(new Insets(top, left, bottom, right)) , but the v4 jar uses setPageMargins(new PageMargins(left, top, right, bottom)) . Because the order of values (20, 10, 10, 10) were not changed this produced a different result. To resolve this, PD4ML margins are now available to be set as parameters: Param.pyMarginLeft, default value 20 Param.pyMarginTop, default value 10 Param.pyMarginRight, default value 10 Param.pyMarginBottom, default value 10 When standard activities like HTMLToPDF / pyViewAsPDF / pyAttachAsPDF are used, add a Property-Set step before calling the activity to add the necessary margin parameters. When CreatePDF smart shape is used, set the parameters via the connector of the CreatePDF.
INC-204349 · Issue 704563
Updated check for portal name with search
Resolved in Pega Version 8.6.4
After update, using search from a Cosmos portal landing page launched the results in a new tab, and the logoff menu did not show which portal was being used. This has been resolved by updating the 'when' rule to check if pxThread.pxPortal contains the portal name rather that testing for equality.
INC-207593 · Issue 702427
Spell Check flag removed from Preview and Public Articles
Resolved in Pega Version 8.6.4
If the spell check button was used when editing a Knowledge Management article, flagged words that were not corrected or set to be ignored continued to display the red flag even when previewing or when the article was being viewed from a public help site. In order to support not showing the flags while previewing or viewing from the Knowledge Management help site, an addition has been made to sanitize underlined words before save or submit.
INC-187196 · Issue 680749
Resolved Ajax popup alert for optimized iOS table
Resolved in Pega Version 8.6.4
When using an application on iOS with a section that contained at least 3 tables with 'optimize code allow' set to true, refreshing caused the error "AJAX request failed. Reason: communication failure" to be displayed. This has been resolved by adding an update which will skip the alert for the pzBuildFilterIcon activity when triggered from pzpega_ui_template_grid_helpers.
INC-215912 · Issue 711380
Corrected links being replaced by KM rich text editor
Resolved in Pega Version 8.6.4
When brackets/parentheses were encountered in URL links in the rich text editor used in Knowledge Management, those links were removed and replaced with a # (pound symbol). This was due to a legacy cross-site scripting security mitigation, and h as been resolved.
INC-209071 · Issue 706040
Other Currency resolves value in Pega DX
Resolved in Pega Version 8.6.4
When using Pega DX with the pxDisplayText currency set to "Other currency", only the property name was sent as part of the metadata and not the actual value. This has been resolved by updating "Other currency" to resolve the property reference and get the value.