The FF changes from Beta to Release

Users now have more access to several more metrics on their metrics page. Improving their visibility and troubleshooting capabilities.

Highlights

• New metrics visible in the metrics page;

• New metrics improve visibility of platform and infra elements, greatly speeding up troubleshooting and understanding of platform behaviour.

• The selection of metrics leverages our deep understanding

In order to assist users in the migration to Jakarta EE required for 2025.Q3 and beyond, Blade and Workspace users now have a command to automatically convert their source code from Java EE to Jakarta EE for DXP-provided libraries.

Benefits

This tool simplifies the process for users migrating custom code to Jakarta. Providing:

1. In-place source code transformation from javax to jakarta for custom development projects using DXP-provided libraries

2. Liferay-specific dependency mapping

3. Portlet 4.0 conversion

4. Integration into Liferay Workspace

5. Supports source code conversion regardless of deployment method (e.g. JAR or WAR)

This tool is supported by Liferay to convert source code for compatibility with the Jakarta libraries provided by Liferay DXP.

The OpenSearch 2 connector is transitioning to Generally Available (GA). A new version of the application is expected to be released on Liferay Marketplace for 2026.Q1 later in Q1 (by the end of March, tentative).

Include page fragments interactions for Analytics Cloud performance tracking. Previously, only assets displayed via native widgets (portlets) were instrumented for performance metrics

A user-centric consent management approach where consent preferences are securely stored on the server and linked to a registered user account, enabling a persistent, cross-device experience while maintaining user control and compliance.

Key Benefits:

• Seamless experience: Users are not repeatedly prompted for consent across devices or after clearing browser data.

• Stronger compliance & control: Consent is centrally managed, auditable, and can be optionally restricted by the user for cross-device storage.

A configurable consent access mechanism that allows administrators to enable and customize a persistent floating icon, giving end users continuous access to the Consent Panel after the initial banner interaction.

Key Benefits:

• Continuous user control: End users can easily revisit and modify or withdraw their consent at any time.

• Flexible configuration: Administrators can enable, disable, and customize the floating icon to match site needs and design.

Previously, comments might have been trapped in the Liferay UI; now, they are first-class citizens in the API, allowing for seamless discussion threads across any connected platform.

Liferay has expanded its Headless API capabilities to include full management of Object Entry comments. When commenting is enabled for an Object definition, developers can now interact with those discussions via dedicated REST endpoints. This update supports full CRUD operations (GET, POST, PUT, and DELETE) using External Reference Codes (ERCs) for easier identification across systems.

Key Benefits:

• Feature Parity for External Applications: Developers building custom front-ends can now provide a fully interactive "social" experience.

• Complete CRUD Capabilities: Users aren't just able to read comments; users can programmatically create, update, and delete them.

Adding OpenID Connect and Facebook authentication options to the Sign-In utility page.

Enhancements to the consent renewal configuration ensuring consistent field placement, controlled activation flow, and improved usability through date-based selection for renewal and dissent periods.

Key Benefits:

• Consistent and intuitive configuration: Standardized field positioning and enabled-only editing reduce confusion and misconfiguration.

• Improved usability and precision: Date selector support allows more accurate and user-friendly management of renewal and dissent periods.

As part of Liferay strategy to increase product led growth, we are going to offer a free tier version of our CMS with some key limitations to allow users to test and interact with the product enough to understand if the product meets their needs.

To make this possible, we need to implement how the tiers (Free and Enterprise) will affect the product and how these customers can move from the Free to the Enterprise through the product.

Key Benefits:

• Lower Barrier to Entry: Users can start building and testing their ideas immediately without upfront investment, making it easier to validate the CMS for their specific needs.

The platform now features a "Reset Consent for All Users" button located within the Instance Settings under the Platform configuration for Terms of Use.

When an administrator activates this button, the system automatically resets the agreedToTermsOfUse flag for every account in the instance, which effectively forces all users to review and accept the current legal version upon their next login.

To ensure complete transparency, this action triggers a specialized AGREED_TO_TERMS_OF_USE audit event rather than a standard user update log. This dedicated event captures critical metadata within its payload, specifically the articleId and groupId, to provide definitive proof of exactly which version of the terms was active at the time of the reset.

Key Benefits:

• Regulatory Compliance: Easily prove exactly which version of your legal terms a user accepted, simplifying audits for GDPR, CCPA, or internal legal reviews.

• Operational Efficiency: Eliminates the need for manual workarounds or technical intervention when legal documents are updated; a single click handles the entire user base.

• Granular Reporting: By using a dedicated audit event instead of a generic update flag, administrators can filter logs more effectively to monitor compliance trends and completion rates.

This epic is focused on implementing targeted improvements to the import/export translations functionality. In the past, due to resource and time constraints, we were not able to fully optimize the user experience for this feature. This work is aimed at addressing those known shortcomings, specifically by improving the UX and the functionality of key buttons and drag and drop for uploading items, to make the process more intuitive and user-friendly.

We’ve introduced the ability to import and export categories and tags directly within the new CMS. This feature allows you to manage your site’s organization in bulk, removing the need to create or edit every individual item one by one.

Key Benefits:

• Saves Time: Quickly set up or update large lists of categories and tags through a single file upload rather than manual entry.

• Better Accuracy: Easily audit and clean up your tags in a spreadsheet to ensure consistent naming and organization across your entire site.

The Digital Sales Rooms provide a streamlined experience where sales representatives can quickly launch branded deal portals using pre-configured site templates. Within these rooms, a centralized content hub allows for the seamless sharing and management of documents, proposals, and multimedia assets, ensuring all stakeholders are aligned on the latest versions.

To drive proactive sales strategies, the platform includes an Engagement Tracking Dashboard that monitors buyer activity in real-time, highlighting which assets are being viewed or downloaded. Collaboration is facilitated through a persistent commenting system that keeps deal-related discussions in context, while a library of specialized Page Fragments allows teams to build tailored, visually engaging buyer experiences, such as milestone timelines and video introductions, without requiring technical design skills.

Access is managed through a secure, account-based invitation flow, ensuring that sensitive deal data.

Key Benefits:

• Accelerated Deal Velocity: By centralizing documents and approvals, DSR reduces the friction caused by "lost" emails and versioning confusion, leading to faster decision-making cycles.

• Data-Driven Sales Strategy: Engagement analytics allow Sales Reps to gauge buyer "heat" levels, knowing exactly which stakeholders are active and which documents are most interesting, enabling more targeted follow-ups.

• Professionalized Buyer Experience: Provides B2B buyers with a modern, self-service portal that is consistently branded and easy to navigate, reinforcing the seller’s position as a premium partner.

• Reduced IT Overhead: The no-code site creation flow empowers non-technical staff, such as Sales Engineers or Account Executives, to spin up secure environments without intervention from the IT department.

1. Digital Sales Room - Creation

2. Digital Sales Rooms - Uploading Documents

3. Digital Sales Rooms - Invitations & Contributor's Perspective

4. Digitial Sales Rooms - Analytics

CMS administrators can now modify content structures and their repeatable fields after publication — adjusting field configurations, nesting order, and repeatable settings without deleting existing content. Teams iterate on their data models as business needs shift, and all previously published entries stay intact.

Key Benefits:

• Refine your content model based on real-world usage instead of locking in every decision up front.

• Skip the "delete everything and rebuild" cycle when requirements change — existing entries come along for the ride.

• CMS admins adjust structures directly, without pulling in developers or database work for every tweak.

Data modelers can now define Link Content fields that let content creators select existing entries from other objects—single or multiple—instead of retyping the same values across entries. The CMS moves from isolated documents to a connected data model, so information like vendor names, categories, or authors stays consistent across every publication.

Key Benefits:

• Eliminate typos and inconsistencies by picking existing entries instead of re-entering text.

• Reuse the same author, category, or vendor across hundreds of entries—update it once and it propagates everywhere.

• Support both single and multi-select relationships, from "one author per article" to "many products per campaign.”

This feature introduces a centralized administration interface within the Data Set Manager to oversee and moderate User Views. Administrators can now access a global list of all User Views to monitor usage or perform cleanups.

Key Benefits:

• Centralized Oversight: A new "Manage User Views" button in the Data Set Manager provides a complete list of all User Views for easier monitoring.

• Contextual Access: Admins can jump to the management view from specific Data Set settings, where the list is automatically pre-filtered to show only the views belonging to that Data Set.

• Administrative Control: Enables admins to maintain system hygiene by deleting individual or multiple User Views via bulk actions.

• Full Visibility: Provides key details at a glance, such as which user created the view and which Data Set it belongs to, ensuring better governance of user-generated configurations.

From now on CK Editor 5 will be the default rich text editor present in Liferay DXP. For those customers with custom plugins or other particularities over CK Editor 4 that don’t want to upgrade yet, they can enable the deprecation Feature Flag (FF-11235) to have CK Editor 4 as default in DXP.

Note: CK Editor 4 still remains the default editor on some of the DXP features, those which are in Maintenance Mode such as Knowledge Base or Blogs, these experiences will not be migrated to CK Editor 5.

Content teams can now find and replace text, URLs, or terms across the entire CMS repository in a single action — covering titles, content fields, and friendly URLs. Every operation includes a mandatory preview, scoped targeting, and automatic versioning, so large-scale updates like rebrandings or URL migrations are fast, reversible, and low-risk.

Key Benefits:

• Cut rebrandings and terminology rollouts from hours of manual edits to a single bulk action.

• Preview every change before it's committed, with automatic versioning if you need to roll back.

• Scope replacements by site, content type, or field so global updates stay surgical instead of sweeping