With this new feature, Instance Administrator can export audit data filtered by user as well as filtered by site. They can also store site data for audit events.

We display some additional messages to Site and Site template Administrators when there is a Friendly URL collision between Site page and Site template page.

From now on, users can view the summary of failed staging processes, which can help them to solve the issue(s) which caused the staging process to fail.

Using LAR files for export/import in the portal are stored in DM. These LAR files can increase the size of the DM significantly. We have changed this, so the LARs are not kept in the DM after the export/import process.

On LPS-136108: URLs using a virtual host are always reformatted on export and import, even in cases where they don't need to be the validation of the Web Content was added for Liferay layout URLs. Before this, there was no validation, so users could create their customizations where they could add different URLs to the Web Content's content. After the validation was added, some custom URLs became unable to be added to the Web Content. From user perspective this was a feature loss, so we decided to deliver a feature to make customers able to add their custom URLs to Web Content's content field. This feature is about adding a configuration for storing the user’s relative URL patterns. So custom URLs containing this pattern would bypass validation.

Before the Import process starts, users are now asked via a confirmation dialog if the user is sure about deleting application data . Also, we have improved the error message for Staging related references.

As a Site Template Administrator: template propagations are run completely in the background and background tasks are executed in a sequence. The LAR from the Site Template export is cached, so different Sites can reuse it.

• LayoutSetPrototypeMergeBackgroundTaskExecutor always uses the latest Template version for the propagation.
• If there is already a queued background task for the Site, we don’t create a new one.
• If there is a background task in progress, we only create a new background task if the Template was modified.

Two new configuration options were added:

• The first one gives the users the chance to automate an existing feature, which improves performance.
• The other one is about displaying the Advanced Staging configuration screen to the users, improving usability.

This is the Staging related implementation of a bigger change. On the Staging side, the LXC Client extensions (Remote apps) could be handled. To make this feature completely working, LPS-182183: Export/Import of FrontEnd Client Extensions is also needed.

• Deletion of property upgrade.log.context.name. Now all upgrade related log lines are automatically tagged with the key upgrade.component, which provides more meaningful information.
• Upgrade Report is now compatible also with upgrade on startup, and it can be printed as Log Thread Context information.
• Upgrades log the result and the type of upgrade that has taken place after all the upgrade processes finish.
• New mBean available with upgrade on startup to obtain real time information about the status and the result of the upgrade.

Creation of a new property called upgrade.report.dl.storage.size.timeout that specifies the number of seconds that the upgrade report generation will wait for calculating the DL size before timing out. This property is set to 10 by default but it can be modified in the portal-ext.properties file.

Adds support for creating custom client extension development profiles in the same project.
For example, when the user creates a file called client-extension.dev.yaml , a new task will be available to the user called deployDev.

In order to allow developers to exclude directories from the build, a new property has been added: liferay.workspace.dir.excludes.globs= 

Kaleo Forms was already in maintenance mode. It is now being moved to deprecated, so it can be removed at the same time as DDL in about a year. This solution is being replaced by Objects, Workflow, and Form Container Fragments.

The portlets that are in the Contacts module will be deprecated.

These are:

1. Contacts Center
2. Members
3. My Contacts
4. Profile

In the first step, the modules were pushed to the maintenance mode.

These modules are obsolete ones and are no longer being used. They have been moved to deprecate and later it will be removed.

特定の行動に基づいて、より詳細な顧客セグメントを作成できるようになりました。 セグメンテーション機能を拡張し、標準的なウェブサイト活動だけでなく、カスタムイベントを含むオーディエンスのセグメンテーションが可能になりました。 ターゲットを絞った顧客グループを作成し、よりパーソナライズされた体験を提供することができます。 さらに、Liferay DXPは、カスタムイベント基準が変更されたときにアラートを提供し、セグメントの正確性と関連性を保証します。 顧客分析をより詳細に管理し、より適切なコンテンツを配信できるようになります。

オブジェクトに基づいた新しいOut-of-the-Box（OOTB）メールの通知テンプレート。 このテンプレートは、注文ステータスが「保留」に変更されると、注文作成者に自動的に送信されます。

この通知には以下の内容が含まれています:

• 注文番号

• 注文日

• アカウント名

• 配送先住所

• 注文商品の概要

• 注文合計

私たちはコマース通知を廃止し、新しい通知にはオブジェクトを使用します。

この機能では、製品仕様のカスタム選択リストを作成および管理する機能が導入されています。ユーザーは製品属性の特定の値を定義できるようになり、データの一貫性と効率が向上します。この機能には、新しい候補リストを作成したり、既存の候補リストを仕様ページに直接追加したりするオプションが含まれています。

ロールマネージャーは、ロールのUI内でオブジェクトエントリの権限を直接定義できるようになりました。新しい「オブジェクト」メインメニュー項目が 権限の定義タブに追加され、すべてのカスタム オブジェクトがリストされ、より詳細な権限の割り当てが可能になりました。