SR-C83468 · Issue 424951
Legacy multipart upload support added for very large hotfix catalogs
Resolved in Pega Version 8.1.4
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-C87986 · Issue 428573
Resize handle correctly changed for RTL locale
Resolved in Pega Version 8.1.4
When the locale was set to RTL, dragging sections to the left caused a resize and dragging sections to the right moved them to the left. This has been resolved by ensuring the resizable handle for workarea is correctly changed when the locale is RTL.
SR-C86126 · Issue 423259
CSV import for delete date values will be formatted before row processing
Resolved in Pega Version 8.1.4
In order to support using CSV import for delete purposes, date/time class keys will be formatted before processing the row.
SR-C84643 · Issue 423856
Logs now support RandomAccessFileAppender
Resolved in Pega Version 8.1.4
Support has been added to the LogFileDownload and LogViewer HTML final rules for using RandomAccessFileAppender. This is in addition to the existing support for RollingRandomAccessFileAppender and RollingFileAppender.
SR-C74642 · Issue 424007
Data page reference properties will not be resolved if hidden
Resolved in Pega Version 8.1.4
In order to improve code efficiency, in conditions where a text input field configured with a 'When' visibility condition references a property which is present in a data page, the system will skip the process of resolving the property name if the 'When' rule is evaluated as false.
SR-C81410 · Issue 422138
Radiobutton aria-label enhanced to retrieve localized field value
Resolved in Pega Version 8.1.4
Localization code has been added to the pzpega_ui_template_radiogroup file to support using RadioButton aria-labels for Field value.
SR-C89250 · Issue 429743
Guardrail score ignores test rulesets
Resolved in Pega Version 8.1.4
Test rulesets for a branch were unexpectedly being considered when calculating the Guardrail score. This has been corrected.
SR-C83050 · Issue 422978
IE width calculation fixed for imported built-on with dymanic layout
Resolved in Pega Version 8.1.4
After upgrade, the Built On input for the application screen in Designer Studio was not rendering in the Microsoft Internet Explorer 11 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-C95232 · Issue 432328
Removed extranous tick mark on negative numbers in Excel export
Resolved in Pega Version 8.1.4
All negative amounts had an extra ( ‘ ) in front when report definition results were exported to Excel. This was a byproduct of a security update, and has been resolved.
SR-C76412 · Issue 425190
Content type header removed from default inclusion in JWT token to support MS integration
Resolved in Pega Version 8.1.4
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.