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.

Organization Setup superseded by New Application Wizard

Valid from Pega Version 7.1.3

The Organization Setup Wizard has been retired in PRPC 7.1.3.  This feature was previously launched from the Designer Studio > Org & Security > Organization > Organization Setup menu. Users are encouraged to run the New Application Wizard (also known as Application Express) instead:

NewAppWizard.jpg

This tool quickly generates an application along with all of the artifacts previously offered by the Organization Setup Wizard. This includes, but is not limited to, the class hierarchy, application rule, organization/division/unit rules, and all relevant data instances.

See the following PDN article for more details on the New Application Wizard:

Create new applications quickly and easily with Application Express

DCO

Valid from Pega Version 7.1.3

In this release, specification support in Case Designer was improved.  Also, improvements and fixes were made to the New Application Wizard.

  • Changes were made to support a split schema environment
  • Shared and Component RuleSets can be copied.
  • Can edit in Word from either Grids or Lists.
  • More than 50 case types are now supported for an application.

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.

Updated Word merge support with Microsoft Silverlight plug-in

Valid from Pega Version 7.1.3

Starting in this release, Pega 7 features that integrate with the Word merge capability are now cross-browser. ActiveX controls (which are only compatible with Internet Explorer) have been replaced with Microsoft Silverlight. This plug-in must be downloaded separately from Microsoft because it is not shipped with Pega 7.

Common features that are affected by this change include the Specification form and Case Type landing page.

Prior to using these features, see the release note Word merge support with Microsoft Silverlight plug-in for more information about setting up their client systems.

Changes to the Attach Content control in Pega Client for Windows

Valid from Pega Version 8.2

Users who access offline-enabled Pega Platform™ applications from Pega Client for Windows can now use the Attach Content control within a case view to attach files with a native file picker control or take screenshots with a device camera. Images are immediately attached to the case, and image file names are based on a time stamp. If a device has no camera, the client skips the source selection step and the native file picker control opens.

For more information, see Harness and Sections forms – Adding an Attach Content control.

Manage test ID access with an access group role

Valid from Pega Version 8.2

Test IDs for user interface components are available only to users who have the PegaRULES:TestID role added to their access group. This requirement allows administrators to limit access to test IDs to users who create or run tests. At run time, applications do not include the test ID data for users without the PegaRULES:TestID role, which reduces the amount of code that is downloaded to the client.

For more information see Managing Test ID access with an access group role

Text file rules support the Google Closure Compiler

Valid from Pega Version 8.2

Text file rules support Google Closure Compiler as the default option for minification of JavaScript code. Minification reduces the size of JavaScript in text file rules for faster download. Access the Closure Compiler by selecting it in the Minification menu in a text file rule. For more information, see Text File rules - Completing the Main tab.

Date range option added to DateTime control

Valid from Pega Version 8.2

The autogenerated DateTime control, used in forms, now features a custom date range option in the calendar picker. To specify a time period, click the From date and To date fields on an interactive calendar overlay. This input method is both convenient and mobile-friendly.

Enhancements to the AJAX container

Valid from Pega Version 8.2

It is now possible to set a document limit for an AJAX container, between 2 and 16 to control the number of documents opened by users. To reduce development time, you can also choose a new option to have no default view. The multidocument mode features tabbed navigation so that users can switch between open documents. A tabless container, on the other hand, includes an out-of-the-box navigation action for Home, which helps application users move within the portal.

For more information, see Configuring the AJAX container.

Moderate and severe guardrail warnings require justification

Valid from Pega Version 8.2

When checking in a rule, all moderate and severe warnings must be justified. Guardrail warnings now appear in a warning header when you save a rule that has warnings. Requiring justification encourages developers to address guardrail warnings. For more information see Application guardrails require justification.

 

Ready to crush complexity?

Experience the benefits of Pega Community when you log in.

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