Published Release Notes

Label changes for text analytic models

The classification analysis label has changed to topic detection and the entity extraction label has changed to text extraction. Also, the sentiment analysis, topic detection, and intent detection labels are now located under Text Categorization in the Analytics Center. These name changes reflect industry standards and provide a clearer distinction between different types of text analytics models in Pega^® Platform.

For more information, see Text analytics models.

CRM core data types included in Pega Platform

Customer Relationship Management (CRM) core data types are now included with Pega^® Platform, making it easier to bring your data into your Pega application. You can either import your data into the data tables for the CRM data types or use integration to communicate with your own system of record. The database tables for these data types are non-Pega formatted, which gives you better performance and more control over your data.

For information about the database tables, see CRM data types in Pega Platform.

Savable data pages support loading pages individually from a page list

You can now load individual pages in a page list from single object data pages to your case and data types. This functionality allows you to save autopopulated properties with the Load each page individually option using a flow action, save data page smart shape, or the activity method.

For more information, see Saving data in a data page as part of a flow.

Consistent search experience in App Studio

Pega Platform™ now supports a unified search mechanism in App Studio. Instead of manually locating a single item, such as a case type, a channel, or a data object, you can simply use the Search option in the navigation pane. You can also use Search in case types and personas landing pages, to conveniently access the information that you need, for example channels and case types associated with a persona.  

For more information, see Plan your Microjourneys more conveniently in an improved Case Designer (8.5), Creating a Microjourney for customer success.

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

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.

Life cycle tab renamed to Workflow

The Life cycle tab for case types has been renamed to Workflow. On the Workflow tab, you can define a life cycle for case types by clicking Life cycle, and you can define user actions for case types and stages by clicking Optional actions.

For information about defining a life cycle for a case type, see:

• Pega Express 7.3.1 – Defining a life cycle for a case type
• Pega Platform 7.3.1 – Defining a life cycle for a case type

For information about user actions, see:

• Pega Express 7.3.1 – User actions
• Pega Platform 7.3.1 – User actions

Generate an XSD file for XML format output

You can now use Business Intelligence Exchange (BIX) to generate an XSD file for existing XML output when the Get all properties check box is selected on the Definition tab of the Extract rule form. You can now validate the XML output and generate DDL statements by using the generated XSD file. Some tags might not be included in the generated XSD file because of missing values in the XML output.

For more information, see Generating an XSD file for XML output.

Section preview added for templated sections in Designer Studio

When you create a templated section, a preview displays on the Design tab of the Section form, showing how the section will look at run time. The section preview immediately shows the results of each design change that you make as you add, move, or delete elements, resize the section, or modify the application skin. By helping you visualize the section's runtime appearance, section preview reduces rework and saves you development time.

For more information, see Section preview shows changes in real time for templated sections.

Database

Improvements to data handling were made for search indexing, agent processing, and filtering.  Scripts were provided for proper population of the database tables.

• Importing data from shared obj-external tables is now supported.
• A validation warning will now display when an unexposed property is used in filter or join conditions.
• A Global Search index may now be created across two databases.
• Agent processing on multiple nodes has been improved.
• Improvements were made to controls in Report Definition pages which are used in a dynamic grid.
• Filtering functionality involving special characters has been enhanced.
• Scripts have been provided to populate the RuleSetVersion Major, Minor, and Patch columns.

Use fast processing option does not work

The Use fast processing option on Connect REST and Service REST rule forms does not work unless you obtain the HFix-43000 hotfix from Global Customer Service.

Use the following data model guidelines when using fast processing:

• The JSON property names and the clipboard property names must match.
• The JSON tree structure and the clipboard tree structure must be similar.
• The scalar arrays in JSON must be mapped to the clipboard as page lists.
• Multi-dimensional arrays must be mapped into page lists of page lists with the same embedded property names.

​In addition, page groups, value groups, and Java objects are not supported by fast processing.