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-D29127 · Issue 506863
SAML data pages restored after passivation
Resolved in Pega Version 8.2.4
If login used SAML SSO, resuming the session after passivation resulted in missing or empty data pages when using an SAP integration with Pega Cloud. This was traced to a security change that modified the D_SAMLAssertionDataPage and D_SamlSsoLoginInfo data pages as readonly, causing them to not be passivated under these conditions. To resolve this, the data pages have been made editable so they will be restored as expected. This change also resolves any difficulty with SAML logoff activities in conjunction with SAP and Pega Cloud.
SR-A2424 · Issue 205812
Latency resolved for sites with repeated SAML authentication requests
Resolved in Pega Version 7.1.9
In an installation using SAML SSO for authentication, repeatedly initiating SAML IDP requests were eventually causing poor system performance. To resolve this, support has been added to disable replay cache handling during SSO login via a DSS.
SR-115653 · Issue 166301
Expanded width of Dates dropdown when using WAI
Resolved in Pega Version Pega Platform, Resolved in Pega Version 7.1.7
When WAI rule-set is enabled, the Dates drop down was not wide enough to display the full dates information. This was a problem with the field width being fixed, and has been changed to use an auto-set width.
SR-A3897 · Issue 209254
Resolved authentication requirements in activity pzSetQueryDefaults for SSO setup
Resolved in Pega Version 7.1.9
Code-Security.InitialProfileSetup does not need authentication to run, but during the SSO login it calls Code-Pega-Requestor.pzSetQueryDefaults which was hard-coded to require authentication. This was an error, and the SetQueryDefaults activity no longer requires authentication.
SR-119858 · Issue 175151
Adjusted code to prevent double-localization when using Google Chrome
Resolved in Pega Version Pega Platform, Resolved in Pega Version 7.1.7
When utilizing a locale that uses commas instead of points to demarcate decimals in numbers, editing any numbers in a skin caused extra zeros to be added to the numbers. When using Google Chrome, if an input type is a number, Google Chrome by default will localize. The control is also localizing the value after reload, so localization is happening twice. In order to resolve this, If the input type is text, only control localization will happen.
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-A692 · Issue 205611
Resolved duplicate portal open when using Microsoft Internet Explorer 11
Resolved in Pega Version 7.1.9
When using Microsoft Internet Explorer 11, trying to access the My Group tab in the links 'Manage Operator Schedules and Profiles' was not displaying the screen correctly on click of any operator or workbasket and an extra portal window was opened. This was a browser-specific dynamic container issue where the lack of an explicit type=button declaration was causing a form submit that triggered a main page refresh. That declaration has been added.
SR-116761 · Issue 169833
FormatNumber use clarified
Resolved in Pega Version 7.1.7
Attempting to use the "pxFormatNumber" function in an activity step generated the error message "com.pega.pegarules.session.internal.mgmt.Executable cannot be cast to com.pega.pegarules.pub.runtime.StreamBuilderToolKit". Formatter RUF were not intended to be called directly from activities, but RUF has been enhanced to work with reduced functionality in case it is called from activity. The documentation has also been updated to reflect preferred usage.