INC-217680 · Issue 717606
Tab name displayed correctly in embedded mashup portal
Resolved in Pega Version 8.6.5
"Work Item" was given as as the tab header instead of the Case ID# when a case link was clicked/opened in an application embedded in an external site (IAC). This was traced to the pega.desktop.support.doGadgetAction function not calling the regular handleGadgetLoad function in this scenario, and has been resolved by explicitly directing work items opened in a multi-doc mashup portal to use handleGadgetLoad.
INC-218265 · Issue 720613
DoClose updated to resolve lock and context issues
Resolved in Pega Version 8.6.5
An interaction case was closing when intent tasks were closed from CSRecents. Investigation showed this was due to the doClose activity not being triggered in the right context, and has been resolved. An additional issue with locks not being correctly released after opening the new case Create stage and clicking Cancel in the modal was traced to a missing pyWorkPage in the safeURL params that was needed by the doClose activity, and this has been resolved by adding the primary page name.
INC-218855 · Issue 718835
DSS added to control section collapse on refresh
Resolved in Pega Version 8.6.5
After update from 8.5, using dynamic layouts that included certain controls (autocomplete/text/dropdown) configured with Refresh-Other Section -> Parent / Top Level Section such as a pyCaseActionArea with Event 'On Change' showed a different behavior: entering a value in the configured text/auto-complete field that leads to the refresh of the top level section will collapse all expanded sections if there is a refresh trigger within the embedded section or dynamic layout of the collapsible layouts. In order to control this behavior, a new DSS has been introduced. By default HonourExpandWhenOnRefresh (owning ruleset Pega-UIEngine) will be set to false to maintain the current behavior of collapse on refresh, while setting it to true will use the older behavior of maintaining expanded sections.
INC-219310 · Issue 717114
WorkSearchGadget updated in Theme-Cosmos-02-01
Resolved in Pega Version 8.6.5
The search icon was not working in Cosmos after update, which was traced to the search icon not having an action set. This has been addressed in Theme-Cosmos-03-01, but in this scenario Theme-Cosmos-02-01 was set as the Application definition instead of Theme-Cosmos-03-01. To resolve this, Theme-Cosmos 02-01-01 has been updated to use the newest version of the @baseclass.WorkSearchGadget section.
INC-220363 · Issue 720120
Additional page sizes available for PDF generation
Resolved in Pega Version 8.6.5
Support has been added for using page sizes in PDF generation which are supported by the v4 pd4ml jar including A0-A10.
INC-220459 · Issue 720884
Able to expand rows when other rows are expanded
Resolved in Pega Version 8.6.5
When multiExpand, threadProcessing, and readonly flags were true, attempting to expand multiple rows at the same time collapsed already opened rows and generated an error indicating "target is not defined". This was caused by 'handleEditItem' not calling the collapse functionality for an opened row correctly, and has been resolved by adding a check which allows the expansion of multiple rows for readOnly details.
INC-220989 · Issue 719866
Improved accessibility on create harness
Resolved in Pega Version 8.6.5
Hitting the tab key was navigating out of the popup on the create harness. This has been corrected.
INC-222507 · Issue 721695
Helper text added to clarify maxlength enforcement
Resolved in Pega Version 8.6.5
It is possible to enter more characters into a browser field than is specified by the maximum character limit unless read-only formatting is used. This is due to the resulting HTML input tag having the type of number, which leads to the browser default behavior of not honoring the maxlength attribute. In order to clarify this, helper text has been added with the message "Min and Max characters are ignored for type Number when 'Display value using read-only formatting' is unchecked."
INC-222922 · Issue 722993
Validations fire on collapsed accordion layouts
Resolved in Pega Version 8.6.5
Client validation was not firing on the selected tab of a layout group if the accordion layout was collapsed. If focus was switched to the second tab, the client validation on the first collapsed tab did not work. This has been resolved by modifying the 'else if' condition to pass the validation for the fields places in layout group tabs.
INC-224446 · Issue 724369
Load more works in non-templatized layout
Resolved in Pega Version 8.6.5
After adding a repeating dynamic layout inside a tab group layout (which is a deprecated feature) to make it non-templatized, the progressive pagination option to show the "load more" button did not work. This was caused by the load more functionality having a dependency on pega.ui.RDL even though pega.ui.RDL was not available in case of a non-templatized grid, with the result of generating an exception which broke the flow. This has been resolved by adding a null check which will allow the flow to proceed whether the grid is used inside non-auto-generated or auto-generated elements. Please note that it is strongly recommend to update any deprecated layouts to Layout Group as it is a best practice to keep the code updated to avoid any compatibility issues.