INC-174020 · Issue 650890
Performance improved for Directed Web Access (DWA)
Resolved in Pega Version 8.4.5
Slowness when using a Directed Web Access (DWA) link has been resolved by refining the code of the PZPEGA_UI_DOC_EVENTSCONDITIONSCHAINING script to improve performance.
INC-175990 · Issue 652087
Browser check added to ensure on-click event trigger
Resolved in Pega Version 8.4.5
Clicking Submit from the screen after opening the case from the worklist did not trigger the click event action when using Microsoft Internet Explorer 11. This was due to a change in that browser, and has been resolved by adding a check.
INC-176734 · Issue 655179
Invalid manual time value stops progress and displays error
Resolved in Pega Version 8.4.5
When an invalid time was manually entered, eg. 11, the system previously remained in an error state until the time was corrected. Post-update, the current time of the user's session / browser was populated into the time field when an invalid time was entered. Although the error still displayed, the current time was saved and the user could continue. This has been resolved by adding a condition to show the entered time value and not continue if the entered time value is invalid.
INC-176971 · Issue 655218
Web Mashup works from nested iframe
Resolved in Pega Version 8.4.5
Web Mashup was failing with the error "Browser cookies must be enabled for PRPC Internet Application Composer to function" when it was configured within a nested iframe setup. This has been resolved by adding a cookie check and the appropriate handling for this usecase.
INC-177206 · Issue 655631
Date Time control accepts custom length
Resolved in Pega Version 8.4.5
The date time control was ignoring custom length and expanding the field to the layout width. This was an inadvertent side effect of work done around the visibility of the date picker icon for non-templated layouts, and has been resolved by ensuring the date picker will render with a custom width configured in design time.
SR-C61477 · Issue 418266
HTML conversion added to email IVA
Resolved in Pega Version 8.1.4
When sending through emails that are in HTML format, HTML tags were visible within the Analysis of the email under Entities. These tags also potentially had an impact on topic detection, as the same email sent through in HTML would be classified under a different topic from one sent through as Plain Text.This issue originated because Email IVA received text as HTML while it expected plain text without HTML tags, and was traced to the use of an IMAP setting which sends only HTML to the listener. This has now been fixed such that If any HTML is received by email IVA, it will be converted to plain text via JSoup APIs in the service method as the first step.
SR-C64192 · Issue 415847
Activity Run allows autocomplete control for data transform
Resolved in Pega Version 8.1.4
An enhancement has been added to allow changing the control from Dropdown to Autocomplete when an activity is Run and the "apply data transform" checkbox is checked.
SR-C65841 · Issue 425807
Added handling for cases where IE causes a SAXParseException
Resolved in Pega Version 8.1.4
Numerous SAXParseException messages were seen in the log file, and the queryString showed the pyDeleteDocumentPg being referenced. This was traced to the method used by Internet Explorer to construct an HTTP request: IE sends the header and body of the request in separate TCP packets, but for an unknown reason in this case the body packet goes missing. To resolve this, a toggle has been introduced which will send the pyDeleteDocumentPg request as GET if pega.u.d.GET_REQUEST_DELETEDOCUMENT is set to true in userworkform. In a normal flow without this variable, the request will pass through the normal flow.
SR-C69729 · Issue 415717
External Entity Injection security improved
Resolved in Pega Version 8.1.4
Several updates have been made to improve security against External Entity Injection.
SR-C74054 · Issue 422026
Handling added for summary columns in Export to Excel
Resolved in Pega Version 8.1.4
When a field has an aggregate function in Report Definition, the column alias changes and is not the same as the property name. The consequence is a mismatch between the result set column name and the property name from the property list created beforehand. This results in blank fields when using the "pxDownloadDataRecordsAsCSV" activity for Export to Excel. In order to support the export of summarized columns in Report Definition, an enhancement has been added that uses the column label as an alias for aggregate fields in the native SQL builder of the exportData API to form a map between the property name and the alias name and use it while iterating over the result set.