SR-131228 · Issue 202735
Local template use corrected for 'add item' in repeating grid
Resolved in Pega Version 7.1.9
In repeat grid with options "Expandable rows" and "Override default template", adding a row by action "Add item" resulted in the local template being replaced by the standard "pyGridRowDetails" template. In other cases (e.g. when use action "Edit item") user's custom template was used. To resolve this, templateName generation has been added for expanded pane configuration to check for local templates first before defaulting to the ones provided.
SR-A2141 · Issue 205867
Refined refresh focus logic for radio buttons using on OnChange
Resolved in Pega Version 7.1.9
In a list of Radio Buttons, using the Down Key caused focus to move to the corresponding Radio Button for a split second but immediately shift back to the first Radio Button. This was caused by the OnChange of the radio button having a refresh-this-section, so ReloadSection was being called and the focus was shifted to the first radio button irrespective of the option which was selected. This was confusing behavior, so the system has been modified such that after refresh, focus() element will be called to set focus on the element which caused the refresh.
SR-A2141 · Issue 205271
Refined refresh focus logic for radio buttons using on OnChange
Resolved in Pega Version 7.1.9
In a list of Radio Buttons, using the Down Key caused focus to move to the corresponding Radio Button for a split second but immediately shift back to the first Radio Button. This was caused by the OnChange of the radio button having a refresh-this-section, so ReloadSection was being called and the focus was shifted to the first radio button irrespective of the option which was selected. This was confusing behavior, so the system has been modified such that after refresh, focus() element will be called to set focus on the element which caused the refresh.
SR-132896 · Issue 202844
Added handling for customized flows using "different work item" subprocess
Resolved in Pega Version 7.1.9
After upgrade, customized flows using the "different work item" choice on the subprocess for calling work flow from embedded data page work objects generated the error "'On Another Work Item' was specified yet the same object was supplied." This was traced to a missing pzInsKey for this use case, and the LaunchFlow RUF has been updated to handle this customization.
INC-174321 · Issue 664237
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-175058 · Issue 660935
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-175706 · Issue 659529
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-179188 · Issue 661955
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-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.
SR-131726 · Issue 202769
Fail-over updated to cover server crash scenarios
Resolved in Pega Version 7.1.9
In a testing event, the user session did not properly fail over to another server if the original server was shut down; an error was thrown instead. This was found to be an authentication issue where on node crash, a new requestor was created on the second node and then immediately authenticated as it is SSO. As part of authentication, the mRequiresSpecialProcessingForNodeCrash flag was cleared, meaning the node crash activity was not executed and entire portal was not refreshed. This has been corrected by updating the system to execute crash node activity for SSO cases.