Skip to main content

Published Release Notes

Find release notes for the selected Pega Version and Capability

Browse resolved issues for Platform releases.

This documentation is for non-current versions of Pega Platform. For current release notes, go here.

User Interface

Valid from Pega Version 7.1.3

Issues for cross-browser support for Designer Studio have been addressed. Improvements were made in run-time performance for data pages with grids, and a number of cosmetic changes and fixes were made.

  • Improved loading of Javascript files during saving Harness rules.
  • Login Performance improvements
  • A cursor pointer issue was addressed in Case Manager.
  • In reports, data in columns will now right-align.
  • Improved section validation functionality
  • Harnesses with screen layouts will now save when there is a refresh condition on a panel.
  • Outline View tree has been improved.
  • Improvements to Repeat Grids using Data Pages as a source.
  • Formatted text cells can be put into a grid to display the value of a property retrieved from a Report Definition join.
  • Designer Studio changes to support IE9 and IE10.
  • Improved designer studio layout
  • Designer Studio changes to support quirks mode in IE8 and IE9.
  • Improvements to SmartLabels in Data Pages
  • Tab groups will take parameters for pre-activities in a defer load setup.
  • Sections support nested dynamic layouts.

Cannot copy final section rules in UI Kit ruleset

Valid from Pega Version 7.1.6

You cannot copy section rules in the UI Kit ruleset (UI-Kit-71) that start with pz or px (final rules in the base PRPC rulesets).

Instead, to customize these rules, use the Copy/Merge Ruleset tool, available at Designer Studio >System > Tools > Refactor Rulesets, to copy all rules from the UI Kit into your application ruleset. You can then check the section rules in and out.

Text Input control number type does not validate

Valid from Pega Version 7.1.5

When a Text Input control type is set to "Number" in the Presentation tab:

  • Validation does not trigger and the field is blanked out when a user submits the form.
  • If a value other than a number is entered, the browser sends an empty value, and the value is not validated.
  • In the Clipboard, the field value displays as empty.
  • If the field is required, the validation displays.

This issue occurs when using both the Chrome and Safari web browsers, and is a result of browser behavior for the HTML5 type=“number”. To fix this issue when using these browsers, do not use the "Number" type in Presentation tab of a Text Input control. Instead, the type should be set to "Text".

Unclear error message when saving shared class instance in tenant layer

Valid from Pega Version 7.1.5

If you attempt to save a shared class instance from the tenant layer, Pega 7 displays this message:

This record has x errors. Save Failed: There was a problem saving an instance of class: Error Code: <none> SQL State: <none> Message: <none>

You cannot save a shared instance from the tenant layer if that instance cannot be overridden.

Microsof Internet Explorer 9 (IE9) may display a script error when clicking a Help button

Valid from Pega Version 7.1.6

A script error may be displayed when clicking a Help button when script error notification is turned on in the browser. As a work around, uncheck the Display a notification about every script error option in the Advanced tab of the Options dialog box in Microsoft Internet Explorer 9.

Number and text input controls on Android devices may not display the correct keyboard

Valid from Pega Version 7.1.8

When running a Pega 7 application on a device using the Android operating system, pxNumber and pxTextInput controls may not display when using the desired on-screen keyboard. This happens when the number or text input type is set to number.

At design time, the input type is selected in the Editable Format section of the Presentation tab in the Cell Properties panel for a pxNumber or pxTextInput control. Due to a known limitation in some versions of the Android OS running on some devices, the keyboard displayed at run time may not support entry of decimal values when a Number type keyboard is specified.

To resolve this issue, use the Phone type when numbers with decimal values may be required. Using the Phone type displays a numerical phone keyboard. The Android phone keyboard includes both commas and periods so that decimals may be entered.

Cell Properties dialog

The Phone type selected in the Presentation tab of a Number control

Note that this issue only occurs on Android devices. It is recommended that applications for iOS continue to use type=“Number”.

Tags disappear from Rich Text Editor source mode

Valid from Pega Version 8.5

When you use Rich Text Editor in HTML source mode, some tags disappear from the markup, which causes backward compatibility issues and data loss.

Cause

Pega Platform™ version 8.5.5 introduced the DOM Purifier security plugin. The plugin removes potentially vulnerable tags, including custom tags, from the raw HTML code in the Rich Text Editor source mode.

Workaround

You can disable the DOM Purifier plugin by adding the the window.disableDomPurifier = true markup to the userWorkForm HTML fragment rule.

Alternatively, as of Pega Platform version 8.5.6, you can add a tag to the allow list by including the window.rteCustomAllowedTags = ['myCustomTag'] snippet in the userWorkForm HTML fragment rule. 

In Pega Platform versions 8.5.6 to 8.6, the iframe tag is added to the allow list by default.

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