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= 

This feature introduces the ability to create and manage custom picklists for product specifications. Users can now define specific values for product attributes, improving data consistency and efficiency. The feature includes the option to create new picklists or add existing ones directly on the specification page.

Roles Managers can now define permissions for Object entries directly within the Roles UI. A new “Objects” main menu item has been added to the Define Permissions tab, listing all Custom Objects, allowing easier granular permission assignment.

Some upgrade processes may not consider the ctColectionId column which may generate inconsistencies for customers using Publications, especially for older versions.

Add changeTrackingEnabled to the standard rest-config.yaml so that services must specify Publications support. This will simplify the process of enabling change tracking for future Headless APIs.

We introduced a new feature to streamline workflows with 1:1 relationships between objects! Now, users can create and update nested objects directly from the primary object's CRUD views, and enjoy seamless delete and view operations translated from the Data Set Manager (DSM). This update makes managing data smoother and more efficient.

Elasticsearch 8.15.x has been tested and added to the compatibility matrix to the corresponding Liferay versions.

Note: Compatibility with newer Elasticsearch minor versions is tested in two ways:

1. Latest-Latest: Testing the latest Liferay version with the latest available minor version of Elasticsearch → e.g. Master/2024.Q3 + Elasticsearch 8.15

2. Minimum-Latest: Testing the minimum Liferay version where Elasticsearch 8 compatibility was first made available with the latest minor version of Elasticsearch → DXP 7.4 U81/DXP 7.3 U31 + Elasticsearch 8.15

This way Liferay can allow a broader deployment base to operate their stack with an up-to-date search engine version.

As Elasticsearch is usually releases a new Minor version roughly every two months, this is a recurring process and a planed activity in each quarter.

Per Elastic’s product lifecycle, Elasticsearch 7.17.x versions are supported and maintained until Elasticsearch version 9 is released. While Elastic does not provide specific release dates for future releases, for Elasticsearch 9.0.0, the new release is anticipated in early calendar year 2025.

Therefore, Liferay strongly recommends all customers with 7.17.x deployments to begin the planning phase for an upgrade project to the latest compatible Elasticsearch 8.x version.

Compatibility with Elasticsearch 8 is available on 7.4 U81+. → Operating Liferay 7.4 GA/Update 81+ with Elasticsearch 8 - Liferay

Note: The Elasticsearch 8.x compatibility is provided through the bundled Elasticsearch 7 connector and the REST API Compatibility of Elasticsearch 8.

Liferay ships with an updated Elasticsearch connector using 7.17.21 as the client version and also as version of Sidecar Elasticsearch server for development and testing purposes.

Data Set Manager lets from now to map Array structures, so a given cell of a Data Set can show list of values, for example to list the roles of a user or the tags of a product.

When the users are facing a Frontend Data Set the items can show actions to interact with them that are set in the Data Set Manager. From now own, when the user navigates to a destination URL through an item or creation action, the current URL is added to the destination page, so the user can return to the Data Set after performing the action seamlessly.

Users can now create picklists beginning with capital letters. One key feature is that now users will be able to filter by Active and Inactive values.

Feature Status Change

Map individual specifications, choose the order, and create clear, informative product pages that drive sales and enhance the customer experience.  Simplify product page creation and empower your business with this new feature.

Feature Status Change

Feature Status Change

With the new support of Java JDK 17 and 21 runtimes, Java 11 will no longer be supported for DXP runtime on 2024.Q3 or later.

Liferay Workspace offers support for re-compiling custom modules on JDK 17 or 21.

Commerce Classic is a new Site Initializer based on the Liferay Classic theme.

The order pages have been redesigned using a Display Page Template for the Order with Fragments, overall offering greater flexibility and customization options. This allows for more dynamic and personalized order experiences.

The new Order Pages now enables the users to select shipping and payment options directly from the order page. Once all required information is filled in, users can quickly checkout with a single click, streamlining the purchasing process.

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.