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-A16621 · Issue 233386
Changed image tag to prevent auto-submit of calendar when parameters exceeded
Resolved in Pega Version 7.2.1
When user wanted to select the future date, he navigates by clicking the Year navigation link (arrow link). During this process of selecting a future date in the Year Navigation link, moving beyond the configured Number of years caused the page to be automatically submitted. This was caused by the input tag used for image causing a form submit, and tag has been changed to an anchor to fix this.
SR-A16638 · Issue 233607
Changed edit control to prevent Google Chrome adding zeroes when localizing
Resolved in Pega Version 7.2.1
When using Google Chrome in some locales, zeros were being added to values in the skin and corrupting entered values. This was due to Google Chrome defaulting to localizing input type numbers, which caused dual localization after the control had already localized the value after reload. When input type is text, only the control localization will happen, so a workaround for Google Chrome has been added where the type of control has bene changed to text in the editable mode for the pyItemAlignment section.
SR-D32525 · Issue 505467
Dirty check added to offer save/discard changes when closing tab
Resolved in Pega Version 8.2.4
With the OOTB section enabled, performing a change in the form (changing a text value, selecting a option in a dropdown, etc.) and closing the case generated an unexpected alert indicating that the case was changed and the modifications were lost. This differs from the previous behavior of showing the section pyDirtyCheckConfirm which offered the opportunity to save the work. This was a missed use case and has been resolved by updating the system to perform a check for the dirty state when closing the interaction and show a modal dialog asking the user to choose either save/discard if dirty.
SR-A22152 · Issue 247716
Report Def Filter using .pxObjClass returns all results
Resolved in Pega Version 7.2.1
Using .pxObjClass as a filter in Report Definitions resulted in different and/or incomplete Class arrays being built depending on how the Value field was populated. This was traced to an incorrect "if" check in objClassOptimizer causing class names to be missed, and has been fixed.
SR-D20423 · Issue 503444
Improved upgrade handling for tables using classes with property references
Resolved in Pega Version 8.2.4
After upgrade, some page property values were blank and exposed database columns did not contain the values. Investigation showed that the reference properties did not have context and hence column population was not able to determine their value. To resolve this, instead of doing column population for all the columns, the system will identify classes that have property references and that are being optimized as part of upgrade process and maintain a list of specific columns to update.
SR-A22672 · Issue 243213
Use Pega Log Analyzer in place of Alerts.xls Excel Template
Resolved in Pega Version 7.2.1
A documentation error incorrectly referred to the Alerts.xls Excel template as being available on the PDN. That file is no longer available, and the Pega Log Analyzer should be used instead: https://pdn.pega.com/community/pega-exchange/pegarules-log-analyzer
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.