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-212623 · Issue 709549
HTML attachments conditionally shown in email listener cases
Resolved in Pega Version 8.6.4
When Rich text/html (non-plain text) emails were ingested in email, the original mail was not getting added to the case. Investigation showed that the pzCreateTriageWork activity had an explicit delete step to remove any attachment that started with 'email-content'. Since the HTML attachment name starts with 'email-content', it was deleted in above activity. This has been resolved by adding a when rule named 'pyLinkEmailTriageContentHTML' which will conditionally show email-content.html.
INC-213247 · Issue 708870
Title attribute added for disabled icons
Resolved in Pega Version 8.6.4
The disabled icon control in non-template mode used the tempTitle attribute instead of title, interfering with accessibility because no information was available to screen readers. This has been resolved by adding the aria-disabled attribute to the disabled icon control.
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-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-216358 · Issue 712230
Auto Complete working in Mobile Browser configuration
Resolved in Pega Version 8.6.4
Autocomplete was not working in the mobile browser when logged in as a user and configured with display mode:"in-a-table" and "display as full screen in mobile" disabled. Autocomplete results will always display in List mode in the mobile browser, but with the configuration "in a table" selected and "Display results full screen on phone" unchecked, pzGetACData (which gets called for List mode) was not registered and returned a 403 response. To handle this, the conditions file ActionAssembly.java has been removed so pzGetACData will always be registered.
SR-A8538 · Issue 222591
RepeatIndex generation improved
Resolved in Pega Version 8.1
Controls in a triple layout included in a row repeat did not have matching unique IDs and label for attributes. This was due to incomplete generation of the repeatindex for the ID, and has been fixed.
SR-C4920 · Issue 347563
Grid Header checkbox behavior modified for consistency
Resolved in Pega Version 8.1
Unexpected behavior was seen when clicking on the Checkbox present in Header: all other checkboxes changed their state (which was expected), but if the the Readonly checkbox was checked it was also changing the state the first time (which was not expected). After this first state change, the read-only checkboxes were not changing state (which is correct behavior). Previously, the behavior of Select All / CheckAll checkboxes was as follows: If the SelectAll / CheckAll checkbox is checked - Individual checkboxes are checked only when they are NOT disabled If the SelectAll / CheckAll checkbox is unchecked - Individual checkboxes are unchecked irrespective of their DISABLED state The behavior has now been changed as below: If the SelectAll / CheckAll checkbox is checked - Individual checkboxes are checked only when they are NOT disabled If the SelectAll / CheckAll checkbox is unchecked - Individual checkboxes are unchecked only when they are NOT disabled
SR-C7762 · Issue 350154
Commas removed from filter values to resolve validation errors
Resolved in Pega Version 8.1
When using a Grid layout configured in a section rule, clicking the Filter option and entering a comma separated value in the "To" field in a decimal-type column resulted in an "Invalid numeric range" option message. No error was seen if comma separated values were entered in both the "To" and "From" fields. Because the checkRangeFilter() function in ui_grid.js uses parseFloat() API to extract the decimal content entered in the search boxes, decimals after commas are ignored and validation failed due to the fields not matching. This issue has been fixed by implicitly removing any commas entered by the user.