Skip to main content

Published Release Notes

Find release notes for the selected Pega Version and Capability

Browse resolved issues for Platform releases.

Support for the decisioning-enabled NLP text analyzer in IVAs and Email Bots

Valid from Pega Version 8.3

You can now use the new intelligent natural language processing (iNLP) text analyzer in Pega Intelligent Virtual Assistants™ (IVAs) and Pega Email Bots™. This advanced text analyzer is decisioning-enabled and empowers IVA or Email Bot for all conversational channels to provide smarter responses. The decisioning capability in the system integrates text analytics with strategies, prepositions, and interaction history, to provide the context for making better next-best-action decisions.

For more information, see Use the decisioning-enabled NLP text analyzer in IVAs and Email Bots, Defining advanced Facebook text analyzer configuration and Facebook channel behavior.

Upgrade impact

Existing channels remain with the current configuration, and their current functionality does not change. Channels created after the upgrade automatically use the new text analyzer.  

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

The new text analyzer is enabled or disabled using a new interactive API (iAPI) selection, which is selected by default for new channels. You can disable the iAPI for new channels if you want to maintain current functionality. You can also enable it for existing channels if you want to move existing channels to the new functionality.

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.

 

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.

Upgrading to the secure threading mechanism for email bots

Valid from Pega Version 8.1

In Pega Platform™ version 8.6, Pega Email Bot™ includes a more secure threading mechanism to help track emails from customers and other stakeholders in separate threads for an email triage case.

Upgrade impact

If you upgrade from Pega Platform version 8.5 or earlier, in which you configured an Email channel, perform the following steps to ensure that your system uses the new secure threading mechanism:

  • Update the service email rule that the system uses to send an email reply as the initial acknowledgment.
  • Update the email reply template in the data transform rule that the system uses when a customer service representative (CSR) sends the reply.

For more information about creating an initial acknowledgment email and email reply template, see Creating outbound email templates. For more information about the secure threading mechanism, see Use a secure threading mechanism in emails.

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

For the initial acknowledgment email used by your email bot, update the service method for your email listener rule. On the Response tab for this service email rule, expand the Message contents section. In the Message data section, you specify the rule that defines the structure of the content of the email body. In Pega Platform version 8.6, you use for this purpose the pyEmailAcknowledgement correspondence rule that takes into account the selected built-in template. This template includes the security code tag that the system uses for the secure threading mechanism. If your application uses a different rule in the Message data section, update this definition to match one of the built-in correspondence template rules, for example, EmailAckTemplate_Clear.

The pySetEmailBotReplyTemplate data transform rule sets the name of the email correspondence rule that the system uses as the email reply template. If you do not want to use the default approach using the Classic, Cobalt, or Clear outbound email template themes, override this data transform rule to set the email correspondence rule name for the Param.ReplyTemplate target in the Source column field.

For more information about how to update the service email rule and the data transform rule to ensure that your system uses the secure threading mechanism, see Upgrading to the threading mechanism available in the 8.6 version.

Insights from 8.5 require additional configuration after upgrade

Valid from Pega Version 8.6

Upgrade impact

After you upgrade Pega Platform™ version 8.5 to 8.6, the Explore Data landing page might not include insights that come from the earlier version of the product.

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

Run the pxUpgrade85Insights activity to make all insights from version 8.5 accessible for you in 8.6. By running this activity, you upgrade insights with new metadata that is required in version 8.6. For example, the pxUpgrade85Insights activity provides you with the option to set the visibility of insights to private, public or shared.

For more information about insights, see Visualizing data with insights.

Method for specifying custom search properties has changed

Valid from Pega Version Pega Platform

The method for specifying a custom set of properties that are stored in the Elasticsearch indexes and that can be referenced later in filter conditions or returned in a set or results has changed. Previously, the pySearchModel Data Transform rule was used to specify a custom search property list within a class. The new method is to specify a Data instance of the Data-CustomProperties-Search class.

After upgrading to Pega 7.2, make these changes:

  • Reenter existing pySearchModel Data Transform rules as instances of Data-CustomProperties-Search data instances.
  • Enable the indexing/useDataInstances Data Admin system setting by clicking Records > SysAdmin > Dynamic System Settings.

After you change the set of custom search properties for a class, rebuild the Elasticsearch index for that class on the System Settings Search landing page.

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.

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.

New process for Pega Cloud customers to obtain BIX extract files

Valid from Pega Version 7.3

The process for obtaining Business Intelligence Exchange (BIX) extract and manifest files for Pega® Cloud customers has changed as a result of data security enhancements for HIPAA compliance. By default, after upgrading to Pega 7.3, you must obtain the BIX extract and manifest files from the Pega SFTP server. From within Designer Studio, you can configure the BIX extract and manifest files to be sent to a remote SFTP server by a file listener. For Pega Cloud customers who have purchased a Pega Cloud SFTP Server subscription, you can configure BIX to send the BIX extract and manifest files to the SFTP server's folders for remote SFTP client download.

For more information about obtaining files from the Pega SFTP server, see Obtaining BIX extract files from the Pega SFTP server.

For more information about having files sent to your SFTP server, see Defining SFTP-related data instances.

Ready to crush complexity?

Experience the benefits of Pega Community when you log in.

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