Published Release Notes

Automatically generate OpenAPI Specification documentation for application REST APIs

You can now access a clear, standard view of all the REST APIs in your application by using autogenerated OpenAPI Specification (OAS) documentation. In App Studio, you can view the OAS documentation generated for application-specific REST APIs by using the new Application tab in the API channel. Additionally, service package rules now include an OpenAPI tab where you can view the automatically generated OAS documentation for all the REST services included in the service package. With these enhancements, you can easily find, visualize, and test the REST APIs in your application.

For more information, see Generating OpenAPI Specification documentation for application-specific REST APIs.

Email listeners no longer copy the email subject text to the email body

As of Pega^® 7.2.1, email listeners no longer copy the email subject text to the email body when the body is empty. If your customer application expects text in the body of the email, the application might fail. You can configure email listeners to copy the subject text to the body by using the following Dynamic System Setting:

Owning Ruleset: Pega-IntSvcs

Purpose: email/copyBodyNoContent

Value: true

For more information, see Creating Dynamic System Settings.

New send email automations and enhancements

You can now configure cases, flows, and activities to compose and send guardrail-compliant emails that conform to the MIME standard by using email automations. Use the new Call-Automation method to call an automation from an activity without writing Java.

You can also now categorize error messages in automations to quickly understand the type of error that occurred. In addition, page list data types are now supported for inputs and outputs in automations.

For more information, see Calling an automation from an activity and Viewing automations.

Facilitated application development with saving changes in branches in App Studio

For improved development of your application, you can now define branches in which you save changes that you make to your application in App Studio. Create features in branches so that you can review and merge them without affecting other features in the application. You can quickly identify and review any changes to rules because you know in which application layer they were saved. 

For more information, see Setting branch preferences in Dev Studio, Setting branch preferences in App Studio.

Drag-and-drop functionality for lists and tables

Lists and optimized tables now support the reorganization of their content by reordering items. By configuring repeating dynamic layouts and tables to support drag-and-drop modifications, you enable users to move items between lists and within lists and tables. This enhancement ensures that you can create a flexible and dynamic user interface that helps users display and manage data.

The drag-and-drop functionality can also include custom actions that automate the processes that run when users move items.

For more information, see Configuring drag-and-drop functionality for lists and Configuring drag-and-drop functionality for tables.

Tertiary AJAX container support

Harnesses can now contain up to three AJAX containers which helps you to use the screen area even more efficiently and effectively organize content on the screen.

For more information, see Adding an AJAX container.

Ensure event strategy reliability through unit tests

You can now automate event strategy testing and increase the reliability of the event strategy configuration through unit tests. Avoid errors and ensure that the strategy delivers the expected results by configuring assertions on property values, aggregates, and result counts.

For more information, see Increased event strategy reliability through unit testing.

Increased display area in mobile apps

Mobile apps now support hiding the top and bottom bars when the user scrolls down. When the user scrolls up, the bars appear again. This enhancement improves the mobile user experience by presenting more data on the screen, for example, a longer list of items.

For more information, see Advanced layout options.

Create custom criteria for proposition filters by using the condition builder

Proposition filters now use the condition builder to define the criteria that a proposition or group of propositions must match in order to be offered to a customer. The condition builder provides a simple, flexible tool for selecting and grouping the entry criteria.

For more information, see Create custom criteria for Proposition Filter rules with the condition builder (8.3).

Pagination for repeating dynamic layouts

Repeating dynamic layouts now support pagination, so that you can display extensive sets of data in smaller portions. Additionally, you can add custom icons or messages to inform users whether more data is available.

For more information, see "Pagination" in Configuration options for layouts.