INC-210126 · Issue 708782
Timeout added for Cassandra writes
Resolved in Pega Version 8.6.4
When using Customer Decision Hub with external C* deployment, attempting to stop a data flow run which was reporting stale threads for some partitions resulted in some of the partitions continuing to run while threads were waiting on the Cassandra save operation. This has been resolved by adding configuration for a timeout when waiting for the results of the save operation, with a default of 300 seconds.
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-163644 · Issue 652968
Error message handling added for nested page lists
Resolved in Pega Version 8.7
When a multiselect referring pagelist(x).pagelist2() had an error message, the error was repeated for all pagelist(y).pagelist2() in the UI. This has been resolved by adding error handling for nested page lists by using registerErrorMessages for multiselect errors.
INC-202447 · Issue 698659
Updated variable handling for filter logic to avoid reuse
Resolved in Pega Version 8.6.4
When adding the property "ItemStatus" as a filter for a report, the validation message: "This property does not exist or has no column mapping" appeared. This was traced to an empty caption for a class join property used in
INC-205075 · Issue 698741
Updated variable handling for filter logic to avoid reuse
Resolved in Pega Version 8.6.4
When adding the property "ItemStatus" as a filter for a report, the validation message: "This property does not exist or has no column mapping" appeared. This was traced to an empty caption for a class join property used in
INC-179175 · Issue 664047
Mobile barcode scan sets value with correct context
Resolved in Pega Version 8.7
After implementing a list of items where each has a unique barcode, scanning the barcodes using the mobile app worked correctly the first time but subsequent scans were setting the value on the first element of the list and missing the context of the current scan position. This has been resolved with an update to ensure the scan barcode action sets the value on the correct property when using repeating dynamic layers.
INC-187610 · Issue 672841
Logic made consistent for design time group condition
Resolved in Pega Version 8.7
An inconsistency was seen between the logic string that appears when switching from "Group ORs" mode to "Use advanced logic" mode at design time, though whichever mode was used at Action check-in was always properly reflected on the generated proposition filter so there was no runtime impact. This design time issue was traced to the property "pyGroupConditionsByOld " being empty: this property is transient so its value will not be saved into database. This property should be updated whenever user changes the Logic operator from the drop-down, and this has been resolved by adding an intermediate property to hold the old group condition value when it changes.
INC-172874 · Issue 654366
AccessGroup timeout restores session on relogin
Resolved in Pega Version 8.7
When using Platform Authentication AuthService with "Use AccessGroup Timeout", a timed-out user who logged back in saw all open rule tabs were lost and any changes to checked out rule were not saved. Investigation showed that the URL for the redirected login screen did not have a slash at the end of the path of the app alias, causing it to not maintain a cookie path and instead start a new session on login. This has been resolved by adding the missing slash after the app alias in both the Ajax response and SecurityUtils to avoid creating a new session with a new requestor when logging in again after timeout.
INC-142557 · Issue 600528
Accessibility added to Recents
Resolved in Pega Version 8.5.2
Under all recent items, the work object was not opened when using the keyboard and the focus was on the work object. Clicking with the mouse worked. Investigation showed that on pressing the enter key, actions were not triggered because the action string was not on the same SPAN tag (but in child node). This has been resolved with an update to add tabindex on the same span where action-string is added. In addition, accessibility was not enabled on the out-of-the-box Recents table because the work object elements in the table used a formatted text control; this has been updated to use a link control which will enable the accessibility feature while using keyboard navigation.
INC-140101 · Issue 597637
System will attempt to decrypt data ending in "+"
Resolved in Pega Version 8.5.2
Encrypting and decrypting one specific email address was not working properly when showing on the UI. It was possible to force a decryption using decryptproperty, but Pega generated an error. This was due to the actual encrypted value ending with '+', which conflicted with a system check that skips decryption if the encrypted property value ends with + . To resolve this, the system will attempt to decrypt the property even when encryptedText ends with + .