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-D38492 · Issue 505489
Batching now enabled when using IH Summary shape in substrategies
Resolved in Pega Version 8.2.4
Batching was not being enabled when using IH Summary shape in substrategies. This was traced to the IH_SUMMARY_CACHE field not automatically being passed to sub-strategies, and has been corrected.
SR-D39003 · Issue 505997
Threads will be updated to maintain assembly context when using Static Assembler
Resolved in Pega Version 8.2.4
When running the Static Assembler utility from UI, the assembler process completed successfully but the PegaRULES.log was flooded with the FATAL exception "Usage error - next Executable not based on current". This error was generated from com.pega.pegarules.session.internal.mgmt.Executable constructor, and indicated an issue with the thread context being different from the assembly context. To resolve this, the system has been modified to update the context of thread to what is expected as assembly context.
SR-A6169 · Issue 214467
Corrected compilation error when using param.value in Repeat Layout label
Resolved in Pega Version 7.2
A compilation issue was encountered when a parameter was used in a repeat section cell due to the paramStrValue being double encoded. This has been resolved by adding a check that will skip the extraneous encoding.
SR-A5746 · Issue 213321
Ensured DateTime maintains read-only state when used with editable dates
Resolved in Pega Version 7.2
In a DateTime control with a read-only format set differently from an editable date format, the read-only format was being set to an editable date format when other fields were refreshed. This was an issue with calling the API, and has been corrected.
SR-A6169 · Issue 204154
Corrected compilation error when using param.value in Repeat Layout label
Resolved in Pega Version 7.2
A compilation issue was encountered when a parameter was used in a repeat section cell due to the paramStrValue being double encoded. This has been resolved by adding a check that will skip the extraneous encoding.
SR-A10406 · Issue 223580
Check added for page context when dropdown used in nested repeating grids
Resolved in Pega Version 7.2
A Dropdown placed in nested repeating grids with the event request onclick action "Post value" disappeared from the DOM on select of an option. This was due to an incorrect page parameter, and a check has been added to send the correct contextPage.
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.