Skip to main content

Resolved Issues

View the resolved issues for a specific Platform release.

Go to download resolved issues by patch release.

Browse release notes for a selected Pega Version.

NOTE: Enter just the Case ID number (SR or INC) in order to find the associated Support Request.

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-C80129 · Issue 425385

Enhancement added to hide class join warning from end user

Resolved in Pega Version 8.1.4

An enhancement has been added to hide the joined class warning message at the end user portal if the section pzManageRecords is delegated to the user. This is done by by checking pxLimitedAccess on the pxThread clipboard page.

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.

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-C74648 · Issue 422906

Autocomplete arrow placement corrected in Right to left local mode

Resolved in Pega Version 8.1.4

When using the Autocomplete control, the blue arrow was seen to have an incorrect placement/orientation in RTL mode. This was traced to the autocomplete background-image in RTL mode being the same as that for LTR, and has been resolved by adding specific background-image for RTL.

SR-C74650 · Issue 422909

Grid alignment and headers corrected for Opportunities screen in RTL locale

Resolved in Pega Version 8.1.4

When using the RTL locale, the Opportunity detail screen and search screen had grid alignment and header issues. This has been resolved by updating the py-portal-stages css attached to the enduser skin.

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us