SR-C68750 · Issue 402364
PEGA0066 alert sends data needed for MyAlerts use
Resolved in Pega Version 8.2
In order to facilitate the use of products like the MyAlerts application, the following data will be provided to PDC from PEGA0066 alerts to generate proper diagnostics information and propose solutions for issues with mobile client connections:pxClientErrorCode pxDeviceManufacturer pxDeviceModel pxOSName pxOSVersion pxHybridClientVersion pxInstallationId pxSynchronizationId pxSynchronizationTimestamp pxEnd The whitelisted parameters can be seen on the Alert Summary page in PDC.
SR-C68682 · Issue 409608
Layout Groups Accordion Styles modified to use refresh on change
Resolved in Pega Version 8.2
After updating Layout Groups Accordion styles in a skin rule and saving and checking in the rule, re-opening the skin rule showed that the changes had not been saved. Investigation revealed that in accordion format, the font section is being rendered for the "header" and "tabs" of the of layout group but the third tab was not visible to accordion format. To resolve this, pyComponentDetails of Embed-skin-component-layoutGroup has been modified to use on onchange refresh section instead of "Run visibility condition on client".
SR-C53820 · Issue 401241
DateTime control updated to handle invalid date entry when validation is turned off
Resolved in Pega Version 8.2
After turning off client side validation, trying to update a date in a date time control using the wrong format resulted in that day's date being used. If the client side validation is turned on, entering the date in the wrong format results in a validation message. This was caused by a missed use case for an invalid date entry not being validated, and has been corrected.
SR-C57025 · Issue 395184
Filter value Autocomplete uses localized text for the 'Case Type' string
Resolved in Pega Version 8.2
The Filter value autocomplete field of the Case Manager portal bulk action landing page was not working as expected while using the Japanese locale setting. If the locale setting was English or empty, the filter value was displayed correctly in the autocomplete. This was an issue with comparisons being hard-coded to use the literal text string 'Case Type', which was failing in localization. To fix this, a 'when' rule has been added to compare localized text against pyFilterName and use it in the appropriate rules.
SR-C53680 · Issue 395439
Filter value Autocomplete uses localized text for the 'Case Type' string
Resolved in Pega Version 8.2
The Filter value autocomplete field of the Case Manager portal bulk action landing page was not working as expected while using the Japanese locale setting. If the locale setting was English or empty, the filter value was displayed correctly in the autocomplete. This was an issue with comparisons being hard-coded to use the literal text string 'Case Type', which was failing in localization. To fix this, a 'when' rule has been added to compare localized text against pyFilterName and use it in the appropriate rules.
SR-C54436 · Issue 394199
Resolved Data Type not showing records if Access When rule is mentioned in ARO of the class
Resolved in Pega Version 8.2
Selecting the Records tab in Data Type rule resulted in an error when an "Access when" was defined in an ARO for the same class. This was traced to an issue in the Records tab where the system checks if the user has access to read/write the data records and shows/hides the "Import" link accordingly. The access permissions are checked with the pzHaveAccess API, which internally expects to be executed on a step page which is of type Data-. Here, the conditions were directly used to show the import link on the section "pzRecordsEditorWrapper" of type "PegaAccel-Task-DataTableEditor". The "WHEN" conditions in ARO are defined on Data- class but they are being executed on "PegaAccel-Task-DataTableEditor" during runtime: this works fine when an integer value is provided in ARO instead of Access when rules. To fix the issue, the pzHaveAccess check on the "Import" link has been removed so that it appears irrespective of the user privileges.
INC-148154 · Issue 602921
Hot Fix Manager updated to use installation order for schema import
Resolved in Pega Version 8.3.5
Schema changes were not being imported during the hot fix manager DL import process. Investigation showed this was due to hotfixes in the DL being iterated over from newest to oldest, causing older hotfixes to replace the value added to a map by the newer. To resolve this, the system has been updated to use hotfix install order, which considers selected and dependent hotfixes, rather than ordering newest to oldest. This ensures that newer table representations will override older rather than the other way around.
SR-C79306 · Issue 417259
Visibility consition added for checkbox used to skip validation for rules import
Resolved in Pega Version 8.2
An enhancement has been added to show or hide the the validation checkbox in Import Wizard by way of the new property 'pyDisableSkipValidate'. This adds a visibility condition for the checkbox used to skip running rule validation in pzImportRecords.
SR-C75930 · Issue 416830
Security Event log enhanced to use 24-hour format for timestamps
Resolved in Pega Version 8.2
Previously, the Security Event log used timestamps in the 12-hour format. An enhancement has now been added to use the 24-hour format to clarify the timing of events.
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.