This feature provides a way for customers to consume object validations and manage the experience for end users as they require.

Key Benefits:

• In multi-step forms, end user data can be validated in each step without persisting the data

Data from third party systems can now be managed in DXP through the use of Proxy Objects. Customers can now rely on a transversal OAuth 2 with proper SSO implementation to display data in DXP with the use of Liferay’s low code frontend application building capabilities.

Important: Because the data does not persist in Liferay’s database, some limitations are placed on proxy objects. Learn more.

Managing and synchronizing content across multiple environments just became easier and more reliable. With this release, Liferay expands the capabilities of the Batch Engine by introducing two powerful enhancements:

1. Batch Delete by External Reference Code – Users can now delete items using external reference codes instead of internal IDs, making batch deletions simpler and more consistent across environments.

2. Import Strategy Support for Deletion – When performing a batch delete, users can now define whether the operation should be partial (stop on error) or complete (continue even if some items fail), offering more control and fault tolerance during the process.

Together, these updates streamline how teams manage bulk deletions—especially in environments that rely on external identifiers or require consistent data maintenance across staging, production, and other instances.

Key Benefits:

• More reliable environment synchronization: External Reference Codes allow you to delete the same entities across different environments without depending on internal IDs, reducing risk of mismatches.

• Simplified bulk deletion workflows: Deleting large sets of data is now easier, with fewer manual steps and lower chance of errors.

• Greater control over delete operations: Choose whether the process should stop on errors or complete fully—helping teams tailor the behavior to fit their operational needs.

• Increased resilience and fault tolerance: Deletion jobs are less likely to fail entirely due to minor issues, ensuring smoother maintenance processes.

• Consistent support across entities: These enhancements are available for all entity types supported by the batch engine, making them broadly applicable across different use cases.

In order to add more flexibility to every execution in batch engine, we have added a new parameter ( batchExternalReferenceCode ) to be capable to send it to the backend without updating the ERC of the import task.

Key Benefits:

• Simplicity of execution with one parameter for each purpose.

• Add new capabilities for all entities that supports batch.

We made sure to be able to configure the most relevant SCIM providers by implementing their specifications(Microsoft Entra, Cyber Ark, etc.)

Key Benefits:

Implementing SCIM endpoints from top identity providers streamlines and secures user management by enabling automated provisioning, deprovisioning, and syncing of user data across platforms. This enhances security, ensures compliance, reduces manual work, and improves consistency and user experience. With standardized interoperability, it also future-proofs integrations and boosts operational efficiency while offering better visibility and control over identity lifecycle events

Captcha engine needs to be configurable on instance level to satisfy the multi-tenant environments' need. That has to be possible to configure them for one instance without interfering with the configuration for other instances.

Key Benefits:

Enabling CAPTCHA at the Instance level adds flexibility in configurations without affecting global settings. This supports tailored security and user experiences, and enables compliance per instance, all while retaining centralized control when needed

It’s going to be available without enabling the BETA flag, and from now it’s officially supported.

When issues happen during maintenance periods, end users saw an unbranded default maintenance page. This leaves part of the user flow unattended, with customers unable to forward users to the correct next steps. Setting up and managing maintenance pages that work when DXP is down requires technical skills that not all customers possess, making it impractical for many.

Now we allow customers to upload a maintenance page they designed, fitting their brand and instructing customers on what to do. The implementation functions indepedently from their DXP instance so, as soon as they detect a downtime, they can enable the maintenance page in their Cloud Console to be displayed for their users while they address the issue that caused the downtime.

Configuring the scaling behaviour of Liferay is not simple. Customers are required to have a deep understanding of how their application' metrics behave to set their thresholds. Since charges are also incurred depending on the hours and instances scaled, customers can feel confused on the value they are being invoiced. 

That’s why we allowed for customers to set the maximum and minimum number of scaled instances in their Cloud Console scaling page. This means non-technical customers now can control how little or how much they want to spend in scaling their application. Allowing them pinpoint precision when balancing between improved user experience with more instances, and the increase in costs associated with that.

The Liferay Developer Studio installer now includes JDK 21 as a selectable option if it’s available, simplifying the initial setup and providing a more convenient and user-friendly experience for developers wanting to use the latest Java version supported by Liferay.

This initiative focuses on developing a dedicated "Publisher Page" on the Liferay Marketplace. This page will serve as a public profile for each vendor or seller, showcasing their products, brand, and relevant information like company description, company logo and a contact us form to reach out the publisher directly.

The enhancement aims to improve the overall Marketplace experience by:

• Providing greater visibility and credibility for publishers.

• Enabling customers to make more informed purchasing decisions.

• Fostering a stronger connection between publishers and customers.

• Offering publishers a new avenue for marketing and branding.

Implement multi-currency support to enable marketplace to display product prices in various currencies.

Phase 1- publisher workflow

This feature aims to enhance user experience by allowing publisher to set the price of their apps in multiple currencies during the publisher workflow which are:

• Euro (mandatory)

• USD (mandatory)

• Rupee

• Yen

This release introduces several key improvements across the new Order Pages:

1. Dedicated Shipping Tab for Placed Orders: A new "Shipping" tab has been added to the Order Pages specifically for placed orders, providing a clear and organized view of shipping details for buyers.

2. Modular Order Summary Fragment: The existing "Order Summary" type for the InfoBox fragment has been removed and replaced with a new, more flexible "Order Summary" fragment. This allows for displaying individual fields from the order summary.

3. Enhanced Order Items Table: The Order Items listing table now features Search and Pagination capabilities, making it easier for buyers to navigate and find specific items within large orders.

4. Automated Channel Defaults Application: When a Channel Default (including Addresses, Payment/Delivery Terms, Shipping Options, Payment Options) is configured for an account, the selected default will now be automatically applied to new orders, streamlining the order creation process for buyers.

5. Advanced Placed Orders Search: You can now search by Shipping Address fields directly within the Placed Orders list, offering more granular control for buyers when locating their specific orders.

6. Renamed "Notes" Tab: The "Notes" tab in the Orders Admin UI has been renamed to "Questions & Answers" to align with the updated UI in the new Order Pages, improving consistency across the platform for administrators.

Highlight Key benefits:

1. Improved Clarity and Organization: Easily access shipping information and view order summaries in a more structured, modular format.

2. Enhanced Efficiency: Quickly find specific order items with new search and pagination, and save time with automatic application of channel defaults.

3. Consistent User Experience: Enjoy a more unified and predictable interface across different order management sections, reducing confusion and improving usability.

4. Better Data Management: Gain more powerful tools for searching and managing your placed orders, allowing for faster problem resolution and data retrieval.

5. Streamlined Workflows: Automate the application of default settings, reducing manual input and potential errors during order processing.

We've introduced a new toggle within the Channel Details section, labeled "Hide Orders List in the Account Selector".

This new setting allows you to configure whether the list of open orders is displayed or hidden from the account selector interface for a specific channel. By default, the orders list is visible, and the "Hide Orders List in the Account Selector" toggle is set to off. When activated, the open orders list will no longer appear, providing a cleaner, more streamlined view.

Highlight Key benefits:

1. Enhanced Privacy: For channels where order visibility is not desired or necessary for all users, this toggle provides an immediate way to restrict that information.

2. Improved User Experience: Reduce visual clutter in the account selector, making it easier for users to focus on relevant account information without being distracted by a potentially long list of orders.

3. Greater Flexibility: Tailor the display of each channel to better suit its specific use case and audience, offering a more customized and efficient experience.

We've introduced a brand new Upload option type for products. This option allows buyers to seamlessly upload a file directly during the purchase process.

Similar to our existing product options, the Upload option can be configured either in the Options UI or directly within the Product Options UI. Merchants also have the flexibility to mark this option as "Required", ensuring that a file upload is mandatory before a product can be purchased. Please note that this new Upload option is not eligible for SKU contribution.

In the storefront, the Upload option will appear as a disabled text input field, which will display the name of the uploaded file. Alongside this, buyers will see clear "Select" and "Clear" buttons to manage their file uploads.

Highlight Key benefits:

1. Enhanced Customization:Provides buyers with the ability to personalize products by uploading their own files.

2. Broader Product Offerings:Enables merchants to offer and sell products that require customer-provided assets, such as custom prints or personalized items.

3. Improved Buyer Workflow:Integrates file uploads directly into the purchasing flow, creating a more cohesive experience for custom orders.

This enhancement allows administrators to seamlessly duplicate an existing role along with all of its current permissions.

Similar to creating a new role from scratch, Role Duplication can be initiated directly from the Roles list. Administrators can simply select an existing role, choose Duplicate, and assign a unique name to the new role. The system then creates a fully configured duplicate, including all existing permissions, and redirects the administrator to the Role Details page for further adjustments.

Please note that only the role’s current permissions are copied at the time of duplication. If new applications are deployed later, their permissions are not automatically added to the duplicated role.

Highlight Key Benefits:

• Faster Role Setup: Quickly create new roles by reusing an existing permissions set without manual configuration.

• Consistency Across Roles: Maintain uniform permission structures across similar roles, reducing the risk of errors.

• Scalable Administration: Streamline management in large environments where many roles share similar access patterns.

This feature introduces the ability to define and manage custom address types as sub-types of the main address categories—Billing, Shipping, or Billing & Shipping—in Commerce - Account Addresses. This significantly enhances address management flexibility for B2B businesses operating across multiple locations, departments, or stakeholders.

Previously, address management was limited to only two hardcoded types: Shipping and Billing. With this release, businesses can now define additional sub-types (e.g., Ship-to Party, Sold-to Party, Ordering Address, Payer, Disti Branch Officer, DC Delivery Address) through a newly introduced Picklist-based configuration system. These sub-types are configurable and can be mapped directly under one of the three main categories.

This approach ensures compatibility with common ERP systems like SAP, which already support a range of address roles in the order-to-cash process.

This feature allows buyers to actively select their preferred currency from a list of currencies enabled by the administrator for the specific sales channel they are interacting with. Once a currency is selected, all prices will be displayed in that chosen currency throughout their shopping experience.

Changing the currency automatically creates a new order in the newly selected currency.

Crucially, this feature allows merchants to better manage their international pricing strategies (e.g. smart pricing per currency), fine tuning prices when not relying on exchange rates only.

This feature enhances flexibility and convenience for users by allowing them to easily expand their payment method options within the DXP. Users can seamlessly discover, purchase, and integrate new payment methods availbale in the Marketplace directly from the DXP, eliminating the need to navigate external platforms or seek manual solutions. This streamlined process empowers users to quickly adapt to evolving market demands and offer a wider range of payment choices to their customers, ultimately improving their overall user experience.

 
Connecting Asset Libraries to Site Templates allows content creators to validate new assets directly within a template before deploying them to live sites. This feature fills a critical gap where templates currently can’t access Asset Library assets, forcing users to create full sites just to test content. This inefficiency leads to errors and poor user experience.

Key Benefits

1. Improves Efficiency and Workflow: It saves time by letting content creators test sites and assets directly in the Site Template. This eliminates the need to create a new site for every round of testing, which is a slow and cumbersome process.

2. Enhances Data Integrity: This feature prevents the creation of orphaned reference links that occur when a template’s content pages point to Asset Libraries it can’t access. These broken links can cause unexpected behavior and data corruption.

3. Reduces UI Errors: By ensuring proper connections between templates and asset libraries, the feature mitigates UI errors that happen when editing site connections with orphaned data. This provides a more stable and reliable user interface for managing site assets.

Highlights

Site Templates can now be connected to Asset Libraries. New sites generated with a Site Template connected an Asset Library will automatically be connected that Asset Library.

Users can now download a CSV file containing the complete list of all search terms collected from a page, providing easy access for analysis and reporting

Highlights

1. New export feature: Users can now download a CSV file with all search terms collected from a page.

2. Easier analysis and reporting: The export enables deeper analysis and custom reporting outside the platform.

3. Enhancement to previous update: Builds on the improvement from LPD-26181, which made all search terms visible in the Search Terms card.

To reduce confusion and improve transparency for SaaS customers, we’re updating the Analytics Cloud usage limits page. SaaS users will now be redirected to the Customer Portal when they access the Usage Limits menu in AC. This ensures they see the correct consumption metrics associated with their plan: Anonymous Page Views (APVs) and Monthly Active Logged-In Users (MALUs) as previously, the usage page displayed default limits based on Page Views (PVs) and Known Individuals (KIs), which do not apply to SaaS customers.

Highlights

1. Redirect for SaaS users: SaaS customers are now redirected to the Customer Portal when accessing the "Usage Limits" page in AC.

2. Accurate metric display: Customers will see the correct usage metrics—APVs and MALUs—instead of outdated PVs and KIs.

3. Eliminates confusion: Removes misleading limits that previously appeared for SaaS users.

To prevent token duplication in lower-level environments, we’re introducing a new portal property. When set to true in the portal-ext.properties file, this property will automatically clear the AC connection on startup. This ensures that if the production token is copied to a UAT environment during migration, it will be removed on startup—preventing data contamination, eliminating the need for manual disconnection, and preserving the integrity of the AC connection in production.

Highlights

1. Prevents data contamination between environments

2. Eliminates the need for manual disconnection

3. Preserves production data integrity

Analytics Cloud Cookie Control (LPD-10588)

Utility page for cookie policy lists and describes all cookies in use. Users can add and update cookies in the list with the cookie object. When the cookie manager is enabled, Analytics Cloud only tracks data from users who consent to statistics cookies.

This feature introduces customizable permissions for the "Owner" role and other user roles within Publications, allowing administrators to define exactly who can publish, edit, invite users, or manage permissions at the publication level. A new "Permissions" section has been added to the "Enable Publication" settings, along with an "Edit Permissions" button that opens the Publication permissions modal. Admins can now revoke the "Publish on Production" permission for any user on a publication-by-publication basis. Once revoked, the change is reflected immediately, the user will no longer be able to publish content to production, and the revoked status is saved and visible in the publication permissions settings. Only users with the Admin role or the specific permission to manage publication roles can make these changes. This enhancement provides granular control over user capabilities within each publication, helping teams better manage their content workflows and avoid accidental publishing.
 

Key benefits:

• Safeguard Production Changes: Blocks users from publishing or modifying production content via Publications unless explicitly granted.

• Enhanced Role Governance: Admins now have complete oversight of publication-level permissions for all user roles, including Owners.

A new warning has been added to the Publications configuration screen to alert admins when "Sandbox Only" mode is enabled but publication Owners still have permission to publish. In this scenario, any user who creates a sandbox publication can still push changes to production, potentially bypassing the intended protection. The system now displays a warning message when this configuration is detected, guiding admins to review and adjust permissions for the Owner role accordingly.
 

Key benefits:

• Prevent accidental publishing by alerting admins when Owner permissions still allow publishing in Sandbox mode.

• Increase visibility into role-based permissions that may unintentionally allow production changes.

We enabled navigation menus to be retrieved using their External Reference Code (ERC) through Liferay’s headless APIs. This enhancement enables a more precise and consistent identification of navigation menus across sites and environments, particularly useful in multi-site and content migration contexts. It complements the existing functionality by providing an alternative for IDs.
 

Key benefits:

• Improved data consistency: ERC-based retrieval ensures references remain valid across environments.

• Easier data migration: ERCs streamline the export/import process across different Liferay sites by providing a consistent identifier.

• Better filtering options: Admins can now export navigation menus based on creation or modification date range, giving finer control over headless operations.

As customers increasingly adopt HTML5 for content creation, there's a growing need to upgrade the current rich text editing capabilities and CKEditor 5 has been selected as the default editor for Liferay DXP to meet this demand. CK Editor 5 has been made available in DXP under Beta Feature Flag. (FF-11235):

• Web Content Description field

• Page Builder:

  • Paragraph

  • Forms → Rich Text

To help users build pages faster with more design options, Liferay now allows direct access to Marketplace fragments from within the page builder. In addition to native and already-installed fragments, users can now browse and install additional fragments available on the Marketplace—expanding their library without leaving the editor.

This gives customers the ability to use pre-built fragments shared by Liferay, technology partners, and the broader community, making it easier to create flexible, high-quality pages with less effort.

Users can translate text fields from Objects when using Text Input Fragments in Form Containers.

Dynamically show or hide configuration fields in a custom fragment based on user input values.

With the introduction of the new CMS approach for managing object entries, the existing 1:1 nested object entry functionality in the Page Builder (LPD-20213) is now deprecated and will be removed. This feature has proven to be complex and underutilized by end-users.

The new approach, being developed under the CMS 2.0 initiative, will offer a more intuitive user experience for object relationships, allowing users to configure child structures as repeatable or non-repeatable.

The new Side Panel (also known as Info Panel) is a reusable Clay React component that provides a consistent, accessible, and responsive sliding panel for use across Liferay applications. It supports common use cases such as content editing, navigation, and contextual information display.
 

Key benefits:

• We established a uniform look and feel across all instances of the Side Panel, reducing cognitive load and improving usability and also ensured compliance with accessibility standards (e.g. keyboard navigation, ARIA roles), enabling inclusive design by default.

• Reduces redundant implementations and streamlines maintenance by offering a centralised, reusable component.

• Reinforces design consistency and reusability across the product ecosystem.

The addition of new translations and locales ensures that users in Myanmar, Bosnia & Herzegovina, Ireland and Serbia can interact with the platform in their preferred languages or regional variation.

Key benefits:

• Tailors the user experience for specific markets and regions, improving relevance and usability

• We made the platform more inclusive by expanding language and locale options.

The Accessibility Checker Component is being deprecated as part of our effort to improve accessibility tooling and simplify our component library. After evaluating its usage and overlap with other accessibility solutions in Liferay, we found it to be redundant and we stopped using it long time ago.

By displaying the blueprint's results in a Collection Display fragment (available since DXP 7.4 U88 as Beta), you can leverage search to return your assets dynamically, and reap the benefits of the fragments toolbox to lay out the page.

Enhanced Type Support

Now, the Blueprint Collection Provider supports asset types (like structured web content and Objects) allowing to map specific item fields beyond the the basic information fields (i.e., asset entry fields) in fragments, depending on the Searchable Types settings of your blueprint.

 
When selecting Web Content Article as Searchable Types, the subtype selector becomes available

 
Selecting an available Web Content Structure (Subtype) as Searchable Types in a blueprint

 
Web Content Article with a specific Web Content Structure selected as subtype in a blueprint

 
Mapping a Web Content Structure field from a Blueprint Collection Provider with a specific return type in a fragment

 
Web Content Article with no subtype restriction selected as Searchable Type in a Blueprint

 
Mapping Web Content Article field from a Blueprint Collection Provider with a specific return type in a fragment

 
Document with a specific subtype (Document Type) is selected as Searchable Types in a blueprint

 
Mapping Document Type fields from a Blueprint Collection Provider with a specific return type in a fragment

 
Object type selected as Searchable Types in a blueprint

 
Mapping Object fields from a Blueprint Collection Provider with specific return type in a fragment

 
Message Boards Message selected as Searchable Types in a blueprint

 
Mapping basic information fields from a Blueprint Collection Provider with return type Asset in a fragment

Opt-in Collection Provider

Configure if a collection provider should be published when creating a new blueprint, or later via the Configuration tab or through the action menu in the table view in Blueprints.

Enabling a blueprint as a Collection Provider on creation

 
Enabling/disabling a blueprint as a Collection Provider via Configuration later

Enable blueprint as a collection provide via the action menu in the Blueprints admin

Benefits

• Access and map type specific item fields fields in fragments for an extend range of types including Web Content Article and structures, Documents and Document Types and Objects.

• Limit searches to specific subtypes via Query Settings in Blueprints

Description

• Embedded items now include actions (when the headless entity supports)

• Filter by Workflow Status via the filter request parameter.

  • Filter field: status

  • Examples: status eq 0, status eq 0 or status eq 2

Benefits

• Invoke available actions on the returned items

• Filter results by workflow status

Liferay Self-Hosted deployments can update their Elastic stack to this version. For Liferay PaaS projects a new Elasticsearch image will be provided under Liferay Cloud’s Docker Hub account.

Deployments can operate their stack using the latest available, secure and stable version of OpenSearch 2.

Requires to install Liferay Connector to OpenSearch 2.

Liferay Tomcat Bundles and Docker Images ship with Elasticsearch 8.18 as the sidecar search engine.

Benefits

The Elasticsearch server runtime included in Liferay DXP Tomcat Bundles and Docker Images (aka. Sidecar Elasticsearch, located under [Liferay-Home]/elasticsearch-sidecar) is provided as a convenience for local development and testing only. It is neither suitable nor supported for production.

Instead, configure Liferay to connect to Elasticsearch as a self-managed, standalone server or cluster of server nodes.