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.

Low-code styling in mobile apps

Valid from Pega Version 8.5

The mobile channel now supports enhanced low-code styling and branding of mobile apps. For example, you can customize app icons in three different ways: by uploading an image, by selecting from a list of font icons, or by using the default text-based icons. This enhancement helps you to conveniently customize the look of mobile apps to match the branding guidelines of your company and provide a consistent experience for users across different channels.

For more information, see Applying a custom theme to mobile apps.

Offline support for Cosmos-based mobile apps

Valid from Pega Version 8.5

Mobile apps that are based on the Cosmos design system now support offline mode. Previously, offline-enabled apps had to rely on the classic look. Now, you can use the low-code Cosmos solutions to design apps that operate reliably regardless of the connection status. 

For more information, see Designing apps for offline mode.

Enhanced search in the mobile channel

Valid from Pega Version 8.5

The search configuration now includes up to three additional secondary fields, such as the case ID, category, cost, date, owner, and active channel. The enhancement increases the usability of search on mobile apps and provides more contextual information in the search results.

For more information, see Adding a search gadget.

Improved mobile channel user experience

Valid from Pega Version 8.5

Mobile channel authoring now includes two significant enhancements to the user experience. The new instant run-time preview makes security configuration more convenient. In addition, the offline tab is now present by default, to help you build offline-enabled mobile apps and complete assignments in areas with limited connectivity.

Enhanced swipe support for case actions

Valid from Pega Version 8.5

UI authoring in the mobile channel now offers more case-wide actions that can be performed by swiping on list items. For example, you can add a swipe action to attach an invoice to your expense work item. This enhancement increases usability and work efficiency as it allows for fast, instinctive mobile interactions.

For more information, see Designing a new mobile list page.

Descendant class instances now included in reports

Valid from Pega Version 7.2

The Report on descendant class instances option on the Data Access tab of the Report Definition rule has a new option to now include data from all descendant classes of the report's primary class. If descendant classes are mapped to multiple class tables, the generated SQL query performs UNIONs to include this data. Previously, only a single class was included in the report.

You can select a subset of descendant classes to include or exclude by adding a filter condition on pxObjClass.

Existing reports retain the older behavior for this option after an upgrade or update. To use the new option, you must set it for each existing report. New reports created in Designer Studio and out-of-the-box Pega 7 Platform template reports from which new reports are created in the Report Browser (pyDefaultReport and pyDefaultSummaryReport) default to the new option. If you have created custom template reports for some application classes, you must change them to enable the new option in reports that are created in the Report Browser for these classes.

See Reporting on data in multiple class tables.

Report Definition query filters can search embedded properties

Valid from Pega Version 7.2

Filter conditions on Report Definition rules that query the Elasticsearch indexes can now reference embedded properties. Previously, filter conditions could reference only the top-level properties of a class. To reference an embedded property within a filter condition, specify indexes for embedded page lists and page groups, for example, Customers(1).Addresses(1).City = Boston OR Customers(1).Addresses(1).State = MA.

These indexes are ignored in the generated query, and so can potentially match any value in a page list or group. However, filter conditions that reference multiple embedded properties in the same page list or page group, as displayed above, might not be satisfied on the same page.

BIX extracts can be scheduled and run from the Pega 7 Platform by using agents

Valid from Pega Version 7.2

You can create an agent that periodically invokes the new pxExtractDataWithArgs activity to run a BIX Extract rule. The activity takes the class and extract rule name, as well as an additional input string with a list of BIX command-line parameters, as input parameters to use for the run.

Report Definitions can query tables in multiple schemas

Valid from Pega Version 7.2

You can create a Report Definition that queries class tables in multiple schemas in the same database. Previously, queries on tables that were mapped to PegaRULES and PegaDATA schemas could not include tables that were mapped to other schemas, because other schemas were assumed to be in a different database. The schemas to which queried class tables belong are no longer validated when you save the Report Definition, so you can now query tables in schemas other than PegaRULES and PegaDATA. However, Report Definitions that query tables that are in more than one database fail when run.

Support for large reference data in offline mobile apps

Valid from Pega Version 7.2

A data page in a Pega 7 Platform mobile application with offline capability enabled can now be marked as a large data page. This feature improves performance significantly when you have a large amount of data in which only individual records change.

In this situation, after the initial sync to the mobile app, only the changes in the large data page are synced instead of the entire large data page. The database table is created for such large data pages in the encrypted SQLite database on the device. Changes such as add, delete, or update are reconciled as row-level updates. Furthermore, you can use JavaScript to query against this data. A large referenced data page is supported by list-based components such as repeating dynamic layout, auto-complete, a dropdown list, and radio button.

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