Platform '24.1 release notes

New client-managed deployments of Pega Platform require the Search and Reporting Service (SRS) and external Kafka to run, and clients that use earlier releases must first externalize these services before updating. New client-managed deployments of Pega Customer Decision Hub™ and Pega Process AI™ require external Cassandra, and clients that use earlier releases must first externalize Cassandra before updating.

For more information, see Externalization of services in your deployment.

Because some earlier Application Server versions do not support Java 17, these Application Servers are also no longer supported in Pega Platform '24.2. For a full list of Application Servers that are no longer supported, refer to the Application Servers section of the Platform Support Guide.

For more information, see the Platform Support Guide and the Pega Platform technology support roadmap.

When you create a new Case Type, the system automatically creates a table-based Insight, which you can then use as a landing page in your Portal. This improvement enables you to showcase significant data from your application more conveniently. For example, you can enhance the visibility of a sales-related Insight in your application, making it more accessible to the audience.

The autogenerated Insight features Primary Fields only, which you can define to match your business requirements.

For more information, see Configuring Primary Fields.

The following figure shows a sample table-based Insight for sales, which has been automatically generated with a Case Type.

Note: The autogenerated Insights do not have any data unless you run the Case Type. In this example, the Case Type includes three Cases.

The figure includes:

1. Table-based Insight with Cases.
2. Primary fields.
3. List of landing pages.

For more information about Portals and landing pages, see Organizing the main navigation for a standard work Portal and Pages for applications.

For example, you can set a human resources-related Insight as a landing page, and then easily add new data objects, such as a new employee's data, straight from the Portal. In this way, you save time and gain the opportunity to manage application data more conveniently.

For more information, see Adding Insights to your application.

The following video shows how adding a data object works at run time. In this example, a new record with John Doe's data is added to the human resources-related Insight.

Pega Platform release '24.2 extends the scope of actions that you can perform in table-based Insights that are contained within Cases. Now, you can create Case instances, edit and reorder rows, and perform custom bulk actions in table-based Insights when viewing a Case in your application. With this enhancement, users save time and can conveniently tailor Insights to match specific business requirements.

The following video shows a Case with a table-based Insight that contains orders for furniture. In this example, a bulk edit has been performed on five East India Wood Rectangular Table records, changing each to American Wood Rectangular Table. With this functionality, you can maintain consistency and save a significant amount of time.

You can now apply a separate, stricter Content Security Policy (CSP) rule for Constellation UI Portals when configuring a Constellation application. Previously, all UI Portals for Constellation applications used the same CSP rule. The new CSP rule adds the following two options to the Script-Source and Style-Source directives (these options are cleared by default for both updates and new installs):

• Nonce (Number used once): Generates a new random 128-bit character identifier on every page load or reload. Only scripts with the matching nonce will be run. Select Nonce to protect your resource from inline attacks. Using Nonce eliminates the need to add the hash sources to the Style-Source directive to achieve the same protection. For strict compliance, select Nonce for both Script-Source and Style-Source directives of Constellation UI Portals. Nonce applies to Constellation UI Portals only. It is not used by traditional UI Portals, even if you select it.
• Blob (Binary Large Object): Enables you to restrict the matching of data inline resources to those defined using the Blob data type. If you select the Data option, it automatically includes Blob data types (and filesystem and mediastream data types), even if the Blob checkbox is not selected. You can select Blob only, instead of Data, to allow only Blob data types. As a best practice, select Blob for the Script-Source directive of Constellation UI Portals. Blob can be used by both traditional and Constellation UI Portals.

The following UI updates were made in Dev Studio:

Security tab of the Application Definition:

On the Security tab of Constellation UI applications, the Content security section has been renamed to Content security policy. The section displays the mode options (Reject and Report or Report only) by UI Portal (traditional and Constellation). Previously, you could not apply a separate content security policy to each UI Portal. Helper text has been added that describes each Portal type.

Policy Definition tab of Records > Security > Content Security Policy:

On the Policy Definition tab, checkboxes for Nonce and Blob are displayed in the Script-Source and Style-Source sections. Both checkboxes are cleared by default for all Portal types and for both updates and new installs.

For information about CSP settings for Constellation UI Portals, see CSP settings in Constellation.