これで、特定の行動に基づいて、より詳細な顧客セグメントを作成できるようになった。 セグメンテーション機能を拡張し、標準的なウェブサイト活動だけでなく、カスタムイベントを含むオーディエンスのセグメンテーションが可能になりました。

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:

• Enhanced Efficiency and Governance: Achieve immediate content visibility and streamlined collaboration by centralizing assets into a single, unified view. Rigorous versioning and workflow controls ensure consistent content quality and compliance across the organization.

• Maximum Agility and Portability: Leverage a modern headless-first, API-driven architecture (REST/GraphQL) that makes content fully portable, ensuring instant readiness for distribution and maximum reach across all your digital channels.

• Measurable Performance and Data-Driven Strategy: Empower content owners with embedded analytics and strong preview capabilities, enabling teams to make instant, informed decisions that drive superior business outcomes.

A new set of fragments has been introduced under a dedicated category called “Account Selector.”.

These fragments allow to compose and customize the account selector according to their specific business needs.

Here is a list of the newly added fragments for building the account selector:

• Account Selector: this fragment is the main orchestrator of the entire component, handles the communication with external components, the dropdown mechanism and the panels(up to 5 can be configured), and manages the main drop zone areas

• Account Selector Button: OOTB available Account Selector call-to-action

  (preserves the current logic for page/component refreshes), used to open/close the account selector(any custom button hooked up with the Javascript business logic can be used).

• Account Selector Panel: this fragment can be drag-and-dropped inside the Account Selector’s panel drop zone (each panel is a tab that can be navigated in the dropdown) and creates a drop zone to place account-related views

• Accounts Data Set: Data Set fragment to display the list of selectable accounts for the current user

• Create Account Button: configurable call-to-action that allows the creation of new accounts, maintaining the existing Account Selector flow.

• Account Orders Data Set: Data Set fragment to display the list of selectable orders for the current account

• Create Order Button: configurable call-to-action that allows the creation of new orders, maintaining the existing Account Selector flow.

A fully configured Account Selector is also available out-of-the-box (OOTB) in the Commerce Classic Site Initializer (LPD-20379).

Key Benefits:

• Flexible Customization: Easily tailor the account selector to match your site’s structure and user needs.

• Improved User Experience: Enables intuitive navigation and personalization of account-related views.

• Configurable Control: Enable or disable specific features and interactions without custom development.

The Liferay database upgrade process has been enhanced with automated database repair routines to improve the speed and reliability of DXP upgrades.

During the upgrade process, these routines automatically identify and correct common database inconsistencies or missing references.

These repair routines are targeted at known issues with data structures only, keeping your critical data content safe. Details of these repair processes are provided for review in the Liferay Upgrade Report after a database upgrade completes.

Key Benefits:

• Faster upgrades

• Minimize risks for current and future upgrades

• Automates data maintenance

An MCP Server acts as a bridge between your solution and AI models. For us, the new Liferay DXP MCP Server exposes our Headless APIs through a standardized interface that LLMs can understand and interact with allowing them both to retrieve information, but also interact with Liferay DXP to create or update different types of entities.

Key Benefits:

• MCP is a standard protocol that allows users to integrate easily Liferay DXP to any compatible AI ( like ChatGPT, Gemini, Github Copilot, etc ), reducing implementation and maintenance costs.

• Because MCP defines a standard protocol, AI models can reliably query, call functions, and retrieve data in structured ways (JSON schemas, typed responses, etc.).

• Leveraging the Headless APIs in the MCP server, we ensure that our permission system enforces that LLMs access only the information the user making queries can access.

Easier Content Management, Headlessly 

With Liferay’s new Headless CMS, you can create, organize, and publish content across multiple channels easily in a single interface. With a unified content creation and management experience, you’re able to: 

• Go to market faster by reusing content across different sites, pages, and channels through APIs. 

• Use flexible content structures or even define custom structures without any coding knowledge. 

• Streamline collaboration with shared spaces and built-in publishing workflows. 

Eliminate Data Silos with HubSpot Lead Connector 

By creating a seamless, automated bridge between Liferay DXP and HubSpot CRM, you can ensure that every new contact, company, and lead captured in Liferay DXP is instantly synced and ready for your next campaign. 

Easily Promote Content Among Environments 

Transfer data and content across environments safely and reliably. Through a significant change to the infrastructure, users are able to: 

• Move elements that use the new infrastructure at the instance level, such as Object Definitions, Picklists, or Roles, and freely export and import Object Entries with any scope.

• Use partial imports to avoid blocking users in the case of errors. 

• Receive clearer error messages that give the user full control to recover from errors and missing references.