Skip to main content

Resolved Issues

View the resolved issues for a specific Platform release.

Go to download resolved issues by patch release.

Browse release notes for a selected Pega Version.

NOTE: Enter just the Case ID number (SR or INC) in order to find the associated Support Request.

Please update your bookmarks. This site will be discontinued in Dec 2024.

Pega Platform Resolved Issues for 8.1 and newer are now available on the Support Center.

SR-116950 · Issue 168328

Rule name validation checks relaxed for draft mode

Resolved in Pega Version 7.1.7

In order to facilitate flow design, Decision shape properties will no longer require rule name validation when using Draft Mode.

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-117039 · Issue 169671

Standardized class display options for App Explorer

Resolved in Pega Version 7.1.7

Inconsistencies had appeared in how Application Explorer handled switching the display between name and label (short description) in the class hierarchy display. The App Explorer menu now shows the option to toggle between Class labels and Rule names, with a default setting of displaying Rule names. In addition, the short description display will not include the rule purpose.

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.

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us