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.

Tracked changes persist between client sessions

Valid from Pega Version 7.1.7

The Microsoft Word native change tracking feature persists between client sessions for specifications. Enable this feature to facilitate collaborative reviews of your specifications with project stakeholders.

Inserting your specification updates as tracked changes allows you to:

  • Provide visible markup to the next reviewer.
  • Correlate edits to a specific user and time.
  • Generate documents that include markup and comments.

Local settings, such as the colors you specify for markup, do not persist between clients.

For instructions on how to prevent markup and comments from appearing in generated documents, see Advanced options for editing specifications.

Add multiple attachments at once

Valid from Pega Version 7.1.7

You can now add more than one attachment to a requirement or specification at a time, without closing the Add/Edit Attachment modal dialog box. Use the traditional browse method to upload an attachment or drag and drop a local file, based on your needs. View and access your attachments from the Application Profile landing page, Requirement form, or Specification form.

Plan projects using release data

Valid from Pega Version 7.1.7

Requirements and specifications can now be mapped to a target release and iteration within a specific release. Populating these fields allows you to set and publish a release schedule through worksheets generated by the Sizing wizard. Access these fields from the Application Profile landing page or by opening any requirement or specification.

The Release and Iteration fields as they appear in a specification and a corresponding worksheet

The Sizing wizard incorporates values from the Release and Iteration fields for specifications only.

Specification type extended for decisioning users

Valid from Pega Version 7.1.7

Specifications now support a Decision Strategy Manager (DSM) type. This allows you to map your specifications to a decisioning component, such as a strategy or model. After you select an appropriate subtype and provide relevant metadata, you can run the Sizing wizard to incorporate these details into project sizing worksheets.

DSM specification details as they appear in the Specification form and Sizing wizard output

You must have access to Decision Management rulesets to create DSM specifications. For more information on specification types, refer to the Details tab of the Specification form. To view all specifications in your application, filtered by type, refer to the Application Profile landing page.

Add collections as linked implementations

Valid from Pega Version 7.1.7

You can now identify a collection or individual steps within a collection as an implementation of a specification. Linking specifications to rules allows you to more accurately convey your application design to project stakeholders. Use the Specifications tab on the Collection form to create these links.

To see all implementations for a given specification, refer to the Application Profile landing page or the Implementations tab of the Specification form.

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