SR-116445 · Issue 169717
SOAP settings updated to work with IBM JBK 1.7
Resolved in Pega Version 7.1.7
When calling Service SOAP hosted on WebSphere 8.5+ and JDK 1.7, the SOAP client was failing with a java.lang.VerifyError. This was traced to a change in the settings necessary for use with IBM JBK 1.7, and the needed properties have been updated.
SR-116508 · Issue 170253
Large flow handling improved for IE8
Resolved in Pega Version 7.1.7
When opening a large flow in IE8 which includes multiple sub flows, a long-running script warning is displayed. This is caused by too many calls being executed at once on IE8, and has been remedied by turning on the asyncProcessing parameter for IE8.
SR-116719 · Issue 167427
Added handling for SOAP elements with empty case types
Resolved in Pega Version 7.1.7
If customers created a SOAP element with an attribute like Text, the generated WSDL from services wizard did not have a type for the element "CaseStatus" and failed validation with the error "Element 'CaseStatus' with empty content type cannot have text or element content." The XML has been updated to correctly handle this use case.
SR-116818 · Issue 167121
Corrected swim lane routing with shapes
Resolved in Pega Version 7.1.7
While using swim lanes, adding shapes into the flow caused unexpected and random behavior of the process modeler including failure to return control to the user after saving. This error was related to routing handling when swim lanes are present, and has been corrected.
SR-116989 · Issue 170784
XSS alert resolved for integer type property in Edit Data Table
Resolved in Pega Version 7.1.7
The presence of an integer type property in Edit Data Table was generating an XSS alert. This was caused by changes in the html- getMessagesAll that rendered the property value directly, and has been updated to an XSS-safe API.
SR-117020 · Issue 167867
Cookies only generated if IAC enabled
Resolved in Pega Version 7.1.7
IAC cookies were being generated in environments where IAC was not deployed, causing the application be flagged in a security audit due to missing Secure attributes. To correct this, the system has been updated to bypass cookie generation if IAC is not in use.
SR-117047 · Issue 173480
Thai characters now working in eform generated PDFs
Resolved in Pega Version 7.1.7
PDFs generated using out-of-the-box Map-eForm rules worked when data was entered in English, but data entered using the Thai keyboard was not reflected in the generated PDF. The root cause of this problem was a third-party product integrated with PRPC. iText is used to convert eForm data into PDF, but it was not honoring the appearances set to the acrofield. To remedy this, the included version of iText has been updated to version 2.1.7, and the NeedAppearance setting for the AcroFields now 'true' by default.
SR-117228 · Issue 168249
Resolved issues with Flow shapes distributed across Swim Lanes
Resolved in Pega Version 7.1.7
Pool size is maintained as both pixels and inches, but auto conversion was failing if the pool dimension was very large. This created an error where saving a flow rule could cause the pool to drastically shrink (for example, 20 inches becoming 20 pixels). In order to maintain the proper dimensions, a check has been added for pool and swimlane to ensure the proper inch/pixel conversions.
SR-117815 · Issue 170081
Updated UUID generation to function with Ping Identity
Resolved in Pega Version 7.1.7
Issues were experienced in trying to achieve connectivity using SAML 2.0 for an SSO solution. Ping Identity imposes a constraint on the format of the Request ID that it receives, and fails if that ID does not start with a letter or underscore. This ID is a random UUID generated by java code, and it had no set leading character. In order to allow full interoperability, the UUID generation has been replaced with a custom implementation which generates unique IDs starting with "_".
SR-118305 · Issue 171562
Report definition reference columns expanded to include data type smallint
Resolved in Pega Version 7.1.7
Report definitions with reference columns of data type SmallInt in their database were not able to run as expected after migration due to missing support for that data type. This support has been added.