INC-174699 · Issue 652070
Work objects can open in multiple tabs with Layout group
Resolved in Pega Version 8.5.4
After implementing the Worker portal with Layout Group(Tab) to open work objects and other options (Pulse, Spaces, My Cases etc.) in multiple tabs, the tabs opened as expected the first time but after all of the tabs were closed any newly opened cases appeared in popup windows instead of tabs. Investigation showed that when the last tab was closed, the display was set to the main div container of the ajaxcontainer so opening the work object again used a new window. Tab Group has been deprecated in the current Pega version, but the site has a requirement to open the cases in same way as they appeared with Tab Group; to resolve this, support has been added by making the width 0 for the active header highlighter instead of using display none for the main container for this configuration.
INC-174921 · Issue 652320
Client Side required validation applied to dropdown Date field
Resolved in Pega Version 8.5.4
The mandatory validation on submit of the screenflow screen was not being triggered even though 'Required' was configured on the Date field.This was traced to the validation being applied to a hidden field when the date time control is configured in dropdown mode, and has been resolved by adding a condition for validating this configuration.
INC-155878 · Issue 645364
Class list updated when using ActivateDocument in portal navigation
Resolved in Pega Version 8.5.4
Global search worked the first time it was used, but failed after another case was opened from the dashboard or there was a click on any landing page home, dashboard, or space. Investigation showed this was caused by the pySearchText being blank in the clipboard, which was traced to a harness context issue related to pega.desktop.activateDocument being used in pzPortalNavigation on DynamicLayout with Application Logo and Application label. To resolve this, an update has been made that will update the class list with the proper one when the data-harness-id is set.
SR-C84033 · Issue 422745
Added handling for legacy page adaptors to get all messages
Resolved in Pega Version 8.2.2
If a validation message was present on the Clipboard, the front-end screen was turning blue and displaying the error "There has been an issue, please consult with administrator". This happened when getMessagesAll was called for pyWorkPage and an auto-populate property was present in the embedded pages/properties. To resolve this, cast has been removed when getting all messages and a new API has been added for legacy page adapters to get all messages.
SR-D10966 · Issue 475333
IH summary behavior change reverted
Resolved in Pega Version 8.2.2
Changes introduced to Interaction History aggregations in 8.1 intended to better align them with the existing behavior of the Interaction History shape in Strategy produced the unexpected side effect of lots of empty records. Based on feedback, the decision has been made to revert the IH aggregation behavior change.
SR-C96456 · Issue 436307
Autocomplete grid scroll bar fixed for large DataPage results
Resolved in Pega Version 8.2.2
When autocomplete (default setting) was present inside a grid and the result popup had < 20 results, the scrollbar was not coming up in Google Chrome. This has been resolved by modifying the fixGridWidthIfRequired API to set set vertical scroll to auto.
SR-C97399 · Issue 439742
Button type added to allow grid expand in Edge
Resolved in Pega Version 8.2.2
When using an expand pane grid in a modal with the Edge browser, clicking on the expand icon using the enter key was throwing an error in new window. This was traced to an issue with a hidden non-auto-generated button in the pzModalHelp control not having a default type, and has been resolved by adding type="button" in the control so Edge will treat it as a submit button.
SR-D10100 · Issue 463307
Bulk actions filter works properly when additional filters are added
Resolved in Pega Version 8.2.2
The Bulk Actions filter was not working if other filters were used in conjunction with it. Investigation showed that when 'assigned to operator' was given a value, the values were fetched properly. When an additional condition was added, the section 'pyBulkProcessingSearchSection' activity called 'pzDefaultOperators' which then set the 'pyUserIdentifier' value to null, and no results were returned. As the activity already had a step to check if the .pyUsage!="Operator" and only then property-set, pyUserIdentifier = "", the subsequent step to set the pyUserIdentifier = "" and override the previous step has been removed.
SR-D10171 · Issue 482472
Updated UtilsEmailListener to handle additional special characters in the email ID
Resolved in Pega Version 8.2.2
When the Email Listener tried to map the properties from the email body and message header to the Pega Default out-of-the-box properties or user provided text properties, the mapping worked for simple alphanumeric email IDs, but mapped only the trailing part of the address if the Email ID contained an apostrophe or single quotes. For example, "toast.'[email protected]" was mapped as "[email protected]". This was due to a missed special character in the regex pattern, and UtilsEmailListener.java has been updated to correctly handle special characters in the email address as specified in RFC 5322.
SR-D10281 · Issue 482814
Configuration settings introduced for VBD read/write consistency
Resolved in Pega Version 8.2.2
Exports of VBD data at different consistency levels showed data inconsistency between Cassandra nodes. VBD uses the default DSM consistency level of ONE for its reads and writes, which will not automatically repair data when inconsistency exists. Data inconsistencies can lead to VBD timeouts trying to load partition data. To support VBD read/write integrity, an enhancement has been added to allow configuration of VBD read/write consistency levels by way of the following DSS properties (Owning Ruleset: Pega-DecisionEngine): vbd/readConsistencyLevel and vbd/writeConsistencyLevel. R + W > N where R is the consistency level of read operations, W is the consistency level of write operations, and N is the number of replicas. These will override the default DSM read/write consistency levels (ONE).