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-117158 · Issue 169361
Corrected inclusion of "Other Specifications" in Document Wizard
Resolved in Pega Version 7.1.7
The 'Other Specifications' section of the application doc was being included regardless of whether the checkbox was selected in step 4 of the Document Wizard. This has been corrected to ensure 'Other Specifications' are documented only when they are selected.
SR-117391 · Issue 170006
Export to Excel replaces embedded control characters in APW
Resolved in Pega Version 7.1.7
In Application Profile Wizard, attempting to Export to Excel would fail if any specifications text contained an embedded control character (such as might appear after cutting and pasting from a Word or text file). To prevent the exporting failure, any control characters introduced into the generated data are now replaced with spaces during the export process.
SR-117461 · Issue 169210
Delete All Links' button disabled if rule is read-only
Resolved in Pega Version 7.1.7
When an Application Requirement rule is read-only due to being in a locked ruleset etc., the Delete All Links button was offered as an option. In order to avoid confusion, the Delete All Links button is now readonly when the rule is not editable.
SR-117604 · Issue 169493
Increased limit for Application Document flows
Resolved in Pega Version 7.1.7
Application Document previously limited the number of flows to 50 and would not list those exceeding the limit. This limit has been removed.
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-117840 · Issue 170516
Autopopulate correctly set/disabled in the CSR portal
Resolved in Pega Version 7.1.7
Switching to some clipboard pages caused a null pointer error in the CSR portal for the operator. This was caused by an autopopulate call being made even when autopopulate was disabled. This has been corrected.
SR-117921 · Issue 174204
Warning message displays for ruleset save in lower version
Resolved in Pega Version 7.1.7
If a developer tried to save a rule in lower ruleset version while the same rule is already in a higher ruleset version, this was allowed with no warning. This behavior has been corrected.
SR-117961 · Issue 174233
Datetime conversion smoothed for SQL queries
Resolved in Pega Version 7.1.7
If the date time format on an SQL Server 2008 instance is set to ydm, a datetime conversion error was created due to the PRPC query using ymd format. In order to support all date formats for SQLServer, Timestamp is now formatted as "yyyyMMdd HH:mm:ss:SSS".
SR-118029 · Issue 173069
BIX filtering corrected
Resolved in Pega Version 7.1.7
Bix filters were not working consistently due to a missing call in the logic handling the ruleset references, and are now working correctly.