Published Release Notes

File sharing improvements in custom mobile apps

Case management in custom mobile apps that are built for Android and iOS using Pega Infinity Mobile Client™ is now improved with the enhanced Attach content control. You can now attach files of any type from the device storage and from cloud services, for example, Google Drive or iCloud, or from other mobile apps that are installed on the device. Additionally, you can share any file attachments, except for signature files, in external mobile apps.

For more information, see Enabling attaching files to an application.

Custom DX API attributes for auto-generated controls

Auto-generated controls now include the option to add custom attributes for use with the Pega Digital Experience (DX) API. The attributes are part of the DX API response to the front end and you can use them to modify the run-time behavior of the UI elements in your application. For example, you can add an attribute to a field that displays a tooltip text for that field at run time. This enhancement introduces significant flexibility to application development and gives you greater control over UI components.

For more information, see Adding custom attributes for version 1 DX API to auto-generated controls.

Data schema requires update after multitenant upgrade

After an out-of-place, multitenant upgrade to Pega 7.2.2 from Pega 7.2 or later, the PR_DATA_TAG_RELEVANTRECORD table that is in the existing data schema is not present in the new rules schema. The table must be present in the rules schema for the upgrade to the rules schema to work. Copy the PR_DATA_TAG_RELEVANTRECORD table from the existing data schema to the new rules schema, and then upgrade the new rules schema. The PR_DATA_TAG_RELEVANTRECORD table is not required to be in the rules schema. After the rules schema upgrade is finished, drop the copy of the table that is in the new rules schema before you upgrade the data schema.

Support for email triaging of interaction cases for the Email user channel

You can now triage customer email content that is saved in an interaction case for the Pega^® Intelligent Virtual Assistant for Email. A customer service representative can reply to the email, reassign the interaction case to another user or a work queue, resolve the interaction case, or spin off a business case from the interaction case. Carrying out these actions improves the artificial intelligence capability of the Pega Intelligent Virtual Assistant for Email, for example, for automatic email routing purposes.

For more information, see Email triage an interaction case.

Post private messages in Pulse

You can now post messages in Pulse to initiate conversations with selected users within a context. By posting private messages, you can discuss specific topics with relevant users without broadcasting them to all users.

For more information, see:

• App Studio – Posting a message in Pulse
• Dev Studio – Posting a message in Pulse

Reference spaces and documents in Pulse

You can now reference spaces and documents when you post Pulse messages. By including a link in your Pulse message that opens a relevant space or application document, you can add context to a conversation.

For more information, see:

• App Studio – Adding a reference in Pulse
• Dev Studio – Adding a reference in Pulse

Create and assign tasks in Pulse

You can now create and assign tasks in Pulse for case work that needs to be completed within a specific time frame. For example, you can assign a task to yourself as a reminder to upload proof of address documents to a Car Loans case by the end of the day.

For more information, see Creating a task in Pulse, Enabling users to post messages in the activity feed.

Support for rich HTML text in IVA for Email

Pega Intelligent Virtual Assistant™ (IVA) for Email now supports rich HTML text in email conversations, which enhances the overall user experience. You can enable this option in the Email channel configuration in IVA for Email to display rich text in email conversations for case triaging. Natural language processing (NLP) analysis works flawlessly in scenarios for all email content that contains rich HTML text.

For more information, see Enabling rich HTML text in emails.

Stream-based alternative for interaction history

Accelerate the processing of high-volume interaction history data by incorporating a stream-based interaction history into your application. A stream-based interaction history processes large volumes of data more quickly than a traditional relational database interaction history so that you can react to your customers' needs in real time.

For more information, see Process high-volume interactions more efficiently and Aggregates-only mode for a stream-based interaction history.

Value list and value group properties are not supported inside data flows

Value list and value group properties are not supported inside data flows, and you need to instead use other property types.

See the Pega 7 developer help to check all available property types.