Published Release Notes

Preflight optimization extended to actions

The preflight optimization process now excludes JavaScript for actions that are not used in the application. To enable preflight optimization, click Designer Studio > User Interface > Application readiness > Preflight optimization.

For more information, see Optimizing application load time.

Ability to include all properties in search results

You can now include all properties in a class in search results so that they can be used in report filtering. When the Enable search results for all properties option is selected on the Custom Search Properties rule form, all top level and embedded page scalar properties for the class are indexed and returned in search results, and all embedded page list, page group, value list, and value group properties for the class are indexed but not returned in search results. Selecting this option might affect performance.

In addition, by default, properties defined in the Data-Tag-RelevantRecord instance for a class are indexed and returned in search results and do not need to be explicitly configured.

You must reindex search after selecting or clearing Enable search results for all properties and after changing the properties that are defined in the Data-Tag-RelevantRecord instance.

For more information, see Specifying custom search properties.

Pega API available in Pega Express

The Pega^® API is now included on the Channels and Interfaces dashboard in Pega Express. You can configure Pega APIs to access Pega application functionality directly from Pega Express without switching to Designer Studio.

For more information about channel interfaces, see Channels and interfaces. For more information about the Pega API.

Legacy rules removed to reduce Pega Platform installation size

The installation of Pega^® Platform 7.4 removes deprecated and unused rules. The smaller installation size decreases rule sync time and reduces the amount of storage required for Pega Platform. In addition, the smaller installation reduces the rule database size and shortens installation and upgrade times. You can access the legacy rules, if needed, in the PegaLegacyRules:01-01-01 in the Resource Kit on the Pega Platform media.

For more information see Finding legacy rules in sections.

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.

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.

Context-specific documentation is not available in express mode

Help topics that are opened from express mode display content that is specific to Designer Studio.

If your system is dedicated to applications that are developed in express mode exclusively, and you do not need Designer Studio help topics, you can set the Online Help URL field on the System Settings landing page to: https://pdn.pega.com/sites/default/files/help_p7e/procomhelpmain.htm. Alternatively, you can view the contextual help system for Pega 7 Express in a separate browser tab.

Layout groups support test ID on nested dynamic layouts

Dynamic layouts support the addition of a test ID to each dynamic layout within a layout group. Test IDs support automated testing by providing a unique identifier for user interface elements. Add test IDs to a dynamic layout within a layout group from the General tab of the layout properties.

For more information, see Dynamic Layout Properties - General tab.

Edit icons and titles for messages in the activity feed

You can now edit the icons and titles of messages that are displayed in the activity feed for Pulse by customizing the pxFeed Pulse gadget. For example, to inform other users of an application about important Twitter updates that are related to the organization, you can create a message that displays a Twitter icon and a title of Twitter updates.

For more information, see Pulse enhancements for social collaboration.