SR-C82353 · Issue 426014
CorrNew loop logic updated to handle custom notifications
Resolved in Pega Version 8.2.1
When CorrNew was used to configure a email smart shape in a custom notification, having a 'not available' party as the last parameter was leading to the mail not being sent. To resolve this, the 'while' loop logic has been updated to iterate over the workparties for every party role.
SR-C85312 · Issue 424037
Check added for custom section use in Summary report exported to Excel
Resolved in Pega Version 8.2.1
Criteria were missing when Export to PDF was used for Summary reports filtered by a custom section. This was caused by the needed pyQueryTokenList not being repopulated for the export in the case of custom section use, and has been resolved by adding a summary report check in the pzIncludeCustomFilterSection section before invoking pzClearRDTempFilters function.
SR-C90261 · Issue 428122
Hotfix installer updated to adhere to installorder file included in the package
Resolved in Pega Version 8.2.1
In order to ensure hotfixes are always installed in the proper order, the installer has been updated to iterate over a set that is ordered according to the INSTALLORDER.PEGA file included in the DL file at packaging time.
SR-C83050 · Issue 422977
IE width calculation fixed for imported built-on with dymanic layout
Resolved in Pega Version 8.2.1
After upgrade, the Built On input for the application screen in Designer Studio was not rendering in the IE11 browser if dynamic layout was used. This was caused by a browser-specific issue with width calculation for pzDefinition, and code has been added to handle this issue.
SR-C89316 · Issue 426077
Lower major ruleset versions will not be considered during design time validation
Resolved in Pega Version 8.2.1
After circumstancing a rule by property and withdrawing the rule in higher version, the same rule was circumstanced by template. Later after major skimming, attempting to perform a save-as of the circumstanced template rule resulted in an error stating that the circumstanced property already existed. During design time, the system validated the rule with rules from all other ruleset versions. In this corner case where a property-based circumstanced rule was withdrawn and then skimming was performed, the error occurred because it was being saved in a different major ruleset instead of into the same major ruleset. In order to better handle this condition, the system will not consider rules from lower major versions during design time validation.
SR-C75723 · Issue 421826
Rollback filter query updated to handle very large classes mapped to the same history table
Resolved in Pega Version 8.2.1
When rolling back the imported product file using deployment manager, the error "DatabaseException caused by prior exception: org.postgresql.util.PSQLException: ERROR: column "pzinskey" does not exist" was seen. This was traced to the rollback process picking the already processed items from the history table due to an incomplete filter query that occurred when there were more than 1000 classes mapped to same history table. This has been resolved.
SR-C81410 · Issue 422137
Radiobutton aria-label enhanced to retrieve localized field value
Resolved in Pega Version 8.2.1
Localization code has been added to the pzpega_ui_template_radiogroup file to support using RadioButton aria-labels for Field value.
SR-C83468 · Issue 424950
Legacy multipart upload support added for very large hotfix catalogs
Resolved in Pega Version 8.2.1
After a package containing 100+ hotfixes was installed, the fixes were not visible in the Hotfix Manager page even though the database status showed them as "Installed". Investigation showed that performing a system scan on the catalog upload was resulting in thread dumps while decoding the request URL due to the control used for catalog upload posting the entire content in form data rather than sending a multi-part request. To unblock this use case for catalogs with huge data, the system has been updated to perform a legacy upload where a form submit is used with content-type as "multipart/form-data" rather than sending the entire data in the request header.
SR-C76412 · Issue 425189
Content type header removed from default inclusion in JWT token to support MS integration
Resolved in Pega Version 8.2.1
In order to integrate Pega with Office365 to use the Outlook API to Send and Get messages, an access token is required as a part of Authentication process. For obtaining an access token from the Azure directory, the process is to follow the OAuth 2.0 client credentials flow which requires the generation of a JSON Web Token (JWT) with the required Header, Payload and Signature. However, because Pega adds the tag "cty": "application/json" by default, using the out-of-the-box 'Token Profile' rule to generate the JWT and pass the same in a REST call to Microsoft was resulting in a error response indicating that there was an unsupported token header. This has been resolved by removing the content type header in the JWT token.
SR-C79482 · Issue 424536
DSS added to allow custom timeout for BIX query
Resolved in Pega Version 8.2.1
The BIX query to retrieve the blob column was taking up to 60 seconds for large volume, causing timeouts. Previously, the extract defaulted to using repost pzSample which is internal/final and has a default timeout of 30 seconds. In order to avoid timeouts, the new DSS "BIX/selectQueryTimeout" has been added to allow setting a custom value. Further refinements will be made for multi-tenant environments in a future release.