Users can now generate and download a PDF report of their event analysis, enabling seamless sharing of key insights with stakeholders.

Key Benefits:

• The PDF format ensures consistency when sharing insights across teams.
• The feature is accessible directly from the Event Analysis interface, simplifying the download process. 
• Users can optionaly choose to add a date range while downloading their pdf

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:

• Processing Time: Depending on the number of users deleted, the process may take some time in Analytics Cloud. You can track the progress in Data Control & Privacy > Request Log under “Request Status.”
• Suppression Before Deletion: Each deleted user must first be suppressed before being permanently deleted in Analytics Cloud. As a result, you will see two requests per user—one for suppression and another for deletion.

We’ve introduced a new bulk operations feature that allows you to select multiple changes within a publication and perform actions on them all at once. This feature streamlines the process of managing multiple changes, saving you time and effort when working with large publications.

Key Benefits:

• Efficiency: You can now select multiple changes and perform bulk actions (like moving or discarding them) without needing to handle each change individually. This is particularly helpful in large publications where managing changes one at a time can be cumbersome and time-consuming.
• Improved Workflow: The ability to select and execute multiple operations at once significantly reduces the number of steps needed to manage your content, improving your overall workflow and productivity.

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

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.

This release introduces in-context translation for all the form fields directly within the page editor. This empowers content creators to easily create localized form experiences for their users, enabling them to complete forms in their preferred language. Only designated localizable form fields will be translated, ensuring precise control over localized content.

Key Benefits:

• Faster time to publish localized forms: Translating directly in the editor reduces the steps needed to launch forms in multiple languages.

• Reduces reliance on external tools or workflows: Content teams can manage translations within the same interface they use to build pages, simplifying the process.

• Improves accuracy and consistency: Only the form fields marked as translatable are included, so there's less risk of translating the wrong content or missing something important.

• Better experience for global audiences: Visitors can complete forms in their preferred language, which can increase completion rates and engagement.Gives teams more control over localization: Editors can choose exactly what gets translated and when, without needing developer support.

Field visibility can now be configured based on values within the same custom fragment. This enables fields to dynamically show or hide based on user input, supporting more responsive and context-aware interfaces.

This update gives teams more flexibility when building custom fragments, making it easier to support complex use cases without additional custom code.

Customers very commonly deploy fragments through the deploy folder, we identified that we are missing one log once the fragment import finished. Until now Liferay added a message in the application server logs that show that the fragment import has started, but it never indicates when it finishes. Some advantages of logging when the import process finishes is that customers can check when the deployment is still in progress and when it ends, not only being informed in case of failures.

This feature enable the creation of multi steps forms in Page Editor.

Allow users to modify only the first collection display item.

The existing documentation for Clay components and the API Table has been inconsistent in quality, often lacking detailed explanations and practical examples. This inconsistency makes it difficult for developers to effectively utilise these components, leading to confusion and an increased number of support requests.

Key Benefits:

• Developers now have a better mechanism for generating API Tables for components, improving the overall understanding of component usage and available APIs. With detailed explanations and real-world examples.

• With this new standardised documentation practices we can ensure a uniform quality and completeness across all components.

• Clearer, more structured, and more practical documentation will reduce frustration and improve the development process.

• Clearer documentation minimizes the need for external support, freeing up resources and improving response times.

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.

Style Books in Liferay are now explicitly tied to a specific theme at the moment of creation, using the frontend token definition provided by that theme (via OSGi or themeCSS client extension). This structural link now ensures that each Style Book can only operate within the boundaries of its associated theme, eliminating cross-theme token contamination and enforcing clearer theme-based design governance.

Key Benefits:

• Users can no longer save Style Books that accidentally combine tokens from different themes, avoiding visual inconsistencies and design regressions.

• Every Style Book now visibly shows which theme it belongs to, reducing errors and making it easier for teams to manage design assets across multiple sites.

• When applying a Style Book to a page, the system will only list those created with the same theme as the page’s current one—no more trial-and-error or guesswork.

• If a Style Book becomes incompatible with the applied theme (e.g., after a theme change), it will be automatically unlinked to prevent display issues.

• During platform upgrades, existing Style Books are automatically linked to the site’s current public theme (as defined in Site Builder > Pages > Options > Configuration), reducing manual cleanup work.

• If a Style Book is imported without a valid themeId, the user gets a clear warning and knows exactly what’s missing to fix the import.

• Style Books based on themes that are no longer deployed or no longer provide a valid frontend token definition are automatically marked as inactive—clearly flagged and non-selectable.

• The OSGi or themeCSS client extension ID is displayed for inactive Style Books, helping devs or admins identify which theme needs to be re-installed or fixed.

With the release of Liferay DXP 2025.Q2, we are deprecating the Elasticsearch 7 compatibility due to the end-of-maintenance and upcoming EOL of the Elastic Stack 7.17. Liferay strongly recommends all customers with 7.17.x or earlier deployments to upgrade to the latest compatible version of Elasticsearch 8.x. Learn more. 

The Concurrent and Sync Reindex Modes, providing high-availability, introduced in Liferay DXP 7.4 Update 98 / Liferay DXP 2023.Q4 are now GA.

Reduce downtime, improve operational and resource utilization efficiency with the new Concurrent and Sync reindex execution modes providing high-availability in search capabilities while the operation is running.

In this release a new type of Data Set called System Data Sets is introduced, which will allow admin users to clone Java/Code Data Sets, making them editable and customizable through the Data Set Manager, which allow to customize any administration part of DXP built with a customizable Java/Code Data Set.

In this release the Data Sets from Order Pages have been made available as System Data Sets:

• Pending Order Items

• Placed Order Items

• Order Returns

• Pending Orders

• Placed Orders

In the next releases more and more Data Sets will be added to the list.
 

Key Benefits

• This epic increases the flexibility of Liferay DXP by enabling partial customization of previously hardcoded Data Sets.

• Admins will have more control over the user experience, enhancing the platform's ability to meet diverse and evolving business requirements.

• This also reduces the need for custom development efforts to modify or replace hardcoded Data Sets.

When an admin user is managing a Data Set, they might create sorting options, filters and actions. Until now, if the admin user chose not to show them to the end-user, they had to be deleted. From now on, these sub-entities can be deactivated, hiding them from the end-user without losing editing progress.

Key Benefits:

• Easier management of sub-entities without requiring deletion and recreation.
• Improved usability by allowing admins to configure visibility dynamically.
• More flexibility in defining experiences without modifying underlying data.

Improved the usability, functionality, and consistency of bulk actions in Frontend Data Sets across Liferay DXP. The selection behaviour of items has been refined, ensuring consistency in visualization modes, enhancing bulk action visibility, and making interactions more intuitive and efficient for end users.

Key Benefits:

• Preserve selection between pages of items so the user can easily select items from multiple pages.
• Add Select All and Clear buttons to allow users to easily work with large amount of items.
• Added contextual menu with access to all bulk actions available.
• Highlighted bulk actions to easily access more common actions.

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. In this release CK Editor 5 has been made available in DXP and installed in four different experiences under Beta Feature Flag. (FF-11235):

• Web Content

• Object entry (editing a Rich Text Field)

• Document Types (when adding a Rich Text field)

• Metadata Set (when adding a Rich Text field)

• Forms

• Element Sets

After this, CK Editor 5 will be included in other areas and experiences in the near future:

• Page Builder

• Commerce

• Web Content Description

Key Benefits:

Benefits when CK Editor is available across all DXP, note that current effort only includes Webcontent

1. Support modern web standards, including HTML5 and Content Security Policy (CSP).

2. Provide a seamless copy-paste experience from external tools.

3. Leverage OOTB features like the inline editor for a more flexible editing workflow.

4. Adopt a supported and actively maintained version of CK Editor.

5. Remove reliance on multiple editors and standardize the editing experience across Liferay DXP.

More highlights and benefits here

To continue broading the CSP support now 2 new directives are supported: base-uri and object-src

With these two new directives support Liferay DXP covers all the directives recommended in the Google CSP Evaluator.

Key Benefits:

• Enhanced Security: Mitigates risks of XSS and data injection attacks by controlling resource loading and execution.

• Compliance-Friendly: Aligns with industry-standard security requirements, supporting stricter compliance protocols.

• Customizable Policies: Allows developers to tailor CSP directives to meet specific project or organizational needs.

• Improved Trust: Strengthens end-user trust by providing a more secure and reliable platform experience.

Supported directives with recommended values:

Working with Global Services to identify pain points in Javascript resources distribution and unused code was the trigger to:

• Remove unused packages

• Deprecate old packages

• Set configurations to let users to not use/load some functionalities

• Create a JS size comparision report

• Create tooling to be able to split modules in smaller submodules
   

Key Benefits:

• Reduced total JS bundle size → Faster portal loading

• Reduced total exports → Faster portal loading

• Taking as example Masterclass home page:

  • Reduced JS Size in MB by 20%

  • Reduced number of request by 12 %

  • Mobile Lighthouse score from 52 to 56

  • Desktop Lighthouse score from 70 to 77

• Allow teams to divide modules to offer smaller entry points when they detect some part of the module is not commonly used.

• Size report tooling able to trigger risks.

The Lodash library is being deprecated and it is not included in the bundle unless deprecation FF LPD-48975 is enabled.

The AMD Loader is being deprecated and it is not included in the bundle unless deprecation FF LPD-48372 is enabled.

As a result of the AMD Loader deprecation, the npm-bundler will stop working too, it is recommended to use standard bundling tools such as webpack, esbuild, vite, etc.

The JS Component Support Tabs (data-toggle="liferay-tabs" API ) is being deprecated and it is not included in the bundle unless deprecation FF LPD-47713 is enabled.

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:

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