INC-133583 · Issue 584923
Rest connector supports extended chars in attachments
Resolved in Pega Version 8.3.5
When the pyRequestAttachmentPage clipboard page was populated with a file name that contained Latin supplemental 1 unicode characters (decimal values 160 to 255 - for example an umlaut), any extended characters were being converted to question marks (?) before the call was sent, causing the web service call initiated by Pega to fail. To better support this use, an enhancement has been added to support a multipart request with extended characters in the file name. This allows the pyRequestAttachmentPage to specify pyFileNameExtendedChars, allowing RFC 6532 mode to be toggled for multipart requests with attachments. This mode allows for UTF-8 encoding in the attachment file name header, rather than the default ASCII encoding.
INC-143461 · Issue 601841
Updated JSON DT nested page property handling
Resolved in Pega Version 8.3.5
In a JSON data transform, when using an "Update page" step on a single-page property, as a child step of an "Append and map to" step where a pagelist property is given, the pagelist was populated with only one result but the single-page property was treated like a pagelist and received multiple results. This has been resolved by updating the ClipboardJSONDeserializer implementation and downstream abstractions to support "clipboard only" relations as properties in nested PageLists.
INC-139297 · Issue 601421
JSON content type update
Resolved in Pega Version 8.3.5
An update has been made to ensure the content_type is set to application/json for JSON response.
SR-A23916 · Issue 253818
BIX extract WO handling corrected
Resolved in Pega Version 7.2.2
After upgrade, a BIX report was not working correctly due to the difference in work object handling. During BIX extract, the currently extracted WO was being maintained on a tempPage that was not subsequently being used for the lookup. This has been fixed.
SR-A76413 · Issue 254770
Custom datatypes import support added to SQL RD
Resolved in Pega Version 7.2.2
After upgrade, external classes of type 'text' mapped to an external DB were throwing an error while executing report definition. This was due to the method used to get the column type, and the logic has been updated to correct this.
SR-A52484 · Issue 251721
BIX Extract retains pre-upgrade filenames and columns
Resolved in Pega Version 7.2.2
After upgrade, extract rules were created with underscores replacing dashes in the original filenames and ExtractIndentifier and ExtractDateTime columns were added to the output csv file. This was an inadvertent change related to enhancements made to filename conventions, and has been corrected with the prconfig "bix/retainOriginalFileNameForCSV" to retain the filename as provided in the extract rule and the prconfig "bix/ignoreAdditionalColumnsInCSV" to not add the new additional columns pxExtractIdentifier and pxExtractDateTime when upgrading rulesets.
SR-A24412 · Issue 249993
Calendar icon display fixed for Microsoft Internet Explorer11
Resolved in Pega Version 7.2.2
Calendar icons were not displayed in a data table in Microsoft Internet Explorer 11 due to the browser not supporting the icon rendering. A meta tag has been added in the ReviewHarness to correct this.
SR-A23686 · Issue 249793
Support extended for NUMERIC types in RD SQL joins/filters
Resolved in Pega Version 7.2.2
Support has been extended for NUMERIC types in Report Definitions, more specifically to support references to NUMERIC properties in join and filter conditions in RDs using SQL Server 2012, by updating the IDENTITY column type handling in the RUF pzCheckCompatibilityOfColumnTypes function.
SR-A75946 · Issue 252101
pxCommitDateTime BIX extraction more robust
Resolved in Pega Version 7.2.2
The exported XML file was not including the pxCommitDateTime column even when that column was included in the BIX extraction. This was traced to the site trying to perform the commit on the same work object more than once: performing the commit the second time caused the previous value to be overridden by the new commitdatetime. That led to the pxCommitDateTime not being stored in the BLOB, and since BIX extracts the data from source table's BLOB, it cannot extract the value of pxCommitDateTime. To resolve this, the source query that BIX uses has been modified to get both pzPVStream and pxCommitDateTime (if the column is present in the source table) and use the value of pxCommitDateTime from the resultset while writing to the output file.
SR-A75998 · Issue 253191
Improved SOAP envelope cache for WSA/WSSE use
Resolved in Pega Version 7.2.2
After configuring and successfully using Connect-SOAP to a non-secure Endpoint, enabling WSA and WSSE for the connect-SOAP configuration and then disabling it again generated the error "Caused by: com.pega.apache.axis2.AxisFault: A required header representing a Message Addressing Property is not present". This was due to the way the SOAP envelope was being cached and the code has been updated to correctly reflect the desired header processing.