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-117085 · Issue 169328
Corrected property inheritances in the XML assembler
Resolved in Pega Version Pega Platform, Resolved in Pega Version 7.1.7
An error was noted where some attributes for IdentifierType elements were not being created in parse XML for the WSDL consumed. All attributes should passed down from the base type to the derived [restriction] type, but a Parse XML assembler issue combined with a defect in XML Rule Builder caused the Parse/Stream rule nodes to not inherit attribute nodes from the parent type(s). This has been corrected.
SR-117131 · Issue 167711
Corrected Rule cleanup utility
Resolved in Pega Version 7.1.7
The Rule Cleanup utility deletes instances from pr4_rule_ruleset that contain old ruleset versions. Some Rule-RuleSet-Name instances have rulesets and were deleted incorrectly. To correct this, the utility has been modified with an additional 'where' clause to restrict deleting Rule-RuleSet-Name instances.
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-117164 · Issue 169821
Tightened vertical privileges
Resolved in Pega Version 7.1.7
If a User with lower rights accessed the cookie of a Manager, it was possible to update the Operator Details. A privilege check has been added when saving the operator record to resolve this issue.
SR-117173 · Issue 168365
Dynamic system settings for address map control updated
Resolved in Pega Version 7.1.7
Due to an error, the dynamic system settings for address map control had a value pre-set instead of a blank default. This has been corrected.
SR-117204 · Issue 168225
Error message logging improved for DB2
Resolved in Pega Version Pega Platform, Resolved in Pega Version 7.1.7
During normal development activities, a console log was showing a large volume of Integrity Constraint Violation Exceptions that seemed to correlate with the level of activity of users and the number of concurrent active users. The system uses infoForced to make sure "real" errors are reported, but attempts to suppress those deemed to be "noise". In this case, the system was lacking an additional "if" test for DB2, and this has been added.
SR-117205 · Issue 171200
Corrected datetime calendar validation on forms with messages
Resolved in Pega Version 7.1.7
When messages were present on a form (validation, etc.) and the date selector was used, the screen blanked after selecting the date. This was caused by an error in the datetime calendar popover and has been resolved.
SR-117216 · Issue 168600
Validation corrected for Case Manager portal types
Resolved in Pega Version 7.1.7
After migration, changing the application header text for the Case Manager portal was throwing the error "pySkinType: ** You must specify a skin to use or select "Default to Application Skin" upon checkout. To correct this, the validation activity step has been updated with a 'when' expression to skip this validation for mobile portals
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.