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.

Reports with visualizations of performance and automation levels for the email bot

Valid from Pega Version 8.5

In the Email Manager portal, you can now use built-in reports to visualize Pega Email Bot™ performance and the automation levels that are related to received emails, triaged cases, and created business cases. You can plug the reports to display the report data in other portals, for example the Case Manager portal. Based on the information displayed in the reports, you can adjust the machine learning models to achieve greater automation in the system.

For more information, see Viewing the reports for the Email channel and Built-in reports for the email bot.

Improved experience when building an IVA and Email Bot in App Studio

Valid from Pega Version 8.5

Build your Pega Intelligent Virtual Assistant™ (IVA) and Pega Email Bot™ while working only in App Studio. This approach makes the design process easier and more intuitive, and saves you time. You can now modify the advanced text analyzer configuration while working in App Studio. In addition, if you have access to Dev Studio, you can edit the text analyzer rule from App Studio for your chatbot or email bot by clicking a link to open the settings in Dev Studio.

For more information, see Adding a text analyzer for an email bot and Adding a text analyzer for an IVA.

Triage cases archiving in the email bot (Pega Cloud Services)

Valid from Pega Version 8.5

For Pega Platform™ that is installed in Pega Cloud® Services, you can configure Pega Email Bot™ to archive resolved triage cases that are older than a specified number of days. Archiving triage cases improves the overall performance of your system by reducing the primary storage consumption and cost because the system places such resolved triage cases in a secondary storage.

For more information, see Archiving resolved emails for an email bot (Pega Cloud Services).

Usability improvements in the Email Manager and Case Manager portals

Valid from Pega Version 8.5

Pega Email Bot™ customer service representatives (CSRs) working in the Email Manager, Case Manager, or Case Worker portals can now quickly reply to one recipient or to all recipients. CSRs can also view the sentiment analysis of an email (positive, negative, or neutral) for each received email, displaying the sentiment pattern for the entire email thread in a triage case. The email bot improvements add value for CSRs working in the portals and help them save time when responding to user requests.

For more information, see Understanding the email triage process and Replying to customers by email for an email bot.

New database tables for email bots

Valid from Pega Version 8.5

Pega Email Bot™ now uses two new database tables that make the system more reliable and improve system performance. The pc_work_triage table stores complete information about email triage cases for the email bot. The pr_index_tracktriageactions table stores information about captured actions in triage cases.

Upgrade impact

During an upgrade to Pega Platform™ 8.5, a dedicated job scheduler automatically migrates resolved and open triage cases to these email bot tables in the background. If you expose additional properties as database columns or expose additional custom columns in the pc_work table, you must prepare your application for this automated migration. For more information, see Migrating triage cases to new tables.

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

If the pc_work table in your application has no additional properties or custom columns, there is nothing to do; if it does, prior to an upgrade to Pega Platform 8.5, you must extend the pyPopulateColumnNamesExtension data transform to any exposed additional columns in legacy tables with this information.

For more information, see Database schema for email bot tables.

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.

Discontinued support for list view and summary view rules

Valid from Pega Version 7.2

The list view rule and the summary view rule are deprecated, and support for these rules has been discontinued. Existing list view and summary view reports will continue to work on supported browsers. However, the last version of Internet Explorer that list view and summary view rules support is Internet Explorer 11.

You cannot create new list view or summary view reports. Instead, create list reports and summarized reports by using the report definition rule. To prevent display issues, re-create the custom list view and summary view reports that you need as report definition reports.

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.

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