Published Release Notes

Immediate drain available for the quiesce process when using high availability

The quiesce process, which is used to take a server out of service for maintenance in a highly available system, can now be modified to use the immediate drain method. When using the default slow drain method for quiesce, users are placed in a passivation queue. When using the immediate drain method, users can continue to access the node being quiesced until it is removed from the load balancer.

Organizations should determine which quiesce method to use based on the overall needs of their users. However, for applications that have implemented long poll requests, it is recommended to use the slow drain method.

For more information, see the Pega 7.2.1 High Availability Administration Guide.

Debugging data synchronization issues with offline-enabled applications

If an offline-enabled mobile application that originates from the Pega 7 Platform fails to synchronize data after reconnecting to the server, the Pega 7 Platform generates a PEGA0066 alert. The alert includes detailed information about the failure, such as the activity that preceded the event, entries collected from the native application, and entries from the JavaScript part of the Pega 7 Platform application. The administrator can use the alert and device logs to facilitate error analysis and debugging without having to access the failing device.

For more information, see Understanding the PEGA0066 alert - Mobile App Data-Sync Failure.

Data APIs support data exploration in React UI tables

Data APIs have been enhanced to support filtering, sorting, paging, and aggregation in React UI tables. You can use that functionality to access your data quickly and intuitively. For example, by using paging, you can query a data page to retrieve the second page of an employee contact list and specify the number of results that are displayed on the page.

For more information, see Data API performance and limitations.

Enhancements to token lifetime limits

Pega Platform™ uses OAuth 2.0 authorization codes, access tokens, and refresh tokens to provide flexible token-based security for applications. Expiration settings for these codes and tokens now adhere to certain strict value range based on industry leading practices. For example, the lifetime specified for the authorization code must be in the range 1-600 seconds.

These can be configured in the OAuth2 Client registration rule form.

For more information, see OAuth 2.0 Management Services.

Building custom mobile apps that require a password to start

To provide extra protection of local data, you can now require user passwords for custom mobile apps. Requiring a password can increase the app's initiation time, but additional protection might be needed for applications that store sensitive information. In Designer Studio, on the Mobile tab, select Enforce user password on start to require user passwords.

For more information, see Configuring password enforcement.

Time-based retrieval of Facebook posts

You can now control the amount of data that is retrieved from Facebook data sets by using the new search functionality for Facebook data set records. You can limit the retrieval of posts to any number of past weeks, days, hours, or minutes to get only the data that is relevant to your business objective or that you lost as a result of a system outage or failure.

For more information, see: Improved Free Text Model rule type.

Improved view authoring

Case authoring in Cosmos React UI now features updated view authoring tools. The redesigned view tab and overlay provide a more intuitive interface for creating views, applying design templates, and adding fields and controls. This enhanced work environment improves the user experience and reduces context switching, which contributes to a lower development effort.

For more information, see Editing views in a case type.

Quick and customized data imports

You can now quickly add, update, or delete data records for your data types by uploading .csv files that contain a large number of records. The bulk import process allows you to import data from a variety of sources and gives you more control over your data. You can customize this process by overriding a data transform to add purposes, a section to add fields, and an activity to define the logic for each purpose.

For more information, see Data import customization.

DocuSign integration

You can now integrate DocuSign with your Pega 7 Platform application to collect digital signatures during case processing. You can make a signature request to DocuSign by adding the Send via DocuSign smart shape to your flow. You can customize your request by overriding the data transforms that are used to make a successful signature request to DocuSign.

For more information, see Integrating DocuSign with the Pega Platform.

Flexbox layout mode for dynamic layouts

The flexbox layout mode is available for dynamic layouts and is now the default layout mode for newly created dynamic layouts. In a flexbox layout, sections contained within the layout can grow or shrink to fit the available space, providing a more efficient way to distribute space between items in a container. Existing dynamic layouts can be converted to the flexbox layout mode. You can configure the layout mode on the Presentation tab of the Dynamic Layout property panel.

For more information, see Dynamic Layout Properties — Presentation tab.