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.

Simple associations for quickly joining classes

Valid from Pega Version 8.3

Associations now have a simple mode. Use a simple association to quickly and easily join a class to another class. The simple association defines a left join, using a foreign key in the source class and the class key in the target class. Use an advanced association for all other conditions. In addition, simple associations are drawn in the Visual data model reporting mode to visualize the relationships that are available for reporting.

Upgrade impact

The new simple mode draws a map of where all the classes defined in the application rule are drawn as nodes. Relationships between the nodes that are defined by relevant properties are drawn as lines linking the two classes. This feature only includes Case and Data classes that are defined on the Application rule form's Cases and Data tab. It also only includes relevant fields for those classes in order to define the relationships from one class to another.

What steps are required to update the application to be compatible with this change?

After a successful upgrade, add the data and case type classes to the application rule in Dev Studio to have the selected classes appear as a node. In addition, if you want a relationship to display as relevant, set the properties (of the class that defines that relationship) as relevant.

 

For more information, see Exploring the data model.

Association changes after upgrade

Valid from Pega Version 8.3

Associations now have a simple mode. Simple associations are those that join to only one class, use a left join, and have one filter condition to a class key in the target class. Existing associations that define a simple foreign key relationship are upgraded to simple associations when opened; all others are treated as advanced associations. All associations continue to work in reporting.

Making an association simple changes only one piece of metadata; all other data on the association rule is not affected.

Upgrade impact

The new simple mode draws a map of where all the classes defined in the application rule are drawn as nodes. Relationships between the nodes that are defined by relevant properties are drawn as lines linking the two classes. This feature only includes Case and Data classes that are defined on the Application rule form's Cases and Data tab. It also only includes relevant fields for those classes in order to define the relationships from one class to another. 

What steps are required to update the application to be compatible with this change?

After a successful upgrade, add the data and case type classes to the application rule in Dev Studio to have the selected classes appear as a node. In addition, if you want a relationship to display as relevant, set the properties (of the class that defines that relationship) as relevant.

 

For more information, see Associations.

 

Change logic does not work in Report Editor

Valid from Pega Version 7.1.2

The Report Editor​ change logic button does not work. As a workaround, use the rule form to change the logic.

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.4

This release focused on improving the user experience of creating new rules and tightening up the use of specifications in the Case Designer.  The layout of the New and Save As forms were made more intuitive and intelligent.  Specification actions were made to be more consistent across various aspects of the Case Designer.

  • After removing specification references, users can create and save a new specification.
  • Developers may now choose either an existing specification or create a new one for subflows and Split-For-Each shapes.
  • If a specification is not associated with flow shapes such as sub flows, Utilities, or Split-For-Each, it is possible to import speciications with the same names, and the flow shapes will default to using those imported specs.
  • In the outline view, specification changes will be preserved when switching from tab to tab.
  • The View Full Details functionality from either Configure Step or the Outline View will display all details, including the specification requirement links.

Reporting & Data

Valid from Pega Version 7.1.4

This release fixed many existing unlocalizable elements in 7.1 reporting interfaces (The Report Viewer, Report Editor, Chart Editor, and the Report Browser) and now they are fully localizable. Changes were made to make Listview, summaryview,  and report viewer display possible WCAG 2.0 level A and AA support.

  • Parameters may now be used in a sub-report join condition.
  • Report Definition localization has been enhanced.
  • Standalone ListViews with embedded SmartInfo have been improved to resize appropriately when the SmartInfo section is expanded.
  • The data section of a report will now display in all of the available space when a fixed header option is selected.
  • When localizing a listview with filters, tool tips are translated.

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.

Reporting

Valid from Pega Version 7.1.3

This release had a focus on extending key capabilities to improve the functionality and ease of use of reporting features based on early adopter feedback.  A series of cosmetic changes and fixes are also included.

  • Multiple boxes may be checked on List view checkboxes
  • Dashboard Charts slider has been improved.
  • Summary View reports and charts have been enhanced.
  • Column properties can be added to a report in the Report Editor.
  • List view column widths can be set by Smart Info.
  • Listviews will display correctly for updated systems.
  • Improvements to the GuardRail Report.

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.

BIX performance improvements for CSV output in the Pega Cloud

Valid from Pega Version 7.2.1

BIX performance has been enhanced to download up to 25 GB of data per hour for extracts from a BLOB-less class table for CSV output. This high-throughput option is available only for Pega Cloud instances that use a Postgres database. This option is used automatically for these types of extracts.

When this option is used, the –x and –c command-line options for BIX are not supported, and the checkSum field in the manifest summary is not populated. If you need these options, you can revert to the previous implementation by using a setting in the prconfig.xml file.

For more information, see BIX high-throughput data downloads in the Pega Cloud.

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