INC-186930 · Issue 679707
Mouse cursor remains consistent when expanding repeating grid column
Resolved in Pega Version 8.6.3
After update, expanding the last column of a repeating grid changed the mouse cursor. Refreshing the portal restored the original cursor. This has been resolved by adding the last column to the disableColumn array.
INC-176757 · Issue 657785
Interaction History properly saved when running strategy on a different data flow
Resolved in Pega Version 8.7
Customized Interaction History properties that had been added to pyInteractionHistoryConfiguration and pyDefaultWorkingSet and saved into the PR_DATA_IH_FACT table were not being saved properly after upgrading from 7.3 to 8.3. This was a missed use case and has been resolved.
SR-B12737 · Issue 283588
Resolved harness error after using pagination 'load more'
Resolved in Pega Version 7.3
After using the Pagination 'load more' option and clicking on any of the newly loaded items, a blank harness was opened. This was traced to missing change tracking data for the newly loaded rows, and has been corrected.
SR-B12737 · Issue 282869
Resolved harness error after using pagination 'load more'
Resolved in Pega Version 7.3
After using the Pagination 'load more' option and clicking on any of the newly loaded items, a blank harness was opened. This was traced to missing change tracking data for the newly loaded rows, and has been corrected.
SR-B40177 · Issue 297056
Resolved harness error after using pagination 'load more'
Resolved in Pega Version 7.3
After using the Pagination 'load more' option and clicking on any of the newly loaded items, a blank harness was opened. This was traced to missing change tracking data for the newly loaded rows, and has been corrected.
SR-B43621 · Issue 300812
Back/Previous years calculation fixed to use current year
Resolved in Pega Version 7.3
In the year dropdown for Date control, the number of back/previous years was calculated based on the selected year and not from the current year. The calculation logic has been fixed to resolve this.
SR-B7143 · Issue 281865
Div fixed for Add button using GridAction section include
Resolved in Pega Version 7.3
After upgrade, using the "Add" button configured as a section include with pzGridAction caused UI issues. This was due to pzGridAction (@baseclass) not closing the div tag properly after calling pzGadgetInclude, and has been fixed.
INC-173886 · Issue 664142
SSLContext created using protocol from REST connector rule form
Resolved in Pega Version 8.7
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-174321 · Issue 664239
SSLContext created using protocol from REST connector rule form
Resolved in Pega Version 8.7
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-175058 · Issue 660933
SSLContext created using protocol from REST connector rule form
Resolved in Pega Version 8.7
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.