INC-223222 · Issue 723634
Corrected apiContext when using bulkActions
Resolved in Pega Version 8.7.3
Row selections in the multi-selection table were intermittently not working after opening a table with bulk actions enabled. Investigation showed that opening a table with bulkActions enabled and then navigating to a table where bulk actions are not available but multi-select is enabled led to functions like setSelectedRows and getSelectedRows still being available in apiContext. This has been resolved by correcting apiContext when bulkActions is enabled.
SR-D23239 · Issue 496707
Support added for multi-operator SAML logins
Resolved in Pega Version 8.2.3
When a SAML user logged in by Single Sign-On (SAML), the system processed the login to portal as a different operator if there was a function on the Attribute field under Operator identification in the SAML authentication service. In this scenario, using an expression for operator provisioning did not work because all SAML login sessions resolved to same first operator due to parseAndEvaluateExpression() in ExpressionHelper.java ignoring new expression arguments if the expression page already existed. To support the use of multiple operator logins in this format, the system has been updated to clone a new expression page for every session and update it with the correct expression arguments.
SR-D71105 · Issue 532189
Corrected error when using CharCounter in non-template mode
Resolved in Pega Version 8.2.6
An error message was generated when trying to save a section with the TextArea's Display CharCounter set to True. This was traced to an error in the remaining character count span generation for non template mode and has been corrected.
SR-D82298 · Issue 544631
Corrected error when using CharCounter in non-template mode
Resolved in Pega Version 8.2.6
An error message was generated when trying to save a section with the TextArea's Display CharCounter set to True. This was traced to an error in the remaining character count span generation for non template mode and has been corrected.
SR-D16327 · Issue 487447
Updated logic for Bulk Upload count when background processing is used
Resolved in Pega Version 8.2.3
When multiple items were queued as part of "Bulk Upload" and the "Transfer To" operation was used with "BULK PROCESS in BACKGROUND", discrepancies were seen in the email received. For example, if two items were selected for transfer, email notifications stated that 1 item was selected and 1 item was processed instead of 2. This was traced to using 'process in background': when selected during bulk processing, the first record is processed in the foreground and remaining records are processed in the background. When the system sent the email notification once the background process was done, the total records computation was not considering the foreground-processed record, and the count was off. The timing logic has been updated to account for the foreground record to resolve this.
SR-D28869 · Issue 499316
Resolved Tooltip not relaunching after hide when using autocomplete controls
Resolved in Pega Version 8.2.3
When a tooltip was configured with SmartInfo and 'Auto-dismiss on hover away' was not checked, the tooltip disappeared when an autocomplete control was clicked and could not be reopened afterwards. The tooltip behaved as expected when it used input text control. This behavior was traced to autocomplete controls being set to hide all other active popovers because autocomplete results are displayed in a popover and only one active popover can exist on the DOM. However, it was seen that the tooltip's Smartinfo popover status was still active even though it was hidden, which is why it could not be launched again. To resolve this, when an autocomplete control is clicked, any active popovers being hidden will also be marked as inactive.
SR-D23906 · Issue 499988
Case status correctly updated when using RDA
Resolved in Pega Version 8.2.3
When a Assignment was routed to a work queue and Flow Action post processing was set to trigger an RDA Automation to update some case property, an error appeared saying there was no data available on the Page and the case status was not updated when it moved to the next stage. This was an issue with case status not being correctly updated when using robotic automation, and has been resolved.
SR-D29416 · Issue 500133
Email template content editors visible when using Smart Investigate
Resolved in Pega Version 8.2.3
When specialized email correspondence templates were used with the Smart Investigate Framework, the correspondence rules did not have all the default values used in visibility conditions. This caused the 'when' rules pzShowSourceOnlyEmailEditor and pzShowBasicEmailEditor to evaluate to false and not display the source stream. To resolve this, UpgradeOnOpen has been added for correspondence rules to set the value for the visibility of rich text editor for source code viewer in order to support the use of custom templates with Smart Investigate Framework.
SR-D74247 · Issue 542916
Resolved errors when using Build Model from the Preview Console
Resolved in Pega Version 8.2.6
Using the Web Chatbot interface and trying to perform Build Model action from Preview Console failed with multiple errors, either "This action is not allowed as it is outside the current transaction" or "class <blank> doesn't exist". This was traced to issues with the transaction during model update, and has been resolved by conditionally disabling the show page step of pzGetModelProcessStatus. This step creates a difference in the context of the current transaction and is disabled when called from Update API.
SR-D15391 · Issue 484922
Add row works as expected when using Embedded Elsewhere with a modal grid
Resolved in Pega Version 8.2.3
When using Embedded Elsewhere, add row was not working on the first attempt for a grid launched inside a modal dialog. Changing the focus then resulted in the added row appearing. This has been resolved by updating the timing for the performInsertAction in the ui_grid JS.