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:
|
Release Notes
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:
Key Benefits:
|
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:
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:
|
To prepare for Microsoft’s removal of Azure Access Control Service (ACS) for SharePoint in Microsoft 365 starting April 2, 2026, we’ve evolved the SharePoint connector authentication model. This ensures customers can continue accessing SharePoint seamlessly after April 2026, without disruption.
Key Benefit:
Ensures uninterrupted access to SharePoint after ACS deprecation
Aligns with Microsoft’s supported and future-proof authentication standards
Improves long-term security and compliance
The permissions-check modal introduced during content publishing is now optional. While this feature provides additional control by allowing users to review permissions before publishing, we recognize that it may add unnecessary steps for some workflows. Customers can now publish in just one step without having to check the permissions first.
Key Benefits:
Greater flexibility to adapt publishing workflows
Maintains enhanced permission control where needed
Avoids unnecessary steps for existing or streamlined flows
Respects different customer contexts and usage patterns
This epic delivers a comprehensive solution for exporting and importing vocabularies and categories with associated data across Liferay environments, tackling potential roadblocks to ensure a smooth and efficient migration process.
This epic delivers a comprehensive solution for exporting and importing tags with associated data across Liferay environments, tackling potential roadblocks to ensure a smooth and efficient migration process.
This feature introduces “Lazy References” to ensure import success regardless of deployment order. If an imported item references a missing Vocabulary or Category, the system creates a temporary “incomplete” dummy object. This special status allows the main content import to succeed immediately. The project’s focus is managing the status lifecycle to allow a smooth transition of these incomplete dummies to a fully approved state when the complete taxonomy object is imported later.
The Question Widget is a legacy application that was primarily maintained to support Liferay Ask. With the recent migration from Ask to Discuss (Liferay's new forum platform), this widget is no longer needed. Therefore, the Question Widget is being deprecated to reduce technical debt and ongoing maintenance costs.
As Liferay continues to invest in platform flexibility and enterprise stability, empowered by Jakarta EE, we are pleased to share that DXP is now certified for use with Oracle WebLogic Server 15c. This application server will be fully supported for Enterprise tier customers. Additionally, to empower DXP deployment on Oracle’s server, we have released a dedicated DXP WAR file optimized for WebLogic 15.
Key Benefits:
Modernized Tech Stack: Provides compatibility with the latest release from Oracle, ensuring your infrastructure is ready for the next generation of enterprise Java applications.
Simplified Installation: Streamlined deployment provided through the dedicated Weblogic WAR file.
Security Compliance: Moving to WebLogic 15c ensures you stay ahead of the security and patch lifecycles of older, non-Jakarta-based application servers.
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:
Databases:
Operating Systems:
Key Benefits:
|
Liferay has released a new version of the Liferay Faces (JSF) portlet bridge framework that is now compatible Jakarta EE, allowing users to migrated JSF portlets for usage with 2026.Q1.
Key Benefits:
Jakarta Support: JSF portlets can now be used on DXP with Jakarta namespace.
Simplified Migration: Liferay continues to support JSF 2.3-built portlets to make it easy to migrate to Jakarta with minimal breaking changes.
PrimeFaces support: Liferay has enabled usage of PrimeFaces portlets with Liferay DXP.
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:
|
This feature introduces a cleaner, more flexible empty-state experience in the Frontend Data Set by allowing the search bar and management bar to be hidden when no content is present.
Key Benefits:
The Dataset Consumer is able to hide Data Set management bar by just clicking a toggle
If toggle is enabled, management bar won’t be rendered in case of a “real” empty state
This can be configured both in system and custom datasets
This change promotes the Save Data Set view state to be recoverable when navigating back to it epic from Beta to General Availability, confirming the feature is stable and fully supported.
This change promotes the CK Editor 5 epic from Beta to Release.
Bridge Your Portal Data and Marketing PowerThe HubSpot Connector for Liferay is a powerful integration tool designed to eliminate data silos. It creates a seamless, automated bridge between your Liferay DXP portal and the HubSpot CRM, ensuring your sales and marketing teams always have the most up-to-date information at their fingertips. Stop wasting time with manual data exports. By connecting Liferay Objects directly to HubSpot, you can ensure that every new contact, company, or lead captured in your portal is instantly synced and ready for your next automated campaign. Key Benefits:
|
This update introduces a full commercial lifecycle for Client Extensions, allowing Publishers to list and sell high-value extensions, and Customers to purchase and deploy them directly into their DXP instances.
Key Benefits:
For Customers (Buyers)
Instant Capability: Acquire complex, production-ready features without long dev cycles.
Integrated Procurement: Purchase and manage licenses directly through the Liferay Marketplace.
For Publishers (Partners/Devs)
Monetization Stream: Turn their custom-built tools into a recurring revenue stream by reaching the global Liferay ecosystem.
Market Visibility: Showcase their technical expertise to a captive audience of enterprise-level decision-makers.
This set of epics aim to complete and strengthen the content page promotion and management system. We have developed necessary endpoints for various page types and implemented a comprehensive catalog of page elements and fragments. Additionally, we enhanced the data architecture through the integration of scopes and secure references. Together, these efforts ensure content integrity during import, export, and staging. The resul is a more stable page editor that handles lazy references and provides a seamless experience across all site components.
Key Benefits:
Comprehensive Site Coverage: By enabling promotion for all page types, organizations can ensure their entire digital presence is synchronized across environments without manual gaps.
Enhanced System Resilience: The implementation of scope-aware identifiers and error-detection spikes prevents broken user experiences caused by missing references or deleted assets during content staging.
We’ve added more flexibility to how you build forms by letting you choose the best interface for every field. You can now switch between different visual styles within the same fragment type—for example, displaying a list of options as a multi-selector checkbox for easy scanning or a multi-selector dropdown to save space. This allows you to customize the user experience to fit your layout perfectly with just one click.
Key Benefits:
Enhanced UX Personalization: Designers can select the most intuitive input method for their audience, such as a drag-and-drop zone for files versus a standard button, without changing the backend data structure.
Streamlined Design Consistency: By offering multiple visual interpretations of the same object fields, the platform allows for diverse form layouts that still maintain strict data integrity and mapping standards.