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

Designer Studio

Valid from Pega Version 7.1.3

Numerous usability improvements were made for this release. A group of cosmetic, functional, and performance enhancements were also included.

  • Treegrid controls work more quickly in IE9 and IE10.
  • On application ruleforms, the 5.4 "Place Properties on Thread Page" checkbox will work in 7.1.
  • Message error handling has been improved.
  • Log messages have been cleaned up.
  • Connectors may now be used in Data Pages.
  • Move Rules wizard has been enhanced to work in Version 7.1.

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.

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.

Support for additional health metrics on the Application Quality landing page

Valid from Pega Version 7.4

On the Application Quality landing page, you can monitor the health of your current application to identify areas that need improvement before deployment. The landing page provides application metrics such as the number of executable rules, the guardrail score, the number of guardrail warnings, the test coverage percentage, and the pass rate of PegaUnit tests. From this landing page, you can also view data for the entire application, for each of its cases, and for rules that are not part of any case type.

For more information, see Application Quality landing page.

View the configuration settings for Pega Platform nodes in Designer Studio

Valid from Pega Version 7.4

On the new Configuration Settings landing page, you can view a list of the configuration settings for a specific node, current or remote, or for an entire cluster. From this landing page you can diagnose settings issues, determine whether settings are loaded correctly, and review the settings' purposes. You can also download the prconfig.xml file for any node in a cluster to modify the settings. The ability to view settings for all nodes in the Cluster from a single landing page makes diagnosing configuration issues across the cluster simpler and easier than logging on to each node individually to view its system settings. For example, if a started agent does not run, you can check if agents are enabled on your system; or if some of your caches are too big, you can check the setting for the cache size. You can also determine if settings are loaded correctly, and identify discrepancies in the settings across the nodes.

For more information, see Viewing the current configuration settings of a node or the whole cluster, Downloading and viewing the prconfig.xml file for a specific node, REST APIs for viewing the configuration settings for Pega Platform.

Support for templated auto responses during email triaging of interaction cases

Valid from Pega Version 7.4

When you triage an interaction case by email, you can now select a predefined email response to provide feedback to a customer more quickly. The category that is associated with this email determines the type of responses that you can select. You can create an email response template or use an existing template.

For more information, see Defining suggested replies for the Email channel.

Submit application changes made in Pega Express to a continuous integration and delivery pipeline

Valid from Pega Version 7.4

After you make changes to your application in Pega® Express, you can submit these changes into a continuous integration and delivery pipeline that is configured in Deployment Manager. By using Pega Express to submit your application changes into staging, preproduction, and production systems, you can quickly start builds without involvement from IT.

For more information, see Starting a continuous delivery build.

Ability to run report definitions against an Elasticsearch index

Valid from Pega Version 7.4

To improve report generation performance, you can now run report definitions against Elasticsearch indexes instead of using SQL queries directly against the database. This feature is disabled by default and does not apply to reports that have features that are not supported by Elasticsearch. If a report query cannot be run against Elasticsearch indexes, Pega® Platform automatically uses an SQL query.

For information about enabling and using this feature, see Configuring a report definition to run against an Elasticsearch index.

Search index fields can retain the original property type

Valid from Pega Version 7.4

You can now configure fields in the search index to retain the property type of the original property. By default, properties in an indexed class are converted to a string before they are placed in fields in the search index, referred to as a typeless index. Type-aware search indexes let you run report queries with filters, date calculations, and aggregations directly in the query. To configure a class to have type-aware properties, use a dedicated index.

For more information, refer to Custom search properties.

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