Release Notes
DXP is now certified for use with the MySQL 8.4 database version. Also applies to 2025.Q1 LTS.
Key Benefits:
Allows users to update to the latest LTS version of MySQL database. As an LTS release, MySQL 8.4 is the most stable and predictable version for production environments since it receives bug fixes and security patches for an extended period from Oracle. This longer support window reduces the need for frequent major upgrades.
Liferay DXP now allows on-demand migration of Virtual Instances across different installations, making existing environments portable and easier to manage—especially in cloud-based deployments. Whether you're moving from on-premise to Liferay SaaS, or just shifting between environments (like UAT to Production) on the same installation, this feature simplifies the process by allowing instances to be migrated, instead of the entire database.
Feature can be enabled with Beta Feature Flag: LPD-11342
With the upcoming release of Jakarta and new application server versions, Liferay is focused on becoming a full feature enterprise platform. Supporting Java 17 prevents usage of Java 21 features that will improve performance and reduce cloud costs. We are marking Java 17 for deprecation as we plan to fully focus on Java 21 in 2026.
This feature aims to enable all fields of an object to be localizable and displayed according to the user's chosen locale settings.
Key Benefits:
The localization feature will support all existing locales in the system
Custom Object entries and Modifiable System Objects entries
Localization settings are now managed at the individual field level
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:
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.
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.
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:
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.
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.
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.
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.
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.
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.
Improved Clarity and Organization: Easily access shipping information and view order summaries in a more structured, modular format.
Enhanced Efficiency: Quickly find specific order items with new search and pagination, and save time with automatic application of channel defaults.
Consistent User Experience: Enjoy a more unified and predictable interface across different order management sections, reducing confusion and improving usability.
Better Data Management: Gain more powerful tools for searching and managing your placed orders, allowing for faster problem resolution and data retrieval.
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.
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.
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.
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.
Enhanced Customization:Provides buyers with the ability to personalize products by uploading their own files.
Broader Product Offerings:Enables merchants to offer and sell products that require customer-provided assets, such as custom prints or personalized items.
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.
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.