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.

Support for multiple work queues in the Email Manager portal

Valid from Pega Version 8.3

Pega Email Bot™ now provides multiple work queues in the Email Manager portal. With this functionality, operators, such as customer service representatives, can now triage cases more efficiently by selecting different work queues. Operators have access to work queues only for the current Pega Platform™ application.

For more information, see Email Manager portal.

Automatic model training when mapping entities to case properties in Email Bot

Valid from Pega Version 8.3

You can now initiate automatic feedback to entity models in Pega Email Bot™, during manual mapping of email content to a case property.

To enable automatic feedback, you set the Work-Channel-Triage.pyIsRuntimeFeedback rule to true in Pega Platform™. By default this feature is disabled. Enabling this feature ensures that the email bot is more responsive by automatically copying detected entities, such as names, locations, dates, and ZIP codes, to case type properties of a case type.

For more information, see Email triage, Email channel NLP model and Enabling the NLP model training for the email channel.

New property pxCommitDateTime

Valid from Pega Version 7.1.8

A new property, pxCommitDateTime, records the time when a record or updated rule was committed to the database. This property also allows for incremental extracts when running BIX.

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.

New property pxSaveDateTime

Valid from Pega Version 7.1.8

A new property, pxSaveDateTime, records the date and the time that an instance was saved with business changes to the database. This property is always used when an instance is saved, whether you are creating an instance or updating an existing instance. This property is not updated when an instance is moved from one system to another, and it is not updated during certain system management operations that do not change the content of the instance, such as column exposure.

Ability to import and export Intelligent Virtual Assistant or Email Bot training data

Valid from Pega Version 8.3

You can now copy Pega Intelligent Virtual Assistant™ (IVA) or Pega Email Bot™ training data between Pega Platform™ application environments by performing an export and import action. Importing and exporting training data between Pega Platform application environments results in greater accuracy of entity detection. Entities are detected by the system in a chat conversation, including attachments, to help respond to the user correctly, and consist of proper nouns that fall into a commonly understood category such as a person, organization, or a ZIP code. The ability to copy training data also makes it easier to maintain IVA or Email Bot, and build its artificial intelligence.

For more information, see Copying training data to another environment and Copy training data and model to another IVA or Email Bot environment.

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