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 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.

Removal of Pega Mobile Client 7

Valid from Pega Version 8.5

You can now use a single Pega Mobile Client™ that improves app performance, app development, and meets all your mobile needs. With the introduction of new functionalities for mobile apps, Pega Mobile Client 7 is removed in Pega Platform™ 8.5.

Upgrade impact

After an upgrade to Pega 8.5, you can no longer build mobile apps based on Pega Mobile Client 7, and existing apps based on Pega Mobile Client 7 no longer connect to Pega Platform. App developers can now configure mobile apps with Pega Mobile Client.

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

Existing clients that upgrade to Pega 8.5 are automatically switched to Pega Mobile Client.

Failed Robotic Assignments work queue type changed to Standard

Valid from Pega Version 8.5

The default Failed Robotic Assignments work queue type is now Standard. In previous releases, the default type was Robotic. For usage information, see Configuring a work queue for robotic automation.

Upgrade impact

After upgrading to Pega Platform 8.5 and later, you cannot save case types in which you configure the Queue for robot smart shape to route new assignments to the Failed Robotic Assignments work queue. Existing assignments that you routed to the Failed Robotic Assignments work queue are not affected.

How do I update my application to be compatible with this change?

As a best practice, do not use the Failed Robotic Assignments work queue in your custom implementations. Instead, configure the Queue for robot smart shape to route new assignments to a Robotic work queue. When possible, update existing case types to use the robotic work queues that you created in your application.

Web portal reuse removed from the mobile channel

Valid from Pega Version 8.5

The reuse of web portals for creating mobile apps with a single web view is no longer supported. You can conveniently update your existing channels that reuse web portals to take advantage of the multiple-views experience and native mobile capabilities, such as native mobile list views or floating action buttons.

Upgrade impact

The Reuse web portal option is removed from Pega Platform 8.5 and later.

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

App developers need to use the migration tool available on the mobile channel to move their apps to the recommended new navigation designer. When users open existing mobile channel with the Reuse web portal option configured, they are prompted to run through the wizard to upgrade the mobile channel to the latest Pega Mobile Client based configuration. When this is done, app developers should rebuild the app.

 

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.

Native synchronization indicators for offline-enabled mobile apps

Valid from Pega Version 8.5

Offline-enabled mobile apps now include a set of native synchronization indicators. Indicators keep users informed about the data synchronization status, for example, the Syncing indicator appears when an app regains network connectivity and starts receiving responses from the server. You can customize the indicators to better suit the look and feel of your mobile app. For more information, see Customizing synchronization indicators.

Upgrade impact

After upgrading Pega Platform™ to version 8.5, your app does not include native synchronization indicators until you update your application to use UI-Kit 15.

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

Update the UI Kit in your application to version 15. For more information, see Updating the UI Kit in your application.

Service Portlet rules are deprecated

Valid from Pega Version 8.2

Service Portlet rules are deprecated. Existing rules will continue to work, but you cannot create new ones. Use Pega Web Mashup instead. In addition, some changes might impact functionality. If you are using Portlet rules and plan to upgrade, contact your customer service representative.

For more information about Pega Web Mashup, see About Pega Web Mashup.

Deprecated metadata types in the Connector and Metadata wizard

Valid from Pega Version 8.2

The WSDL, SAP WSDL, and DTD metadata types have been deprecated in the Connector and Metadata wizard. For WSDL, use SOAP integration, and for DTD, use XSD.

For more information about SOAP connectors, see About Connect SOAP rules. For more information about XSD, see About the Connector and Metadata wizard.

Deprecated support for passing symbolic index as strings to value lists and page lists

Valid from Pega Version 8.2

Starting with the next release after Pega Platform™ 8.2, passing symbolic indexes as strings in parameters, properties, and string literals to both value lists and page lists will no longer be supported. The following examples show the syntax that still works in Pega 8.2, that will not work in the next release:

myPageList("<LAST>")

and

param.str = "<LAST>"
myPageList(param.str)

The following example shows syntax that currently is not supported and gives a validation error. This syntax will also not work in future releases.

param.str = <LAST>
myPageList(param.str)

To avoid issues after upgrading to Pega 8.3, refactor all occurrences of this syntax in your code. For instructions on how to find occurrences of this syntax in your code, see Refactoring unsupported symbolic index syntax for value lists and page lists.

For more information about the correct use of symbolic indexes, see Symbolic indexes – APPEND, CURRENT, INSERT, LAST, and PREPEND.

Improved rich user interface controls in IVA for Web Chatbot

Valid from Pega Version 8.3

In Pega Intelligent Virtual Assistant™ (IVA) for Web Chatbot, you can use additional rich user interface controls, such as the time and date picker or a simple form, to help users accomplish tasks more quickly and to limit errors. IVA for Web Chat can now also display a welcome message in the chat window, for example, to inform the user about the person with whom they are chatting.

For more information, see Streamline conversations in IVA for Web Chatbot with rich user interface controls.

Upgrade impact

The new Ul controls for Web Chatbot are enabled by default upon upgrade. If you do not want the controls enabled, you must disable them.

Also, if you have changed the styles for the welcome message, you may need to make changes to the welcome message to incorporate the new areas in the bot conversation area (such as quick replies).

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

Existing channels will behave as they did previously, so you should determine whether you want to use the new UI controls. If you want to use the new Ul controls, configure the new design-time options.

If you have changed the default styles for the welcome message, review the new settings to ensure that the welcome message is configured properly. 

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