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.

 

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.

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.

New formats for styling report data grids

Valid from Pega Version 7.2.2

When you view a report, the data grid that is displayed is now styled by using either the List report format or the Summarized report format, depending on the report type. With this enhancement, you can display report data differently, and perhaps more effectively, than other grids in your portal. In the skin of your application, these new formats will be added and upgraded automatically by copying the Default format for the Trees & grids layout type, which was previously used to style reports.

For more information, see Modifying data grid formats for reports.

BIX -I command-line option fails for unexposed properties

Valid from Pega Version 7.2.2

Business Intelligence Exchange (BIX) command-line extractions fail when the extract has a filter that uses unexposed property references that are passed in by the input file that you specified in the -I command-line option. Previously, the BIX extraction ignored the filter and the extraction did not fail.

BIX filtering now works like report filtering

Valid from Pega Version 7.2.2

Filtering for Business Intelligence Exchange (BIX) extracts has been enhanced to work like report filtering, making it easier to use. Existing filters that use the Contains/DoesNotContain filter operation will be converted to use the Equals/NotEquals filter operation.

New PEGA0084 alert - Search node count

Valid from Pega Version 7.2.2

The PEGA0084 alert is generated when the number of available index host nodes does not meet the quorum ((replicas/2) + 1) required for index writes to succeed. This alert can occur when some of the index nodes go down, causing the number of available index host nodes to be less than the quorum. For more information, see PEGA0084 - Search node count.

Style charts in the application skin

Valid from Pega Version 7.2.2

You can now style charts in your application skin by selecting Charts in the Controls section and setting a theme. When you style charts by using a theme, charts that are generated for report definition reports and the autogenerated chart control are styled consistently, and you do not need to style charts individually. In addition, you can preview chart themes in the Skin form to see how different charts look without launching an application.

For more information, see Styling charts in the application skin.

View status of custom search indexes

Valid from Pega Version 8.1

Custom search indexes are special purpose indexes that are created and managed outside of Pega Platform™. You can view the status of custom search indexes on the Search landing page to see whether they are complete. This information is useful for troubleshooting and can help you determine whether to rebuild the index.

For more information, see Checking search index status.

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