SR-A33 · Issue 206096
Addressed XML attachment corruption
Resolved in Pega Version 7.1.9
A document file response generated by Connect-REST and attached to the work object was becoming corrupted if it was content type XML. This was an issue with the code converting the doc data to string, and invokerestconnector has been updated to handle this use case.
SR-A3869 · Issue 209484
Corrected REST logic for missing/blank query parameters
Resolved in Pega Version 7.1.9
When running a REST connector with a resource path that contained multiple parameterized areas of the query string where the value of the first and/or last query string parameters were blank or missing, the request URL was missing the query string parts that have an equals sign delimiter but a blank/empty value. This was unexpected behavior traced to a change in the generation logic, and the system has been modified to produce the expected behavior of query parameters with blank values appearing as "val1=" instead of not appearing or missing the equals sign.
SR-A3869 · Issue 210205
Corrected REST logic for missing/blank query parameters
Resolved in Pega Version 7.1.9
When running a REST connector with a resource path that contained multiple parameterized areas of the query string where the value of the first and/or last query string parameters were blank or missing, the request URL was missing the query string parts that have an equals sign delimiter but a blank/empty value. This was unexpected behavior traced to a change in the generation logic, and the system has been modified to produce the expected behavior of query parameters with blank values appearing as "val1=" instead of not appearing or missing the equals sign.
SR-A3992 · Issue 211563
WSDL generation updated
Resolved in Pega Version 7.1.9
A coding error for the constants used in generating WSDL was creating a problem for some installations with the resulting data. This has been corrected.
SR-A4918 · Issue 211744
Reverted WSDL naming convention to previous style
Resolved in Pega Version 7.1.9
In earlier versions of the system, the exposed Pega-generated WSDL had ComplexType named "CreateCaseWSRequestType" with uppercase "T". A recent change to naming the ComplexType "CreateCaseWSRequesttype" with lowercase "t" required a manual override to use previously generated WSDLs after upgrading, so the naming has been reverted to using the uppercase "T" format.
SR-A5413 · Issue 212956
Null check added to ParseXMLSAXRuleWrapper
Resolved in Pega Version 7.1.9
Thread lock error messages were being generated in the clipboard when trying to access a property pyNote whose value has been initialized with XML content. This was traced to ParseXMLSAXRuleWrapper adding a null value to the Clipboard Value list, and a null check has been added to prevent this.
SR-A959 · Issue 205668
Enhanced locking for EmailListener to detect and process auto-reply
Resolved in Pega Version 7.1.9
Due to thread locking timing, the EmailListener was not detecting 'autoreply' emails, causing infinite loops. This has been fixed by adding code to look for DSS Email/AutoReplySubject. If present, it will lock the requestor before getting the custom AutoReply setting and processing as expected.
SR-A100118 · Issue 287256
Auto-populate updated for better page copy references
Resolved in Pega Version 7.3
After upgrade, an error was generated at a page-remove step on the Group information screen while running the quoting process. This happened in cases where a copy was made of a page containing an auto populate property and the data page referred by the AP had Common Parent references, and was traced to the parent page of the reference property having been removed from the common parent page. To resolve this, the auto-populate function has been updated to better maintain references in copies.
SR-A100558 · Issue 271513
Oversized file null-pointer exception resolved
Resolved in Pega Version 7.3
A 413 exception was being generated by uploading files with a size greater than the Initialization/MaxFileUploadSize DSS value. The controls have been modified with a check to restrict properly restrict file size during this process.
SR-A100558 · Issue 274795
Oversized file null-pointer exception resolved
Resolved in Pega Version 7.3
A 413 exception was being generated by uploading files with a size greater than the Initialization/MaxFileUploadSize DSS value. The controls have been modified with a check to restrict properly restrict file size during this process.