We will introduce a deprecation badge within the Segments Editor in DXP. This badge will be visible whenever users attempt to create a new segment or edit an existing one. In addition to the badge, a UI alert will inform users that Segments in DXP are planned to be deprecated and that Analytics Cloud (AC) will become the single source of truth for segmentation.

This change is intended to proactively set expectations and guide users toward creating and managing segments in Analytics Cloud moving forward.

Starting in 2026.Q1 version, the Segments module in DXP will transition to a read-only experience by default. Users will only be able to view the list of segments created in Analytics Cloud within DXP. Segment creation and editing capabilities in DXP will no longer be available unless the Segments deprecation feature flag is explicitly enabled.

The long-term direction is for Analytics Cloud to fully own segment creation and management, ensuring a single, centralized segmentation workflow.

GDPR (EU) requires consent renewal every 12 months. Some national data protection guidelines even recommend more frequent renewal, such as every 6 months.

We the renewal periods configurable where the administrator can manually add a number of months (maximum 12) to define the renewal period.

Key Benefits:

• Supports regulatory compliance: Provides the technical capability to align consent renewal with GDPR and national data protection guidelines, including more frequent renewal requirements.

Object entry pages can now use meaningful, human-readable URLs even when built with custom layouts. Instead of relying on automatically generated numeric identifiers, administrators can define addresses based on business data, such as an event name.

This improvement brings the same flexibility already available in other layout experiences to scenarios that require more advanced or tailored UIs. The result is clearer links, easier sharing, better discoverability, and a more consistent navigation pattern across the portal.

Key Benefits:

• Consistency across layouts – Custom layouts now provide the same URL capabilities users already expect elsewhere.

A new notification capability has been added to the Orders Questions & Answers feature (formerly Commerce Order Notes) to improve timely communication between Buyers and Order Managers, ensuring that Order Managers are notified when a Buyer adds a comment and Buyers are notified when an Order Manager responds.

To support both user notifications and email notifications, we created a new System Object: Commerce Order Note. By leveraging Object Actions, it is now possible to trigger notifications directly from the Questions & Answers flow.

On the Commerce Order Note object, we introduced two terms — Order Note Recipient Emails and Order Note Recipient IDs, to dynamically determine the recipients of email and user notifications. The recipient selection logic respects channel-level configurations, including Open Orders Visibility Scope, Placed Orders Visibility Scope, ensuring that notifications are sent exclusively to users who are authorized and within the configured visibility scope.

Additionally, a new toggle was added in the Channel configuration — Enable Notifications User Scope — which, when activated, ensures that only the buyer user who is the owner of the order receives notifications for responses from Order Managers.

This ensures that notifications are both permission-aware and contextually relevant, maintaining privacy while improving responsiveness.

Key Benefits:

• Improved Communication Efficiency: Buyers and Order Managers are instantly notified of new messages, reducing response times and eliminating manual follow-ups.

• Role and Permission-Based Accuracy: Notifications are dynamically scoped to authorized users only, ensuring privacy and reducing unnecessary alerts.

• Targeted & Controlled Visibility: Private notes and user-scoped configurations ensure sensitive communications are shared only with intended recipients.

• Configurable & Flexible: Channel-level visibility settings combined with the Enable Notifications User Scope toggle allow organizations to tailor notification behavior according to operational needs.

Within the Orders Admin Panel, a new “Recalculate” button has been introduced in the Order Summary.

This button enables administrators to recompute overall order totals following manual adjustments to order lines, executing a controlled summary-level recalculation without re-triggering the full pricing engine.

Key behavior:

• For any line the user has manually adjusted, the system preserves the user-entered values.

• For lines that have not been modified, the system retains the existing calculated values.

• Existing discounts on each line continue to be included in the total discount calculation.

• Manual quantity adjustments do not trigger changes to delivery pricing.

Key Benefits:

• Preserves User Control: Manual adjustments remain intact and are never overridden.

• Prevents Unintended Repricing: The full pricing engine is not triggered, reducing risk of unexpected changes.

• Improves Accuracy: Users can safely recompute totals without manual recalculation outside the system.

• Enhances Efficiency: Reduces reliance on external tools (e.g., spreadsheets) for validation.

We have introduced account-scoped order visibility to ensure that Order Managers only see and manage orders belonging to the Accounts they are assigned to.

This enhancement includes:

• A new regular role: Order Administrator

  • Grants out-of-the-box (OOTB) visibility and control over the Orders and Shipments panels within the Commerce Applications Menu.

• A new Order permission: Manage Accounts Scoped Orders

  • Assigned OOTB to the Order Manager Account Role.

  • When granted, this permission automatically filters orders so users can only view orders associated with the Accounts they are assigned to as Order Manager.

By combining the Order Administrator role with the Manage Accounts Scoped Orders permission, Order Managers can directly manage the full order lifecycle for their assigned Accounts through the Administrative Panels—without exposure to unrelated Account data.

Key Benefits:

• Data Isolation & Security: Ensures Order Managers only access orders relevant to their assigned Accounts.

• Improved Operational Focus: Reduces noise by removing visibility of unrelated orders, enabling faster and more accurate processing.

• Enhanced Governance & Compliance: Supports stricter access control policies and aligns with account-based operational models.

• Scalable Multi-Account Support: Ideal for organizations where multiple Order Managers operate across different Accounts.

Platform flexibility and enterprise system support is important to our users. With this release we have expanded the Compatibility Matrix to include some new environments.

Application Servers:

1. Added support for WebLogic 15c (see details in dedicated WebLogic 15 release note)

2. Expanded Jboss version support from 8.0 to 8.x to help our users stay up to date with Red Hat support policy

Databases:

1. Added support for MariaDB 11.8

2. Added support for PostgreSQL 17.x

Operating Systems:

1. Added support for Red Hat Enterprise Linux 10

Key Benefits:

• Access to newer versions of environment to ensure the latest performance, compliance, and security patching access.

With Liferay's New Headless Content Management System (CMS), creating, organizing, and publishing content is simpler because all content management tasks are brought together in a single interface. Your content is independent of its presentation, allowing you to reuse it across sites, pages, and APIs.

You can work with articles, documents, media, and more, while taking advantage of features like global asset views, organized spaces, and cross-site publishing. Thanks to Liferay Objects, the CMS provides flexible content structures and ensures a smooth, consistent authoring and publishing experience.

Key Benefits:

• Release Change status from Beta to Release

• New Gallery View for files

• Export/Import for Categories, Tags and Content Structures

• UX improvements for Import/Export translations

• General UX improvements on Spaces

AI Rules Files (.workspace-rules) are now available OOTB with new Liferay Workspaces. These files provide AI agents with the Liferay-specific logic, context, and guardrails needed to generate accurate, best-practice customizations for Liferay DXP. These rules are symlinked for automatic discovery by Claude Code, Cursor, Gemini, GitHub Copilot, and Windsurf.

Blade 8.0 or higher is required to automatically set up new Liferay Workspaces with the AI Rules Files.

Key Benefits:

• Allows AI agents to become aware of the structure of Liferay Workspaces without any manual configuration.

• Assists new users with setting up a Liferay Workspace and running Tomcat bundle, with explanations for commonly used Blade commands.

• Provides Liferay recommended best practices for development.

• Enables AI agents to access the Liferay MCP server to query content, manage objects, and execute actions within the portal.

• Guided experience available to create and deploy a sample Client Extension, allowing users to quickly see Client Extensions in action in a running portal instance.

In order to assist customers with upgrades to newer Liferay versions, Blade and Workspace users now have a dedicated gradle command upgradeSourceCode to migrate their code automatically to their desired Liferay version. This will do in-place updates to custom code to account for breaking changes in the latest Liferay version.

For customers migrating to Jakarta for the first time, the Jakarta Migration Tool upgradeJakarta is also available to automatically convert their source code from Java EE to Jakarta EE for DXP-provided libraries. The Code Upgrade Tool should be executed first before running the Jakarta Migration Tool.

Key Benefits:

This tool simplifies the process for users migrating their code to newer Liferay versions, providing:

• Automatic source code migration for projects to a target Liferay version.

• Liferay version specific code upgrade automations to account for breaking changes.

• Integration with Liferay Workspace.

From now on, most JavaScript files in Liferay DXP have hashed file names generated at build time. For example, a main.js file may appear at runtime with a randomly generated hash value in its name, such as main.(tvERyCVfuRc).js.

This hash value represents a unique version of the file, so the browser can identify that the file’s contents have not changed. This allows the file to remain in the browser cache indefinitely when the infinite caching strategy is selected.

In addition, the frontend caching infrastructure now supports both infinite caching and time/validation-based caching strategies. These strategies can be configured through Instance Settings.

For those JavaScript files that cannot be hashed because they are generated at runtime by the server depending on some parameters, a new configuration is available in DXP to define their TTL and the option to add the no-cache header. This ensures the revalidation of the asset with the server before being served.

Also, hashed files have a fallback strategy based on TTL + eTag if they are requested using their canonical name. This acts as a fallback for import map errors or legacy portlets that are not aware of hashed file names.

Key Benefits:

The new Liferay DXP caching strategy for JavaScript files improves performance and stability.

1. Faster Page Loads:
Significant reduction in subsequent load times.

2. Elimination of Stale Resources:
Hashed URLs prevent users from seeing outdated JavaScript after an update.

3. Reduced Origin Server Load:
Less server overhead, as browsers retrieve unchanged files directly from their local cache, saving CPU and bandwidth.

4. Cache busting:
Updated resources automatically force the browser to fetch the new version by changing the file name hash whenever the content changes.

"Promote Content among Environments" is a Liferay initiative that takes content promotion to the next level. By implementing a significant infrastructure change (based on Headless Batch APIs), processes are substantially streamlined, optimizing existing processes and adding new ones that enable more secure, stable, and efficient content promotion.

Now you can promote elements at the instance level, such as Object Definitions, Picklists, or Roles, and freely export and import Object Entries with any scope. With the new Lazy References infrastructure based on External Reference Codes, relationships are maintained and updated regardless of the order of importation.

Furthermore, the new Report List provides a comprehensive and detailed record of everything that happened during the import process. This new report is essential for new entities because import processes will run from start to finish without stopping with the first issue, reporting all errors so you can resolve them collectively instead of having to address them individually with each run. For non migrated entities, the behavior will be the current one finishing the process with the first error.

Key Benefits:

• Infrastructure improvement: based on Headless Batch APIs executions, the processes are more efficient, faster and more stable, allowing for easy optimization and showing a clear information about the status of each execution. Some of the old staging entities have been migrated to the new framework:

  • Pages (and related entities like templates, utility pages or master pages )

  • Vocabularies

  • Categories

  • Tags

• New capabilities at Instance level: The coverage of entities that can be promoted is expanded by adding a list of entities like:

  • Instance Level

    • Roles

    • Accounts

    • Account Groups

    • Organizations

• Full support for Objects: Now all related Objects entities are supported for export/import:

  • Object Definitions

  • Picklist

  • Object entries with Company Scope.

  • Object entries with Site Scope

• The order of execution no longer matters: Lazy references based on External Reference Code is the key. Now, for entities that are compatible with Batch, the related elements are not automatically exported. Thanks to the External Reference Code the references can be maintained even if the other element does not exist, making the order of importing irrelevant.

  If an element is missing, an empty shell might be created to maintain the correct structure, and if the information is included either manually or in a subsequent import, the element is updated, preserving all existing relationships.

  For the entities still using the old infrastructure, the relationships will be maintained using the old mechanism.

• All Import information in just one click: Thanks to Lazy References, the process will attempt to import all items for batch-migrated entities without stopping for errors or warnings. For non-migrated entities, the process will still stop at the first error. Due to this hybrid mode, batch-based entities will be imported first. All generated information will be available in a detailed list that can also be exported in CSV format for external processing if needed.

We’ve redesigned the Global Menu to deliver a more intuitive, scalable, and visually engaging navigation experience across Liferay DXP. This update introduces a single, unified entry point to access all platform capabilities, reducing fragmentation and making it easier to move across features.

As part of this transformation, the DXP Control Panel has also been rebuilt with a cleaner UI, improved information architecture, live filtering for faster discovery, and a simplified landing home with contextual shortcuts.

Key Benefits:

• One clear entry point for all Liferay functionalities

• Reduced navigation complexity with consolidated access points

• Faster discovery through live filtering and improved structure

• Greater productivity for administrators and content teams

• Scalable foundation to support future platform growth

Semantic Search with OpenAI Integration (GA) [For LES Subscribers only]

Semantic search, powered by direct integration with OpenAI as a text embedding provider, has officially moved from Beta to General Availability (GA).

Configuration & Opt-in

To ensure zero impact on existing installations, this feature remains opt-in. To begin leveraging semantic search, administrators must manually configure the connection:

• Path: Navigate to Instance Settings > Search > Semantic Search.

• Action: Enable the OpenAI Text Embedding Provider and configure semantic ingestion for your desired content types and languages.

• Documentation: Please refer to the official guide for detailed setup instructions and for customizing search with semantic search.

Status of Other Providers

While OpenAI is now GA, other text embedding providers (such as txtai and Hugging Face) remain in Beta. These can still be accessed and tested by enabling the existing feature flag (LPS-122920) under Instance Settings > Feature Flags > Beta.

Liferay has significantly enhanced how content and experiences are managed with the new CMS, Objects, better content promotion between environments, and many other features that didn’t exist when the Publications' framework was designed.

Instead of redesigning the framework for this new scenario, we are developing a new set of tools that will still support Publications' use cases with even greater efficiency and flexibility:

• Marketing teams will orchestrate new content and page versions as campaigns through a new “bundling” feature.

• Live experiences (“Production”) will keep safe from ongoing or unapproved content and page changes through enhanced content statuses and versions governance.

• Authors will keep free to create, change, and preview their assets in context with a new Preview Framework.

Moving Publications into maintenance mode allows us to continue supporting current users while focusing on this new strategy and the next generation of publishing tools.

Assets that are currently being modified within a publication are now protected from deletion in production by default.

Previously, this behavior was optional and disabled by default. It is now enforced automatically to ensure greater stability and data integrity when working with publications.

Key Benefits:

• Prevents most of the deletion modification conflicts that could only be resolved by discarding changes

• Provides safer default behavior without requiring configuration

A new Pending approval publication status and filter option are now available in the Publications list.

Publications automatically receive the Pending approval status when at least one linked asset is still in Draft or Pending workflow status. A dedicated filter allows users to quickly identify publications that are not yet ready to be published.

Key Benefits:

• Speeds up the review and approval process

• Provides immediate visibility into publication readiness

• Improves clarity of workflow-related behavior

Reviewers can now directly access the desired asset edition screen when clicking Edit or Edit in Production from the Publications Review Change screen.

• Content Pages → Page Builder

• Widget / Portlet Pages → Page editing interface

• Page Templates → Template editor

• Other page types (Panel, Page Set, URL, Embedded, Link to Page) → Configuration screen

Key Benefits:

• Speeds up the review process

• Aligns edit actions with user intent

A new, dedicated Scope configuration is now available within the Query Builder, allowing administrators to precisely limit search results to specific Sites, Asset Libraries, and Spaces.

Key Improvements

• Dedicated Configuration: We recommend using this native Scope setting instead of manual filtering via out-of-the-box or custom query elements. It provides a more intuitive and performant way to define the search boundary.

• Default Behavior: If no specific Site, Asset Library, or Space is selected, the Blueprint will search across all available scopes by default.

Behavior Note: Scope Hierarchy

When a scope is defined within a Blueprint, it acts as a strict boundary.

• No Overrides: Search-time parameters (such as those from a Search Bar widget or the Headless Search API’s scope parameter) cannot override or expand the Blueprint’s pre-defined scope.

• Filtering Logic: Any scope requested at search time must be a subset of the Blueprint’s scope. If a user or API requests a scope that falls outside the Blueprint's configuration, the search will return empty results.

 
Besides the new scope configuration, the Query Settings section has been renamed to Source and moved to the main query builder screen, simplifying the editor experience.

 Key Benefits:

• Dedicated Configuration: We recommend using this native Scope setting instead of manual filtering via out-of-the-box or custom query elements. It provides a more intuitive and performant way to define the search boundary.

• Default Behavior: If no specific Site, Asset Library, or Space is selected, the Blueprint will search across all available scopes by default.