INC-180858 · Issue 660801
SSLContext created using protocol from REST connector rule form
Resolved in Pega Version 8.5.5
After upgrading to IBM websphere v9.0.5.6 or higher, API calls Like REST, Connect-HTTP etc were failing to connect to endpoints using TLSv1.2. Investigation showed that although the connector was configured to send TLSv1.2, the ClientHello handshake was triggered for TLSv1.3. Because the SSLContext was created with highest version supported by protocol in the WAS container, this has been resolved by modifying the code to create SSLContext based on the the protocol selected in the REST connector rule form. Additionally, please note that the Connect-HTTP connector has been deprecated and the Connect-REST capabilities in the platform should be used instead.
INC-155406 · Issue 638705
Clipboard security updated
Resolved in Pega Version 8.5.5
Security has been enhanced for clipboard properties by restricting registration for readonly properties.
INC-157404 · Issue 630693
Adaptive Model report information exports correctly
Resolved in Pega Version 8.5.5
Clicking export to Excel or PDF in the Prediction Studio Adaptive Model report was not working. Investigation showed the first double quote of the propositionName was getting replaced from & quot ; to "", which resulted in an error while performing openUrlWindow action. This has been resolved by adding a new helper handler, while creating context menu using Handlebars.
INC-163644 · Issue 652966
Error message handling added for nested page lists
Resolved in Pega Version 8.5.5
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-164924 · Issue 639019
Serbia added to country codes list
Resolved in Pega Version 8.5.5
The CountryCode for Serbia (SRB) has been added to the existing country codes.
INC-165964 · Issue 656813
Harness context set for modal dialog on interaction portal
Resolved in Pega Version 8.5.5
An AddDelete refresh condition on a page list property was not triggering a ReloadSection as expected. This was a special use case in the interaction portal where a modal dialog was opened but the harness context was not set properly, and has been resolved by ensuring the harness context is correct.
INC-166858 · Issue 664459
Improved text accessibility for screen zoom
Resolved in Pega Version 8.5.5
Under the specific conditions of a very large zoom level and low screen resolution, the inner menu's height was reduced to 0. This has been resolved by setting a minimal height for the inner menu item element to prevent it shrinking to 0.
INC-169866 · Issue 653547
View content type updated to FIELD
Resolved in Pega Version 8.5.5
After upgrade table grids were not visible in the UI for some operators while other operators with the same access group were able to see the same table with the result rows. Investigation showed that the personalized view stored in 8.1.x did not have a content type set, causing all of the columns to be hidden after upgrade to 8.4+ due to the personal view not matching with the design time view. To resolve this, the content type has been updated to FIELD for views.
INC-171352 · Issue 653690
Focus set correctly on the modal window in theme-Cosmos
Resolved in Pega Version 8.5.5
in theme-Cosmos with touch enabled, clicking on a button to open a modal window set the focus on the background instead of in the modal window, forcing tabbing through the full page to reach the modal window. This was traced to the templates not using the pzModalCancel control which has the necessary container_close for the modal dialog close icon, and has been resolved by adding a check to set the focus correctly.
INC-171663 · Issue 655244
MashUp dynamic parameters article updated
Resolved in Pega Version 8.5.5
The documentation for MashUp best practices has been updated to clarify that dynamic parameters sent from the client side using "pega.web.api.setAuthenticationParameters" API will be sent as part of the query parameters and won't be part of the encrypted hash as this hash is generated on the server end while generating the mashup code in the mashup channel.