Now, developers will be able to filter Custom Object Entries using the field values of the related elements for a given Object entry.

It is possible to filter as many levels as needed. The format of the filter query needs to be: relationshipName1[/relationshipName(i)]*/fieldNameN. Being relationshipName1, relationshipName(i), etc the different relationship names that join Object 1 with Object i, and fieldNameN being the name of the field of the latest Object definition on which the user wants to filter.

In addition to this, our nesting capabilities have been enhanced, so now it is possible to retrieve data for an Object entry and its related elements, supporting several levels of nesting.

The names of the different relationships to retrieve need to be specified in the nestedFields parameter, separated by commas. Additionally, the nestedFieldsDepth parameter with the number of levels to retrieve needs to be specified in order to indicate to Liferay how many levels it is necessary to nest.

Now users can manage the tags and categories associated with the Objects entries from the REST APIs. When an Object has Categorization enabled, properties for tags and categories will be exposed in the Object entries schemas. Users can retrieve the information, set or update the tags and categories associated with the Object entries as well as use the information of these fields to filter information

Now it is possible to manage and check the permissions of the object entries directly from the headless APIs.

For each object definition, two new endpoints are available. One to retrieve the permissions that apply to that individual Object entry and another one that allows users to set/update the permissions that apply to that entry.

Now it is possible to use all query parameters available from the API explorer. Parameters such as fields, nestedFields or flatten are accessible and ready to use in your test queries.

The instance administrator can create email templates including the first name.

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.

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.

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= 

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

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

アップグレードプロセスによって ctColectionId 列を考慮しない場合があり、特に古いバージョンのパブリケーションを使用しているお客様に不整合が発生する可能性があります。

標準の rest-config.yaml にchangeTrackingEnabledを追加して、サービスがパブリケーションのサポートを指定しなければならないようにしました。これにより、将来のヘッドレスAPIで変更追跡を可能にするプロセスが簡素化されます。

オブジェクト間の1対1の関係によりワークフローを合理化する新機能を導入しました。ユーザーは、プライマリオブジェクトのCRUDビューから直接ネストされたオブジェクトを作成および更新できるようになり、データ セットマネージャー (DSM) から変換されたシームレスな削除および表示操作を利用できるようになりました。このアップデートにより、データ管理がよりスムーズかつ効率的になりました。

Elasticsearch 8.15.x がテストされ、対応するLiferayのバージョンとの互換性マトリックスに追加されました。

注意: Elasticsearchの新しいマイナーバージョンとの互換性は、2つの方法でテストされています:

1. 最新-最新: 最新の利用可能な Elasticsearchのマイナーバージョンを使用して、最新のLiferayバージョンをテスト → 例: Master/2024.Q3 + Elasticsearch 8.15

2. ミニマム-最新: Elasticsearch 8の互換性が最初に利用可能になったミニマムのLiferayバージョンを、Elasticsearchの最新のマイナーバージョンでテスト → DXP 7.4 U81/DXP 7.3 U31 + Elasticsearch 8.15

このようにすることで、Liferayはより広範なデプロイメントのベースが最新の検索エンジンバージョンでスタックを運用できるようになります。

Elasticsearchは通常、およそ 2 か月ごとに新しいマイナー バージョンをリリースするため、これは定期的なプロセスであり、四半期ごとに計画されたアクティビティです。

Elastic’s product lifecycle に従い、Elasticsearch 7.17.xバージョンはElasticsearchバージョン9がリリースされるまでサポートおよび保守されます。 Elasticsearch 9.0.0は、2025年初頭にリリースされる予定です。

したがって、Liferayでは、7.17.x をデプロイメントしているすべてのお客様に対し、互換性のある最新の Elasticsearch 8.x バージョンへのアップグレードプロジェクトの計画段階を開始することを強くお勧めします。

Elasticsearch 8との互換性は7.4 U81+で利用可能です。→ Operating Liferay 7.4 GA/Update 81+ with Elasticsearch 8 - Liferay

注意: Elasticsearch 8.x との互換性は、バンドルされている Elasticsearch 7 コネクタと Elasticsearch 8 の REST API Compatibility によって提供されます。

Liferayには、クライアントバージョンとして7.17.21を使用し、また開発・テスト用にSidecar ElasticsearchサーバーのバージョンとしてアップデートされたElasticsearchコネクターが同梱されています。

データセットマネージャーでは、配列ストラクチャをマップできるようになりました。これにより、データ セットの特定のセルに値のリストを表示できます。例えば、ユーザーのロールや製品のタグをリストできます。

ユーザーがフロントエンドデータセットに直面している場合、アイテムはデータ セットマネージャーで設定されたユーザーと対話するためのアクションを表示できます。今後は、ユーザーがアイテムまたは作成アクションを通じて宛先URL に移動すると、現在のURLが宛先ページに追加されるため、ユーザーはアクションをシームレスに実行した後にデータ セットに戻ることができます。

大文字で始まる候補リストを作成できるようになりました。 重要な特徴の1つは、ユーザーがアクティブと非アクティブの値でフィルタリングできるようになったことです。

機能ステータスの変更

個々の仕様をマッピングし、順序を選択し、販売を促進し、顧客体験を向上させる明確で有益な製品ページを作成します。  この新機能で商品ページの作成を簡素化し、ビジネスに力を与えましょう。

機能ステータスの変更

機能ステータスの変更

Java JDK 17 および 21 Runtimeの新しいサポートにより、Java 11 は2024.Q3以降のDXP ランタイムではサポートされなくなります。

Liferay Workspaceは、JDK 17 または 21でのカスタムモジュールの再コンパイルのサポートを提供します。

Commerce Classicは、Liferay Classicテーマをベースにした新しいSite Initializerです。

注文ページは、フラグメント注文用の表示ページテンプレートを使用して再設計されており、全体的に柔軟性とカスタマイズオプションが向上しています。 これにより、よりダイナミックでパーソナライズされた注文のエクスペリエンスが可能になります。

新しい注文ページでは、ユーザーが注文ページから直接配送と支払いオプションを選択できるようになりました。必要な情報がすべて入力されると、ユーザーはワンクリックで素早くチェックアウトでき、購入プロセスが合理化されます。

The Liferay Marketplace has undergone a significant architectural enhancement with the formalization and enforcement of Liferay Catalogs. This structure clearly categorizes all Liferay-developed applications, providing explicit transparency on support levels, update schedules, and intended usage.

All Liferay-published applications are now distributed under three dedicated, high-level catalogs:

1. Liferay Inc.: Contains all fully supported, production-ready applications, including crucial productivity tools, security utilities, connectors, and Experience Management features. These apps follow a strict qcial hub for all new, experimental technologies and potential future core features. Apps in this catalog are not officially supported and are intended for testing and feedback purposes only.

2. Liferay Community: Hosts officially deprecated applications that remain available for backward compatibility, as well as applications contributed and offered under open-source licenses. These apps receive support until their latest compatible DXP version and follow a quarterly maintenance schedule.

Key Benefits:

• Targeted Discovery: Efficiently filter the Marketplace to find specific types of applications, such as mission-critical integration connectors (Liferay Inc.) or bleeding-edge experimental features (Liferay Labs).

• Predictable Updates: Rely on the consistent quarterly update schedule for all fully supported (Liferay Inc.) and Community-maintained applications.

A new set of fragments has been introduced under a dedicated category called “Account Selector.”.

These fragments allow to compose and customize the account selector according to their specific business needs.

Here is a list of the newly added fragments for building the account selector:

• Account Selector: this fragment is the main orchestrator of the entire component, handles the communication with external components, the dropdown mechanism and the panels (up to 5 can be configured), and manages the main drop zone areas

• Account Selector Button: OOTB available Account Selector call-to-action

  (preserves the current logic for page/component refreshes), used to open/close the account selector (any custom button hooked up with the Javascript business logic can be used).

• Account Selector Panel: this fragment can be drag-and-dropped inside the Account Selector’s panel drop zone (each panel is a tab that can be navigated in the dropdown) and creates a drop zone to place account-related views

• Accounts Data Set: Data Set fragment to display the list of selectable accounts for the current user

• Create Account Button: configurable call-to-action that allows the creation of new accounts, maintaining the existing Account Selector flow.

• Account Orders Data Set: Data Set fragment to display the list of selectable orders for the current account

• Create Order Button: configurable call-to-action that allows the creation of new orders, maintaining the existing Account Selector flow.

A fully configured Account Selector is also available out-of-the-box (OOTB) in the Commerce Classic Site Initializer (LPD-20379).

Key Benefits:

• Flexible Customization: Easily tailor the account selector to match your site’s structure and user needs.

• Improved User Experience: Enables intuitive navigation and personalization of account-related views.

• Configurable Control: Enable or disable specific features and interactions without custom development.

The new Configurable Order Scoping feature gives administrators more control over how orders are displayed on the site. Two new configuration settings have been added within each Channel:

• Open Orders Visibility Scope

• Placed Orders Visibility Scope

Each configuration offers two visibility options:

• Account (default): Maintains the existing behavior, where users can see all open or placed orders across all accounts they have access to, regardless of who created the order.

• User: Limits visibility so users only see orders they personally created for the accounts they are part of.

In addition, a new permission—“View Organization Orders”—has been introduced under Orders. This permission ensures that Sales Agents can continue to view all orders associated with their accounts, regardless of the scoping configuration. The permission is automatically assigned to the Sales Agent role by default.

Key Benefits:

• Flexible visibility control: Administrators can configure order visibility according to organizational or role-based needs.

• Improved data privacy: Restrict order visibility to the creator when required.

• Backward compatibility: Default setting preserves existing system behavior to avoid workflow disruption.

• Enhanced role management: The new “View Organization Orders” permission ensures key roles, such as Sales Agents, retain appropriate visibility.

The Manage Product Availability at Scale feature empowers catalog managers to efficiently manage individual products through multiple configuration pages containing all catalog’s products. With tools for manual configuration, eligibility-based visibility, and some bulk editing, this feature ensures streamlined operations and enhanced control over product offerings.

The Account Selector Customization feature has moved from BETA to RELEASE.

See also Composable Account Selector in the New Features section.

With Liferay's New Headless Content Management System (CMS), creating, organizing, and publishing content is simpler because all content management tasks are brought together in a single interface. Your content is independent of its presentation, allowing you to reuse it across sites, pages, and APIs.

You can work with articles, documents, media, and more, while taking advantage of features like global asset views, organized spaces, and cross-site publishing. Thanks to Liferay Objects, the CMS provides flexible content structures and ensures a smooth, consistent authoring and publishing experience.

Key Benefits:

• Enhanced Efficiency and Governance: Achieve immediate content visibility and streamlined collaboration by centralizing assets into a single, unified view. Rigorous versioning and workflow controls ensure consistent content quality and compliance across the organization.

• Maximum Agility and Portability: Leverage a modern headless-first, API-driven architecture (REST/GraphQL) that makes content fully portable, ensuring instant readiness for distribution and maximum reach across all your digital channels.

• Measurable Performance and Data-Driven Strategy: Empower content owners with embedded analytics and strong preview capabilities, enabling teams to make instant, informed decisions that drive superior business outcomes.

This epic delivers a comprehensive solution for exporting and importing vocabularies and categories with associated data across Liferay environments, tackling potential roadblocks to ensure a smooth and efficient migration process.

Key Benefits:

• Achieve True Content Portability: Facilitate the easy and standardized movement of content architecture (vocabularies/categories) between different instances, crucial for multi-site rollouts.

• Accelerate Deployment Pipelines: Ensure fast, reliable, and repeatable promotion of entire content structures between environments, maintaining configuration consistency with minimal manual effort.

• Enable Bulk Management & Setup: Quickly bootstrap new environments with pre-defined taxonomies and enable efficient, large-scale bulk editing of existing category metadata via the export-modify-import cycle.

This epic delivers a comprehensive solution for exporting and importing tags with associated data across Liferay environments, tackling potential roadblocks to ensure a smooth and efficient migration process.

Key Benefits:

• Achieve True Content Portability: Facilitate the easy and standardized movement of content architecture between different instances, crucial for multi-site rollouts.

• Accelerate Deployment Pipelines: Ensure fast, reliable, and repeatable promotion of entire content structures between environments, maintaining configuration consistency with minimal manual effort.

This feature introduces “Lazy References” to ensure import success regardless of deployment order. If an imported item references a missing Vocabulary or Category, the system creates a temporary “incomplete” dummy object. This special status allows the main content import to succeed immediately. The project’s focus is managing the status lifecycle to allow a smooth transition of these incomplete dummies to a fully approved state when the complete taxonomy object is imported later.

Key Benefits:

• Order-Agnostic Deployment: Guarantees successful imports by decoupling content from its taxonomy dependencies, allowing content and categories to be deployed in any sequence.

• High Success Rate: Prevents import batch failures by automatically creating placeholders, isolating cleanup and ensuring that core content is immediately available.

The Analytics Cloud Synchronized User Deletion feature (LPD-45375) has been promoted to General Availability (GA), and its corresponding feature flag has been removed.

This update ensures consistency across platforms by allowing users to synchronously delete users from DXP, with those deletions being immediately reflected in Analytics Cloud.

The Static Segments feature has been formally deprecated and removed from Analytics Cloud. The feature has been under a "deprecation" feature flag for several quarters, and the retirement process is now complete.