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.

Please note: beginning with the Pega Platform 8.7.4 Patch, the Resolved Issues have moved to the Support Center.

INC-239902 · Issue 628577

Handling added for multi-file upload of duplicated files

Resolved in Pega Version 8.7

Attaching the same file multiple times during a single upload caused some of the duplicated files to not be included. The issue was not seen when attaching the same file multiple times but in different attempts. The exception "Can't continue with file attachment. FileData.xlsx is missing and might have been quarantined by anti-malware software" was logged. This was caused by the files being uploaded without updating filenames to have a unique ID, so multiple files with the same name were overwriting the previous file. This has been resolved by setting the appendUniqueIdToFileName parameter to true in the upload request so each copy of the filename is treated as an individual file.

SR-A76262 · Issue 256275

Logic updated for parse SOAP to better handle similar element names

Resolved in Pega Version 7.2.2

When the path to an XML node included at least one repeating element and some other element in the path had a name which ended with the name of the repeating node, the data placed in properties by Rule-Parse-XML was potentially inaccurate. The end result is that the data that is recorded in Pega as coming from the N-th occurrence in a repeating element set might contain some data that actually comes from the 0-th occurrence or some other occurrence that is not N. To make the results accurate and consistent, the system has been updated to remove all simple text searches so the replacement of generic node names with indexed node names happens to the correct nodes, regardless of similarities between names in the path.

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