INC-223222 · Issue 723635
Corrected apiContext when using bulkActions
Resolved in Pega Version 8.8
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.
INC-178148 · Issue 660924
Handling added for SSO servlet name
Resolved in Pega Version 8.7
After update, logging into an external site was not working correctly due to the SSO URL being appended with "/app/default". This has been resolved by updating the code to handle the servlet name properly.
INC-188405 · Issue 673063
Handling added for SSO servlet name
Resolved in Pega Version 8.7
After update, logging into an external site was not working correctly due to the SSO URL being appended with "/app/default". This has been resolved by updating the code to handle the servlet name properly.
INC-216162 · Issue 718923
GetNextWork uses correct tabname
Resolved in Pega Version 8.8
Clicking on Get Next was showing the tabname as "Next" instead of the caseid when using the handleMdcTabs function. This has been resolved by setting the correct tabName in case of getNextwork.
INC-178417 · Issue 670114
Flag reset added for grid with 'Expand When'
Resolved in Pega Version 8.7
A grid using an 'Expand When' condition worked as expected when the condition was true, but once expanded the grid did not collapse if the expand condition was changed to false even if a section/harness refresh was performed. This has been resolved by adding an update which will reset the flag when the result of 'Expand When' is false.
INC-211018 · Issue 707525
Number control correct when IME is Japanese
Resolved in Pega Version 8.8
The Microsoft Windows Input Method Editor (IME) allows developers to enter complex characters in four different East Asian languages using the standard keyboard. When IME was in Japanese mode, entering a number resulted in the input happening twice with the result of an entry such as 12345 becoming 124512345. This has been resolved by updating the code to ensure there is no duplicate IME keyboard event.
INC-204256 · Issue 701949
Helper Text displays for radio buttons with 'when' condition
Resolved in Pega Version 8.8
The helper text overlay was not displaying on radio button fields that were conditionally visible using a 'When' rule, though it displayed as expected if a visible expression had "Run visibility condition on client" checked. This has been resolved by adding support for a helper text overlay on radio button with visibility condition (when rule).
INC-233058 · Issue 739763
Helper Text displays for radio buttons with 'when' condition
Resolved in Pega Version 8.8
The helper text overlay was not displaying on radio button fields that were conditionally visible using a 'When' rule, though it displayed as expected if a visible expression had "Run visibility condition on client" checked. This has been resolved by adding support for a helper text overlay on radio button with visibility condition (when rule).
INC-180184 · Issue 665091
Assistance and diagnostics added for issue with opening imported 'when'
Resolved in Pega Version 8.7
After upgrade, attempting to open rules that were developed on lower environments and then imported resulted in unknown errors. A workaround has been added to skip and log any corrupted property that might be interfering with the rule opening: enable Skip-Corrupt-Property to put this in place. To improve diagnostics, the new logger NBA-WME-DEBUG has been added. If the error continues after using Skip-Corrupt-Property, Skip-Corrupt-Property should be disabled and NBA-WME-DEBUG should be enabled and kept active until the issue occurs again.
INC-165992 · Issue 657691
Table Filter save uses correct harness
Resolved in Pega Version 8.7
After creating a new view for table and then relaunching the portal or switching between tabs, the created views were not visible. Investigation showed that the views were saved under the incorrect pycaseworker harness on initial load, causing them to not be visible when returning from the switch and using the correct pyCWPortalContent harness. This has been resolved with the addition of the new parameter innerHarnessName to get the harness name when creating a personalization instance.