Published Release Notes

Support for multiple attachments added to Pulse

You can now upload more than one attachment to posts and comments in Pulse. Because Pulse maintains the continuity of attachments in posts, email messages, and email notifications, you can use it to quickly follow conversations in a case.

For more information about the features that Pulse supports, see Communicating with Pulse.

Ability to generate a dedicated search index for a case type

You can generate a dedicated search index for a case type. Using a dedicated index makes reporting faster without putting additional requirements on the database. 

For more information, see Including indexed data during case search.

Define time conditions for pausing a process in App Studio

You can now pause a process in App Studio until a date or time is reached or a certain amount of time has passed. By defining the conditions that pause a process, you can create dependencies among cases in your application.

For more information, see Pausing a process in a case.

Define participants for case types

You can now configure participants more easily for case types. By defining case participants, you can indicate their relationship with a case and share important case updates with them. You can update case participants at run time, route assignments and approvals to them, and send notifications to them when goals and deadlines are not met.

For more information, see Participant configuration for case types.

View data type relationships in Data Designer

You can now access a visual depiction of the relationships among data types from the Data Designer in App Studio. By understanding how data types depend on properties and other data types, you can extend your data model more quickly.

For more information, see Viewing data relationships.

Create and map data types in Integration Designer

Use the data type wizard in the Integration Designer to create data types and map them to systems of record. The data type wizard reduces complexity when creating and mapping data objects, resulting in reduced development time and a simpler workflow.

For more information, see Mapping fields.

Pin enhancements in spaces

Improve discussions in spaces and stimulate effective communication by using enhanced capabilities of pins. For example, you can search, filter, and like pins, or pin content of a space to another space.

For more information, see Pinning content to a space.

Changes to default Agent settings

Default agent settings across several rulesets have been updated in this release. Changes to settings include agents that are now:

• Disabled by default
• Scheduled to run at a recurring designated time interval (in seconds)
• Scheduled to run daily at a specified time

An example of some updated default agent settings. Compared to earlier versions, you can see in Pega 7.1.7 that ProcessCaseTypeCalculations and ProcessFlowDependencies are now set to run every 60 seconds, and that ProcessEmailRequest is disabled.​

​​This update allows operations staff to understand the general purpose of an agent by product, and enhances usability of this information by improving navigation of agents in large systems through filtering and sorting.

For more information, see Changes to default agent settings in Pega 7.1.7.

Ability to edit and copy data from an email to case properties for an Email channel

The procedure for triaging an email case has been improved to help automate the process and to ensure that the case data is always up-to-date and accurate. The system can pull data, such as a date, name, or an address, out of the received email or its attachments, and automatically assign the data to a spun-off business case property. To help the system learn, you can highlight using a color, edit entity types, and map entity types for an email triage case to business case properties. You can also update cases with new properties, if triage cases are identified as duplicates and contain new detected properties. Each mapped entity type is marked in different color and an entity map legend helps you identify what each color represents.

For more information, see Email triage and Defining suggested cases for the Email channel.

Change tracking tab removed from declare expressions

To simplify the configuration of a declare expression, the Change tracking tab has been removed from the declare expression rule form. To use the Change tracking tab, on the declare expression rule form, click Actions > Use legacy expression.

For more information, see Supported and unsupported configurations in simplified declare expressions.

Upgrade impact

The declare expression rules have been moved from the pr4_rule table to the new pr4_rule_declare_expression table.

The upgrade can fail if you customize the pr4_rule table, such as increasing the length of an existing column.

After a successful upgrade, the declare expression rule form is simplified and lightweight pages support declare expressions.

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

Read-only data pages by default are lightweight. You could also enable lightweight pages for:

• Editable data pages by selecting the Enable option in the editable data page rule form.
• For all pages in a REST service by using the Lightweight clipboard mode in the Service REST form in the Rest API service.

Only simplified declare expressions are supported in lightweight pages. In simplified declare expressions, context-bound rules are not supported. However, a page context could be specified on the New or Save As form of declare expressions. For more information, see Declare Expression rules - Completing the New or Save As form.