Feature Status Change
The Liferay Theme tasks are being deprecated and they will be removed in the future. The feature is based in Gulp 4 which is also deprecated. Customers are encouraged to use third party tooling to substitute it.
Release Notes
Feature Status Change
The AMD Loader are being deprecated and they will be removed in the future. Liferay DXP officially supports ESM, which is the official standardized module system for JavaScript, while AMD was a third-party solution.
By adopting ESM, products align with the language's native capabilities and future direction. Modern browsers now natively support ESM, allowing for direct use without transpilation or additional loaders. This can lead to reduced bundle sizes, faster initial page loads and simplified development workflows. This will imply also the deprecation of Liferay-CLI.
Feature Status Change
The Walkthrough is being deprecated and it will be removed in the future. Liferay will investigate new ways to offer this functionality.
Feature Status Change
The Liferay Talend Components feature is being deprecated and will be removed in the future.
Feature Status Change
Enabling this feature will allow users to work with base64 format in object attachments fields.
Feature Status Change
The functionality for sharing widgets is being deprecated and it will be removed in the future. The feature has been deemed obsolete.
Feature Status Change
The functionality for Supported Clients for widgets is being deprecated and it will be removed in the future. The feature has been deemed obsolete.
Feature Status Change
The functionality for Most Viewed Assets Collection Providers is being deprecated and it will be removed in the future in light of more advanced Analytics Cloud content tracking.
Feature Status Change
Scope of the widgets in a page: Page, Site or Global is being deprecated and it will be removed in the future.
Feature Status Change
The "Featured Content" contributed fragment set is being deprecated and it will be removed in the future.
Feature Status Change
The widget pages are going into maintenance.
Feature Status Change
The Asset Publisher widget is going into maintenance.
Feature Status Change
Users can easily identify components that may cause performance issues in their Pages. We have added a new tab on the Page Audit to show the users the back-end render times of the different components, as well as warnings to help identify specific components configurations that may lead to performance issues. Those warnings also appear on the Edit mode, so the user is aware of possible issues during the page creation.
The AI Assistant is a versatile and powerful tool designed specifically for content creators to enhance their productivity and streamline workflows. By centralizing AI-driven content creation into a single, easy-to-use application, the AI Assistant simplifies the process of generating and managing diverse types of content. Whether you're working on blogs, Knowledge Base articles, or page layouts, the AI Assistant offers the tools and flexibility to help you work smarter and faster—all in one place.
Availability: The AI Assistant is a cloud-based application readily accessible on the Marketplace, making it easy to integrate into your existing digital ecosystem. Its cloud infrastructure ensures reliable performance and scalability, providing users with consistent and seamless access to its capabilities.
Due to the upcoming migration to Jakarta EE, we are deprecating all the current versions of our application servers to prepare for the release of the new versions that are Jakarta EE 10 compatible. This is a breaking change and so new app server versions will replace the old versions.
Deprecated:
Apache Tomcat 9
Wildfly 26.1
Jboss EAP 7.4
Weblogic 14
In 2025.Q3 we are adding support for the following application servers:
Apache Tomcat 10.1
Wildfly 30
Jboss EAP 8.0
Weblogic 15 (Pending release from Oracle)
When filtering a set of items on a Data Set, sometimes we will be interested in filtering for a field that is part of a relationship.
With this new capability, we enable users to choose to filter by children of complex objects.
The Centralized Products Eligibility and Configuration Management 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. Additionally, it enables faster and smarter management of product eligibility for channels, order types and accounts.
Key benefits:
1. Improved Catalog Management Efficiency:
Simplified product configuration editing via a centralized, flat table view.
Streamlined workflows for managing product attributes like visibility, minimum/maximum quantities, eligibility and much more.
Avoid duplicating products to manage specific configurations by modifying targeted configurations instead.
Perform batch updates on visibility, eligibility, and other product attributes for multiple products, whilst inheriting base setting from the Master catalog configuration
Leverage pre-filled default master configurations to ensure consistency and simplify product setup when adding new products in a catalog.
2. Enhanced Control over Product Eligibility and Visibility:
Define and manage eligibility rules tailored to specific customer groups, channels, and accounts
Quickly adjust product availability and settings for various markets and segments (e.g. B2B vs B2C).
Streamline the management of seasonal items or time-sensitive offerings using configuration scheduling.
Release Flag (opt-in)
This release introduces a new Multishipping feature to the storefront, allowing customers to ship parts the same order to multiple addresses with a single checkout. Whether customers are sending gifts to different recipients or shipping products to various locations, the Multishipping feature offers a seamless and flexible shopping experience.
Administrators can allow multishipping in their site through a new configuration in the site’s Channel details page. The customers can access a new “Multishipping” tab in the Open Order Details page to easily manage the Delivery Groups and customize the quantity of each order item for every Delivery Group for the order before the checkout.
Please note that this feature is available through the existing “Commerce Classic Site Initializer” Beta feature flag. To enable it, open the Applications Menu → Control Panel → Instance Settings → Feature Flags → Beta.
Key benefits:
1. Easy to Setup: Multishipping can be activated for your site by enabling “Allow Multishipping” in your site’s Channel Details page.
2. Flexible Address and Delivery Management: Customers can easily set different shipping addresses or different delivery dates for the same address in the context of the same order.
Enhance the user experience by allowing users to directly provision cloud applications from marketplace platform, simplifying application deployment.
Key benefits:
1. Streamlining Application Provisioning: Enable users to provision cloud applications directly from the Marketplace platform, eliminating the need for complex manual processes and without leaving the platform.
2. Intuitive User Interface: Provide an easy-to-use interface for installing and uninstalling cloud applications directly from the marketplace, including an intuitive form for inputting necessary information.
3. Efficient License Management: Offer a clear and intuitive interface for managing application licenses, ensuring compliance and optimizing resource utilization.
Release Flag (opt-in)
This feature allows warehouse managers to define granular eligibility rules for accounts and account groups to access specific warehouses. This enables fine-grained control over which customers can see and purchase inventory from which warehouses.
Key benefits:
1. Improved Inventory Management:
Prevent unauthorized access to inventory data.
Strategically control product visibility based on inventory quantities and stock levels.
Optimize inventory allocation across customer segments.
2. Enhanced Customer Experience:
Provide a more relevant and personalized shopping experience.
Improve customer satisfaction by prioritizing access for key customer segments.
3. Increased Revenue:
Generate higher revenue from valuable customer segments by prioritizing their access to inventory.
4. Reduced Lost Sales:
Minimize lost sales due to stockouts by limiting product visibility for certain customer groups.
Generally Available (aka OOTB)
Added External Reference Codes for references in widget configurations in Commerce and User Management applications. This helps promote data integrity when pages and their widgets are migrated across environments.
Key benefits:
References within the following page widgets now use External Reference Codes instead of internal IDs:
Cart
Cart Summary
Category Content
Commerce Addresses
Commerce Category Navigation
Mini Cart
Open Carts
Option Facet
Order Forecasts Chart
Organization Management
Placed Orders
Product Comparison Bar
Product Comparison Table
Product Details
Product Downloads
Product Publisher
Search Results(Commerce)
Specification Facet
Generally Available (aka OOTB)
Introducing new key improvements to the B2B Guest Checkout experience, enhancing the overall user journey and providing greater flexibility for both new and returning customers.
Guests now have the option to sign in or sign up during the checkout process, directly from the mini-cart. Once logged in, users can either select an existing account or create a new one, ensuring that they can move through the purchase flow smoothly without disruptions. Upon setting the account, guests, now logged-in users, will be redirected to the checkout, making the transition to completing the purchase seamless.
Additionally, if a guest decides to sign in without necessarily checking out, the guest cart will now be merged with their account after logging in. This ensures that any items added to the cart during the guest session are retained when they sign in or select an existing account, improving the continuity and experience for returning users.
Key benefits:
1. Enhanced User Experience: By allowing guests to sign in or create an account directly from the mini-cart, we provide a more intuitive and streamlined checkout process. Guests can complete their purchase with minimal steps, reducing friction and abandonment rates.
2. Cart Persistence: The ability to merge guest carts ensures that items are not lost when guests decide to sign in or register. This improves convenience for returning users and supports a smoother transition between sessions.
Release Flag (opt-in)
Liferay Labs is an innovation hub within Liferay Marketplace dedicated to exploring newer technologies and developing experimental features. It provides a wide range of useful applications developed by Liferay staff. These are available to the community from Marketplace.
Liferay Labs serves as a platform for rapid prototyping and testing new ideas. These apps may often be integrated as future Liferay features. Under Liferay Labs, you can also find all the legacy apps that are no longer under official support.
All apps offered by Liferay Labs are free but without support. However, you may give feedback on apps containing beta features as it helps in improving them for a future release.
Key benefits:
1. Innovation Hub: serves as a testing ground for new and experimental technologies within the Liferay ecosystem.
Enables rapid prototyping and exploration of novel ideas.
2. Community Access: provides a platform for sharing valuable applications developed by Liferay staff with the broader Liferay community.
Makes these applications readily available through the Liferay Marketplace.
3. Future Feature Roadmap:Acts as a proving ground for potential future features of the Liferay platform. Allows for real-world testing and user feedback on new functionalities before official integration.
4. Legacy Application Repository: serves as an archive for legacy applications that are no longer officially supported. Enables users to access and utilize these applications if needed, while acknowledging their limited support.
Release Flag (opt-in)
External Reference Code is now supported in Currencies.
It is also now possible to use the ERC to update and delete Currencies via their headless APIs.
Additional ERC support for the entities that have a relation with a currency has been added when creating new Catalogs, Channels, Price Lists/Promotions, Orders and Payments.
Key benefits:
Enhanced Data Management;
Improved Integration Capabilities;
Enhanced System Scalability;
Reduced Errors
Generally Available (aka OOTB)
This feature enhances the filtering capabilities within the headless-admin-user endpoints by enabling filtering based on custom fields for Accounts and Account Groups.
Key benefits:
Improved Data Retrieval Efficiency
Enhanced Data Management
Increased User Productivity
Generally Available (aka OOTB)
This feature focuses on rigorously aligning the User Management headless APIs with the established standards and best practices. This includes:
Comprehensive Functionality Testing: Verifying that all API endpoints (PATCH/POST/PUT) correctly update the expected fields in user records.
Custom Field Support: Ensuring seamless integration and proper functioning of custom fields within the API interactions.
Error Handling: Thoroughly testing error handling mechanisms and verifying that informative and user-friendly error messages are returned in all relevant scenarios.
Data Manipulation Capabilities: Confirming the correct and efficient functioning of sorting, filtering, and other data manipulation operations within the API.
Key benefits:
Enhanced User Experience: By ensuring the reliability and accuracy of the User Management headless APIs, we provide a seamless and efficient user experience for developers and integrators.
Increased Developer Productivity: Well-defined and documented APIs empower developers to build integrations quickly and confidently, reducing development time and effort.
Improved System Stability: Rigorous testing and alignment with standards minimize the risk of unexpected errors and system disruptions, leading to a more stable and reliable user management system.
Enhanced Data Integrity: By ensuring accurate data updates and consistent API behavior, we maintain the integrity and consistency of user data across the system.
Generally Available (aka OOTB)
This enhancement introduces configurable default permissions for newly created pages. Admins can set these permissions at both the instance and site levels. Instance-level settings are managed in a new Instance Settings panel, while site-specific overrides can be configured in the Site Configuration area.
This feature enables users to export a CSV file containing detailed information about segment membership, including a list of all known individuals within a segment and their associated data, providing valuable insights for stakeholders.
Highlights:
Export Capability: Allows users to generate a CSV file containing segment membership data.
Comprehensive Details: Includes a list of all known individuals in a segment, with details such as names and email addresses.
Actionable Insights: Equips stakeholders with valuable data for analysis and decision-making.
Generally Available (aka OOTB)
Users can access a new Performance tab on the Content Dashboard, which provides detailed metrics for assets, including visitor behavior and the top pages where each asset is featured. Data can be filtered by anonymous or known visitors. These metrics are available for Blogs, Documents and Media, and Web Content and are exclusively accessible to users connected to Analytics Cloud.
This functionality refers to tracking events related to non-default asset types and visualizing the data on a dashboard. From now on, customers will no longer be able to use this specific method to track views of non-default asset types and visualize this data on a dashboard in Analytics Cloud
Using custom event tracking is the recommended way to track your custom assets from now on.
This functionality refers to segments that are static groups of users.
That said, users can now utilize either user group-based segments or dynamic segments instead of static ones moving forward.
Default View and Download permissions for documents have been adjusted to match the behavior prior to the changes introduced in LPD-16744, restoring the expected user experience.
Highlights:
The View and Download permissions will be linked by default when uploading documents through the single and multiple file uploaders
The Permissions configuration UI is improved so users can more easily recognize that the View and Download permissions are separate permissions
The Download permission is now automatically included when a user shares a document and assigns permissions
Generally Available (aka OOTB)
We added External Reference Codes for Categories and Tags and their associated API’s, improving their portability for data migration scenarios.
Highlights:
Users can now perform CRUD operations using a Tag’s ERC through its headless API (Keyword)
Users can now perform CRUD operations using a Category’s ERC through its headless API (TaxonomyCategory)
Generally Available (aka OOTB)
We added External Reference Codes for references in widget configurations in Content Management applications. This helps promote data integrity when pages and their widgets are migrated across environments.
Highlights:
References within the following page widgets now use ERC’s instead of internal ID’s:
- Announcements
- Web Content Display
- Category Filters
- Questions
Generally Available (aka OOTB)
We added several API endpoints for Documents & Media to improve programmatic management of these entities.
Highlights:
Users can now add, delete, and retrieve document types via headless API (DocumentDataDefinitionType)
Users can now add, delete, and retrieve document metadata sets via headless API (DocumentMetadataSet)
Generally Available (aka OOTB)
It is now possible to subscribe to documents and folders, allowing users to receive notifications when they are updated.
Highlights:
Users can now subscribe to documents and folders through the “Subscribe” action and through the Subscribe icon in the Info Panel
If a user subscribes to a folder, all documents and subfolders within it will be automatically subscribed to as well
Generally Available (aka OOTB)
During the publishing process, users can both define and manage permissions, as well as schedule publication dates for their web content. When creating content for the first time, users will have the opportunity to conveniently review and manage permissions. Furthermore, when editing previously created content, users can also adjust permissions directly from the editor view. Additionally, users can easily select the desired publication date for their content during the publishing process.
Users can select and reorder categories for a blog’s friendly URL, so they can preview the order of the categories in the friendly URL and determine how the categories will be presented in the friendly URL along with the title.
Users are able to set different values for the asset types separators in the friendly URLs. Also, they are able to reset to default value, so for those asset types that they have clicked on this option, the separator will be the value defined by default for those specific asset types.
This release expands the support of the Timeline History feature to Blogs, Wiki pages, Bookmarks, Forms, Knowledge base, Message boards, and Categories. The feature enhances the publication toolbar with tools to detect and manage collaboration conflicts.
A timeline icon shows recent modifications in the same asset, which may have been done in production or parallel Publications.
The user can view, discard, or move these changes directly from the toolbar.
Warning icons appear to make users aware of current conflicts in the Publication.
Key benefits:
Enhanced context for content editors and managers for a streamlined collaboration.
New capabilities to detect conflicts before publishing time, while users may have more time to decide how to resolve conflicts without the go-live pressure.
Release Flag (opt-in)
This set of improvements aims to simplify the manual work users must do to resolve conflicts when publishing a publication. Now, instead of raising a conflict to be resolved manually by the user, the system will try to overwrite conflicting changes in production with the modifications done in the publication, meaning that the Modification and Modification deletion conflict types won’t be presented for the user anymore.
In the case of a Deletion modification conflict, the system won’t resolve it automatically, but now it makes it easier to keep the modifications made in the publication. In the Conflicting changes screen, we added a button with the option to "Restore in Production" for conflicts in which the asset was deleted from production and is now in the Recycle bin.
Key benefits:
Reduce the amount of manual work by automatically solving most of the conflicts.
Improve user satisfaction and reliability on publications by ensuring that assets supported by Recycle Bin can be quickly restored, avoiding requiring the user to discard needed changes.
Release Flag (opt-in)