SR-A2879 · Issue 208596
Zero-size attachments now included in correspondence
Resolved in Pega Version 7.1.9
When using the Send Correspondence functionality, an attachment of zero size would be ignored and not included because it did not have any pyAttachStream property. Because there may be a business need to preserve the attachment name and include it anyway, the system has been updated to include and transmit a zero length attachment.
SR-A3054 · Issue 207377
Resolved corruption of Service-SOAP attachments
Resolved in Pega Version 7.1.9
A problem in reading the byte streams was causing Service-SOAP to corrupt the attached PDF/docx files that are part of SOAP request attachments with added null characters. Removing these characters manually resolved the problem as a workaround, but the byte reading logic in MultipartSOAPHandler.java has been updated to fix this issue.
SR-A3295 · Issue 207109
Resolved ClassCastException for JMS listener
Resolved in Pega Version 7.1.9
If a Service JMS rule (Point to Point) was invoked by a JMS listener, the listener would pick up a message created using Tibco queue, pass it to the Service JMS rule, the message would be parsed and the response xml created, but then the system was not able to create a session to respond to the JMS producer. This was traced to the Queue and Topic specific API used by JMSListener causing ClassCastExceptions. To resolve this, the system now uses a generic API devoid of Queue and TopicSessions to send the response message in JMSListener.
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.