Release Notes
The batch engine's export endpoints now support filtering for object entries. This addresses a previous limitation where filtering was not applied to object entries during batch exports. This update ensures consistent data handling and filtering behavior across all entity types.
Key benefits:
Until now, there was no way in batch engine to export and import object entries and their permissions simultaneously. This new capability allows users to do that, streamlining workflows and reducing manual effort.
Key benefits:
Execution in only one call.
Possibility for users to choose to take into account (or not) permissions with object entries.
Data imports, using batch engine, now allows users to preserve content creator information (if required). Previously, imported content with batch was always assigned the user performing the import, resulting in loss of original authorship data when moving content. This update ensures accurate attribution of content ownership (if required).
Key benefits:
Able to keep critical user information during data promotion between environments
Can be configured separately per import process
Implemented proactive access token management with automated email notifications. Users will now receive alerts 1 month, 10 days, and 1 day prior to token expiration, allowing for timely renewal and preventing service disruptions. Notifications are automatically cancelled if a new token is generated.
Key benefits:
Users are notified before token expiration, allowing for timely renewal and uninterrupted access.
Reducing administrative overhead, as automated notifications eliminate the need for manual monitoring and intervention.
By prompting timely renewals, the risk of using expired and potentially compromised tokens is minimized.
The vendor has deprecated OpenSSO/OpenAM, so there's no reason for us to keep it. The alternative, which is PingAM can be integrated using our existing OpenID connector or SAML Authentication.
The SSL Certificate Management view now provides expiration alerts for certificates nearing expiration (e.g., within 30 days) and those that have already expired. Certificates must now be defined exclusively through the LCP.json file, simplifying management and ensuring consistency across deployments. This update reduces manual errors and ensures secure and uninterrupted deployments.
Highlights:
Expiration Alerts: Notifications for certificates nearing expiration and those already expired, with clear visual indicators.
Exclusive LCP.json Configuration: Certificates can only be defined through the LCP.json file.
Improved Visibility: Organized list view showing certificate names, types, associated domains, and expiration dates.
Proactive Management: Tools and alerts to help users maintain secure SSL/TLS configurations.
The Marketplace release of the Liferay Connector to OpenSearch 2 provides an alternative to Elasticsearch for Self-Hosted Liferay deployments.
This connector integrates Liferay DXP with OpenSearch 2.12+, the open source and enterprise grade search engine. OpenSearch offers lexical search for text data, robust scalability and extensibility, and vector search for applications using embeddings, such as Liferay's Semantic Search.
The installation of this app requires specific configurations covered in the official documentation. For detailed compatibility information, see the Search Engine Compatibility Matrix.
The OpenSearch integration is currently a Beta feature with the intention to make it GA in the future.
Liferay Cloud now provides CI/CD support for Client Extensions on Liferay PaaS. Developers can integrate Client Extensions into their Git-based CI/CD pipelines, ensuring automatic builds and deployments alongside core Liferay services. This update enables automated validation, independent deployments, and faster release cycles for Client Extensions.
Highlights:
Dedicated CI/CD Pipeline: Separate build pipeline for Client Extensions to prevent conflicts with core Liferay services.
Automated Builds: Every commit triggers a new Client Extensions build, packaged as a LUFFA archive.
Independent Deployments: Client Extensions builds deploy separately, improving release flexibility.
Seamless Integration: Works with existing Git-based workflows on Liferay PaaS.
Zero Downtime Deployments: Deploy client extensions without affecting the main Liferay service.
Liferay 7.4 introduces the ability to manage language translations directly within client extensions. This enhancement allows developers to provide multilingual support for custom labels and properties without relying solely on OSGi bundles.
Key benefits:
Developers can now define and manage language keys and translations within the client extension itself, ensuring that all labels and custom properties are displayed correctly across different languages.
This feature eliminates the issue of untranslated labels with dashes, providing a consistent and professional appearance on multilingual sites.
Simplifies the process of adding translations, reducing the need for manual intervention and external OSGi bundles, thus accelerating the development and deployment of multilingual features.
Empowers developers to create more flexible and fully localized custom elements and themes, enhancing the overall versatility of the Liferay platform.
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.
We have introduced a new publication size classification feature to help users better manage and plan the publishing process, especially for "large" publications where there are many changes involved. This feature categorizes publications into three tiers: Small, Medium, and Large, based on factors such as the number of changes made and the size of the database. This will allow users to better understand the scale of their publication and take the necessary steps to avoid potential conflicts or performance issues during publishing. Publication Owners are also notified whenever a Publication has changed sizes.
Key Benefits:
Improved Planning: With the new size classification, users can see the current "size" of their publication and allocate the appropriate time and resources for publishing. This helps avoid rushing through a publishing process that might take longer depending on the publication's size.
Better Visibility of Potential Impact: The classification provides users with a visual indicator that highlights the size of the publication, offering transparency about what to expect during the publishing process. It also helps reduce the chances of errors or performance issues related to publishing "large" publications.
Clear Communication: When users hover over the size classification, a helpful tooltip explains what the classification means and the potential consequences for the publishing process, ensuring users have all the information they need to make informed decisions.
When a user is deleted from DXP, the deletion now happens simultaneously in Analytics Cloud. To enable this, we’ve developed an API that automatically removes the same list of users from both DXP and AC in real time, ensuring data consistency across both systems.
Key Benefits:
Enhancenment of the review change screen by adding a progress bar to provide clear, visual feedback during the publication process.When you initiate the publication, you’ll now see a progress bar that tracks the status of the publishing process, helping you understand how much time is left before the process is complete.
Key Benefits:
Better Visual Feedback: The progress bar offers a clear, real-time indication of where you are in the publishing process, so you always know how much time is remaining.
Enhanced User Experience: With the addition of the progress bar, the publishing process feels more responsive and user-friendly, providing you with a smoother workflow
Users can now generate and download a PDF report of their event analysis, enabling seamless sharing of key insights with stakeholders.
Key Benefits:
Microsoft no longer supports Sharepoint versions 2010/2013. See SharePoint Server 2013 - Microsoft Lifecycle and Microsoft SharePoint Server 2010 - Microsoft Lifecycle.This feature has been in maintenance mode for a very long time and there is just a very small user base. Considering the high costs for us in terms of tests maintenance, we decided to deprecate it.
A new toggle has been added within the Specifications and Product Specifications sections of the admin UI.
This toggle allows Catalog Managers to easily show or hide individual specifications associated with a product. This functionality provides the flexibility to curate the information displayed to customers on product detail pages.
Key Benefits:
Improved Data Accuracy and Relevance: Hide internal or less relevant specifications, ensuring that customers only see information pertinent to their purchasing decisions.
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.
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.
Key Benefits:
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.
We integrated the Clay Table's column visibility dropdown and column sorting functionalities into the Frontend Data Set. This makes a unified approach to table interactions across Liferay, replacing inconsistent custom implementations.
Key Benefits:
A more standard column visibility and sorting that guarantee a more usable and predictable interaction across the platform.
Reduces redundant code by aligning with the Clay Table’s native functionalities.
Developers no longer need to manage multiple implementations for similar features.
Ensures UI and UX consistency with Liferay’s design system.