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-A1273 · Issue 204576
PRPCTask is now tenantized
Resolved in Pega Version 7.1.9
On a multi-tenant environment with HTTP event, it was not possible to see the options for warm\blind transfer with interaction from a tenant layer. This was an issue with the task taking the user ID information but not taking the tenant information, so the acceptance of the interaction on the portal was not getting delivered to the desktop. To correct this, PRPCTask is now tenantized.
SR-A1390 · Issue 204953
Added qualification to avoid RequestorInitialize conflicts
Resolved in Pega Version 7.1.9
In the out-of-the-box activity RequestorInitialize, RUF CompareDates was invoked by using a short hand notation which was causing conflicts. This has been solved by qualifying the function with @Ruleset:Library.
SR-A1588 · Issue 211728
Content file path handling updated for Linux
Resolved in Pega Version 7.1.9
In Linux systems, a problem was seen with deleting or updating static content due to a difference in the designated directory name: the directory name is case sensitive, but the code to delete the image forced lower case. This has been resolved by leaving the file path as-is for these systems rather than forcing it to lower case.
SR-A1648 · Issue 206014
Resolved file permissions for Java2 security on WAS8.5
Resolved in Pega Version 7.1.9
After enabling Java 2 security on WAS8.5, access denied file permission exceptions were being generated when deploying and starting ML7. This has been resolved by adding permissions for the temp files in both the WAS and rules policy files, and by adding a doPrivileged block code to borrow a compiler.