Standardized Side Panel Component in Clay React Platform
The newSide Panel (also known as Info Panel) is a reusable Clay React component that provides a consistent, accessible, and responsive sliding panel for use across Liferay applications. It supports common use cases such as content editing, navigation, and contextual information display.
Key benefits:
We established a uniform look and feel across all instances of the Side Panel, reducing cognitive load and improving usability and also ensured compliance with accessibility standards (e.g. keyboard navigation, ARIA roles), enabling inclusive design by default.
Reduces redundant implementations and streamlines maintenance by offering a centralised, reusable component.
Reinforces design consistency and reusability across the product ecosystem.
The addition of new translations and locales ensures that users in Myanmar, Bosnia & Herzegovina, Ireland and Serbia can interact with the platform in their preferred languages or regional variation.
Key benefits:
Tailors the user experience for specific markets and regions, improving relevance and usability
We made the platform more inclusive by expanding language and locale options.
The Accessibility Checker Component is being deprecated as part of our effort to improve accessibility tooling and simplify our component library. After evaluating its usage and overlap with other accessibility solutions in Liferay, we found it to be redundant and we stopped using it long time ago.
Blueprint Collection Provider Extended Type and Subtype Support Search
By displaying the blueprint's results in a Collection Display fragment (available since DXP 7.4 U88 as Beta), you can leverage search to return your assets dynamically, and reap the benefits of the fragments toolbox to lay out the page.
Enhanced Type Support
Now, the Blueprint Collection Provider supports asset types (like structured web content and Objects) allowing to map specific item fields beyond the the basic information fields (i.e., asset entry fields) in fragments, depending on the Searchable Types settings of your blueprint.
When selecting Web Content Article as Searchable Types, the subtype selector becomes available
Selecting an available Web Content Structure (Subtype) as Searchable Types in a blueprint
Web Content Article with a specific Web Content Structure selected as subtype in a blueprint
Mapping a Web Content Structure field from a Blueprint Collection Provider with a specific return type in a fragment
Web Content Article with no subtype restriction selected as Searchable Type in a Blueprint
Mapping Web Content Article field from a Blueprint Collection Provider with a specific return type in a fragment
Document with a specific subtype (Document Type) is selected as Searchable Types in a blueprint
Mapping Document Type fields from a Blueprint Collection Provider with a specific return type in a fragment
Object type selected as Searchable Types in a blueprint
Mapping Object fields from a Blueprint Collection Provider with specific return type in a fragment
Message Boards Message selected as Searchable Types in a blueprint
Mapping basic information fields from a Blueprint Collection Provider with return type Asset in a fragment
Opt-in Collection Provider
Configure if a collection provider should be published when creating a new blueprint, or later via the Configuration tab or through the action menu in the table view in Blueprints.
Enabling a blueprint as a Collection Provider on creation
Enabling/disabling a blueprint as a Collection Provider via Configuration later
Enable blueprint as a collection provide via the action menu in the Blueprints admin
Benefits
Access and map type specific item fields fields in fragments for an extend range of types including Web Content Article and structures, Documents and Document Types and Objects.
Limit searches to specific subtypes via Query Settings in Blueprints
Liferay Self-Hosted deployments can update their Elastic stack to this version. For Liferay PaaS projects a new Elasticsearch image will be provided under Liferay Cloud’s Docker Hub account.
Liferay Tomcat Bundles and Docker Images ship with Elasticsearch 8.18 as the sidecar search engine.
Benefits
The Elasticsearch server runtime included in Liferay DXP Tomcat Bundles and Docker Images (aka. Sidecar Elasticsearch, located under [Liferay-Home]/elasticsearch-sidecar) is provided as a convenience for local development and testing only. It is neither suitable nor supported for production.
Frontend Data Set Cell Renderer CX Upgrade Low/No-Code
Addressing prior limitations, custom cell renderers created with Client Extensions now provide full row data access. This empowers developers with expanded options and greater flexibility for their implementations so they can create a renderer for a cell and include data from all the row mixing the contents. For example, you can create a cell to calculate the volume of a furniture good based on the different dimensions fields.
Benefits
Expand developer capabilities to create more powerful Client Extensions for Data Set Cell Renderers
The Data Set has a revamped experience in terms of selection that also provides a quicker way to contextualize the user interaction.
When facing any of the visualizations (table, card, row) the user can click on the item body to perform single selection. This enhances rapid selection and better interaction.
Benefits
More modern selection pattern that follows industry trends
Clearer states for the user to distinguish when an item is:
With this release, the Liferay DXP is now built with the modern, cloud native technology provided by the Jakarta EE 10 platform. The legacy Java EE platform will no longer be supported on this and future releases, allowing Liferay DXP to continue to evolve and build innovative solutions to meet your business needs.
Benefits
Liferay DXP now certified on Jakarta-based application servers: Tomcat 10.1, Jboss EAP 8.0, and Wildfly 30. This also provides support for newer specifications such as Portlet 4.0, Servlet 6.0, and Spring Framework 6.0. The update paves the way for faster feature development and rapid security fixes available in the modern Java enterprise ecosystem.
PostgreSQL migration now supports all source databases Platform
The Beta feature to migrate databases to PostgreSQL has been updated to support all supported database types. PostgreSQL is the Liferay recommended database server, especially for PaaS and SaaS users and Liferay provides this tool to simplify the migration.
Benefits
Users on MariaDB, SQL Server, Oracle DB, and IBM DB2 are now able to migrate their database to PostgreSQL. The tool was previously limited to users on MySQL. Now all users have access to the DXP and Cloud performance benefits of using PostgreSQL.
The DXP database upgrade process has been enhanced with a suite of verification checks that are executed before any data modifications are made.
These checks have minimal impact on the overall upgrade process execution time, but they can be optionally disabled with the property upgrade.database.preupgrade.verify.enabled=false
Benefits
It can be frustrating when a database upgrade process executes a large amount of modifications to the system and then fails due to a misconfiguration, prompting the need to restore the database and restart the process. Now the database upgrade process will perform a series of configuration checks and report them to the user before modifications are needed. This prevents the need to always restore the database or document library before re-running the upgrade. The upgrade report will still be generated if the preupgrade checks fail, and provide details of any issue.
This feature adds workflow support for Root Models. Child object definitions which are part of a root context will inherit the workflow configurations of the root parent. This simplifies the administration of objects which are part of root model applications.
FriendlyURL support for Object Entries Personalization Low/No-Code
Friendly URLs, also known as clean URLs or pretty URLs, are web addresses that are human-readable and search engine-friendly. They typically use descriptive keywords instead of cryptic file names or query strings. Users can define a friendly URL for entries, making them more human readable and search engine friendly.
Enhanced Batch Deletion Flexibility with External Reference Support at Site Scoped entities Integration
New improvement to make easier the way to promote content among environments. Liferay expands the capabilities of the Batch Engine by introducing a powerful tool for site scoped entities:
Batch Delete by External Reference Code( Site Scoped entities ) – Users can now delete items using external reference codes instead of internal IDs, making batch deletions simpler and more consistent across environments.
Now, covering all scopes, the way teams manage bulk deletions is more simple and safe because it is based on the use of external identifiers so the consistent data maintenance across staging, production, and other instances is possible without changing between environments
Key Business 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.
Context: Both features are part of the “Promote content among environments” strategic initiative.
RESTBuilder generates Jakarta compatible code Integration
Describe the feature:
With the migration to Jakarta, RESTBuilder needed to adapt to be able to generate the classes with the right namespace.
Use the javaEEPackage property to define whether to use javax as namespace (for pre-Jakarta versions of Liferay) or set the value to “jakarta” for newer versions.
Upgrade /siteId and /by-external-reference-code path patterns Integration
In our headless APIs, we have many endpoints with /siteId/{siteId}/ as part of the path for many entities. Now, siteId not only accepts the siteName or the siteId as value, but also the External Reference Code of the site can be used.
Delete Application Data Before Importing in Staging Personalization Integration
Until now, when executing a staging import, users could choose, prior to the import, to delete all existing information in the destination environment. This option has been deprecated due to its low usage (verified directly with clients and partners) and the high risk it entails, as deletion affects not only the elements already in the import but also their related entities. This could lead to the loss of necessary information or the possibility of some entities becoming disconnected from the rest, making both the import and error resolution extremely complicated due to the lack of a list of affected elements. There will not be a substitution, so the alternative will be to delete the elements manually, either from the UI, API or directly in the database before performing the import.
Copy as new update data strategy in Staging Personalization Integration
When executing a staging import, users could choose different strategies to update the data. ”Copy as new” was one of the option, that allow the importer to create new items if they were already in the system. This could lead to create more elements than expecting that later on the user would need to clean. We are deprecating this feature in order to simplify the UI and avoid users to do mistakes.
Extension point for integrating custom CAPTCHA solution/service Security
The Captcha extension point allows customers to integrate custom or third-party CAPTCHA solutions into their system, enabling greater flexibility and control
Key benefits
Removes restrictions on supported CAPTCHA providers
Empowers customers to choose and configure CAPTCHA solutions that best suit their needs
Enhances extensibility and adaptability for diverse use cases and compliance requirements
Just-in-Time (JiT) user provisioning for OIDC and SAML enables automatic synchronization of user data, including user groups at every authentication event. This ensures that user profiles are always up to date
Key benefits
Ensures real-time synchronization of user attributes and group memberships
Reduces administrative overhead by eliminating the need for pre-provisioning
Enhances security and compliance with up-to-date access control
Improves user experience by streamlining access without delays
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:
In-place source code transformation from javax to jakarta for custom development projects using DXP-provided libraries
Liferay-specific dependency mapping
Portlet 4.0 conversion
Integration into Liferay Workspace
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 Liferay Marketplace has undergone a significant architectural enhancement with the formalization and enforcement of Liferay Catalogs. This structure clearly categorizes all Liferay-developed applications, providing explicit transparency on support levels, update schedules, and intended usage.
All Liferay-published applications are now distributed under three dedicated, high-level catalogs:
Liferay Inc.: Contains all fully supported, production-ready applications, including crucial productivity tools, security utilities, connectors, and Experience Management features. These apps follow a strict qcial hub for all new, experimental technologies and potential future core features. Apps in this catalog are not officially supported and are intended for testing and feedback purposes only.
Liferay Community: Hosts officially deprecated applications that remain available for backward compatibility, as well as applications contributed and offered under open-source licenses. These apps receive support until their latest compatible DXP version and follow a quarterly maintenance schedule.
Key Benefits:
Targeted Discovery: Efficiently filter the Marketplace to find specific types of applications, such as mission-critical integration connectors (Liferay Inc.) or bleeding-edge experimental features (Liferay Labs).
Predictable Updates: Rely on the consistent quarterly update schedule for all fully supported (Liferay Inc.) and Community-maintained applications.
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 new Configurable Order Scoping feature gives administrators more control over how orders are displayed on the site. Two new configuration settings have been added within each Channel:
Open Orders Visibility Scope
Placed Orders Visibility Scope
Each configuration offers two visibility options:
Account (default): Maintains the existing behavior, where users can see all open or placed orders across all accounts they have access to, regardless of who created the order.
User: Limits visibility so users only see orders they personally created for the accounts they are part of.
In addition, a new permission—“View Organization Orders”—has been introduced under Orders. This permission ensures that Sales Agents can continue to view all orders associated with their accounts, regardless of the scoping configuration. The permission is automatically assigned to the Sales Agent role by default.
Key Benefits:
Flexible visibility control: Administrators can configure order visibility according to organizational or role-based needs.
Improved data privacy: Restrict order visibility to the creator when required.
Backward compatibility: Default setting preserves existing system behavior to avoid workflow disruption.
Enhanced role management: The new “View Organization Orders” permission ensures key roles, such as Sales Agents, retain appropriate visibility.
The Manage Product Availability at Scale feature empowers catalog managers to efficiently manage individual products through multiple configuration pages containing all catalog’s products. With tools for manual configuration, eligibility-based visibility, and some bulk editing, this feature ensures streamlined operations and enhanced control over product offerings.
New Liferay Headless CMS Content Management System (CMS)
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.
Batch Import/Export for Categories and Vocabularies Content Management System (CMS)
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.
Key Benefits:
Achieve True Content Portability: Facilitate the easy and standardized movement of content architecture (vocabularies/categories) between different instances, crucial for multi-site rollouts.
Accelerate Deployment Pipelines: Ensure fast, reliable, and repeatable promotion of entire content structures between environments, maintaining configuration consistency with minimal manual effort.
Enable Bulk Management & Setup: Quickly bootstrap new environments with pre-defined taxonomies and enable efficient, large-scale bulk editing of existing category metadata via the export-modify-import cycle.
Batch Import/Export for Tags Content Management System (CMS)
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.
Key Benefits:
Achieve True Content Portability: Facilitate the easy and standardized movement of content architecture between different instances, crucial for multi-site rollouts.
Accelerate Deployment Pipelines: Ensure fast, reliable, and repeatable promotion of entire content structures between environments, maintaining configuration consistency with minimal manual effort.
Lazy Reference Support for Tags, Categories and Vocabularies Content Management System (CMS)
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.
Key Benefits:
Order-Agnostic Deployment: Guarantees successful imports by decoupling content from its taxonomy dependencies, allowing content and categories to be deployed in any sequence.
High Success Rate: Prevents import batch failures by automatically creating placeholders, isolating cleanup and ensuring that core content is immediately available.
Analytics Cloud Synchronized User Deletion Personalization
The Analytics Cloud Synchronized User Deletion feature (LPD-45375) has been promoted to General Availability (GA), and its corresponding feature flag has been removed.
This update ensures consistency across platforms by allowing users to synchronously delete users from DXP, with those deletions being immediately reflected in Analytics Cloud.
The Static Segments feature has been formally deprecated and removed from Analytics Cloud. The feature has been under a "deprecation" feature flag for several quarters, and the retirement process is now complete.
The Custom Assets feature has been formally deprecated and removed from Analytics Cloud. The feature had been under a "deprecation" feature flag for several quarters, and the retirement process is now complete.
Preview Display Page Templates in Publications Review Changes Sites
Reviewers can now see exactly how content will appear to end users when using a Display Page Template, ensuring layout and formatting are correct before publishing.
Applies to multiple types of content, including Web Content Articles and Blog Entries.
Reviewers can now see all editable fields for content items in the Data tab — including custom fields created via structures.
Key Benefits:
Improves content quality: Ensures that reviewers can see exactly how content will appear to end users, helping maintain visual and structural accuracy before publishing.
Reduces publishing risks and errors: Allows early detection of layout or formatting issues, minimizing rework and post-publication corrections.
Saves time in the review process: Streamlines validation and reduces the need for multiple review cycles.
Site Settings are now exportable through Headless APIs.
Key Benefits:
Simplified Environment Migration: Easily migrate all site-scoped configurations together with site content using the Batch Engine and Headless Site API.
Greater Consistency: Ensures that site settings and behaviors are replicated accurately across environments.
Enhanced Automation: Supports headless and automated deployment workflows, removing the need for manual configuration updates for site settings.
Usability enhancements for building integrated experiences Sites
With the launch of the new CMS 2.0, two fragments have been created that allow the customers to build a more complete and flexible experience for the end-user. These Accordion and Drag and Drop Upload fragments are better aligned with the real needs of a CMS user and content editors in general, as they allow for improved organization of information and increased usability when managing information and files of any type.
Key Benefits:
Accelerated Time-to-Value: Ready-made fragments allow customers to quickly drag-and-drop functional components, reducing development time and enabling marketing and content teams to create new experiences faster.
Lower Cost of Ownership: Platform-maintained fragments reduce the burden of custom code, ensuring greater long-term stability, easier upgrades, and less time spent on maintenance.
New Fragment to Enable Complex Application Development Sites
With the launch of the new CMS 2.0 and the need to integrate and contribute related objects, a new form fragment has been created. This Form Relationship fragment allows users to populate/fill in nested objects within a form container. With this new fragment, we provide customers with the ability to create more complex forms where they can complete the information for these related objects, thereby offering a more complete experience for the creation of complex applications and for the CMS itself.
Key Benefits:
Maximize Authoring Velocity: By unifying the creation of parent and embedded (repeatable) entities into a single, contextualized screen, customers eliminate clicks and custom code, allowing content teams to publish complex experiences significantly faster.
Ensure Data Integrity: The out-of-the-box fragments enforce data structure and contextual relevance for child entities at the point of creation, guaranteeing consistent, structured content that provides a unified experience for end users.
Support 8-Digit Hex Values in the Style Book’s Editor Personalization
Style Books now support 8-digit hex colour codes (e.g. #RRGGBBAA), which include an alpha channel to define opacity. Previously, these values only worked when set as defaults in the frontend-token-definition.json file; manual input in the editor would strip the opacity digits. With this update, customers can directly enter and save full 8-digit hex values in the Style Book editor, and the opacity is correctly reflected in the UI.
Key Benefits:
User will be able to define colours with both RGB and transparency in a single, standardised format improving Liferay’s design flexibility.
Aligns with modern CSS and browser support for 8-digit hex codes.
No need for more workaround formats (like rgba) to manage opacity.
Enable JavaScript Client Extensions for Administration in SaaS Environments Personalization
In this case, the feature “Enable JavaScript Client Extensions for Administration in SaaS Environments” has remained under Release Feature Flag for three consecutive quarters. During this period, it has demonstrated strong stability, with no reported bugs or user complaints.
Following this evaluation, we’ve decided to move the feature to GA, based on its proven reliability, adoption, and positive feedback.
Semantic Search Support for Custom Objects and Modifiable System Objects Search
Semantic Content Indexing
When the feature flag LPS-122920 is enabled, the platform can now create text embeddings (numerical representations of input text, also known as vector embeddings) for Object entries. These embeddings are generated using the content from the searchable fields and are meant to capture the meaning and the context of the content. You can select from various available third-party providers and models, such as OpenAI or Hugging Face, to generate these vectors.
Customizable Search
Now that semantic indexing is also supported for Object entries, you can create highly customized searches using Blueprints. Specifically, the Rescore by Text Embedding query element is available for use.This element automatically handles the process of creating vectors from the user’s keywords through the configured provider.
For instance, this capability allows you to combine traditional keyword search with AI-powered vector search techniques to implement hybrid search, now also for Object entries. This combination is quickly becoming the new standard for modern content search and discovery.
Key Benefits:
More Relevant Search Results: Create search experiences that understand the meaning and context of your Object based content or application data and user searches.
The Semantic Search capability is planned to be moved to GA status in early 2026. This timeline is intended to outline Liferay’s general product direction and it is subject to change.
From now on most CSS files in Liferay have hashed file names at build time. For example, a clay.css file may appear at run-time with a randomly generated hash value in the name, like clay.(tvERyCVfuRc).css.
This hash value represents a unique version of this file, so the browser can identify that the file's contents haven't changed. This allows the file to remain in Liferay's cache indefinitely.
For those files that can not be hashed, because they are generated in runtime by the server depending on some parameter such as the css tokens, a new onfiguration is available in DXP to configure the TTL and the possibility to add the no-cache header, that ensures the revalidation of the asset with the server before to being served.
Also, hashed files have a fallback strategy based in TTL+eTag if they are called by their canonical name, this is a fallback for error in the import maps or old portlets that doesn’t know the name of a hashed file.
Key Benefits:
The new Liferay DXP caching strategy for CSS files improves performance and stability.
Faster Page Loads: Significant reduction in subsequent load times.
Elimination of Stale Resources: Hashed URLs prevents users from seeing outdated CSS after an update.
Reduced Origin Server Load: Less server overhead as browsers retrieve unchanged files directly from their local cache, saving CPU and bandwidth.
Cache busting: Updated resources automatically force the browser to fetch the new version, but updating their file name with a new hash when content changes.
Maintain Frontend Data Set state in URL Low/No-Code
When a user visits a page that contains a Data Set, there is a certain amount of data that can be altered in some ways:
By filtering the data
By ordering the data
By changing the columns to show on the Table Visualization
By changing the visualization mode
When users navigate away from the Data Set and then return, these unsaved changes are lost, leading to a frustrating user experience.
This feature automatically saves the current view state of a Data Set in the URL. This saved state will ensure the Data Set configuration is consistently recoverable when users navigate back (via browser history or links) and, crucially, that a shared URL provides colleagues with the exact same view.
Key Benefits:
Avoid user frustration: When the user returns to the Data Set they face the same state they had when they left.
Sharing what you see with other users: Users can share the link of a page with a Data Set and the user acessing that very page will face the same Data Set state.
AI Creator Plugin for CK Editor 5 Content Management System (CMS)
As in Ck Editor 4, and to cover the feature parity, the AI Creator plugin has been added to CK Editor 5, so content creators can rely on an AI to create content seamlessly.
Key Benefits:
Accelerate content creation leveraging AI text generation services
Ck Editor 5 Config Contributor Client Extension Content Management System (CMS)
Admins can now fully customize the Rich Text Editor configuration in CKEditor 5 using a new Client Extension. This new extension achieves feature parity with the old CKEditor 4 extension, allowing you to define which toolbars are available across different applications.
Bonus Feature: Unlike its predecessor, the CKEditor 5 extension supports dynamic loading of official CKEditor plugins not included by default in DXP, greatly expanding your customization options.
Key Benefits:
Allow dev users to modify the CK Editor 5 configuration such as new block styles
Allow the dev users to hide plugins such as the options in the editor toolbaar.
Allow users to dynamically add more plugins from CK Editor official showcase.
Allow admins to toggle SPA at instance level Integration
Administrators can enable the SPA feature at instance level
This allow different customers in SaaS to have different configurations as previoulsy it was enabled just at System level (same configuration for several customers)
SPA config at instance level overrides the SPA config defined at System level
Key Benefits:
Mostly SaaS customers can enable/disable SPA in their instance isolately, so Liferay Cloud administrators can defer this configuration to users.
Upgrade Process Automated Database Repair Platform
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.
This epic introduces multi-parent support for Object Definitions, allowing a single child object (e.g., Address) to be associated with more than one possible parent definition (e.g., User or Account). While the definition can support multiple parents, each Object Entry can still only belong to one parent entry at a time, ensuring data consistency.
Key Benefits:
This new feature allows more flexibility when organizing your entries with regards to permissions inheritance.
This feature introduces a new, configurable "On after Login" trigger for Liferay Object Actions. This will empower administrators and developers to define and execute automated processes on Object entries (e.g., creating, updating, or deleting entries, calling external APIs, sending emails) immediately after a user successfully logs into Liferay portal.
Key Benefits:
Faster Time-to-Market: New features tied to user authentication (like automatically creating a user's dashboard data) can be deployed in minutes via the UI, without involving custom development.
Extended Low-Code Power: The Objects framework becomes more valuable by handling a critical part of the digital experience—user sign-in—without needing traditional coding skills.
Real-Time Data Integrity: Ensures that user-specific custom data (like status, last login date, or personalized onboarding tasks) is created or updated instantly and automatically upon login, keeping all systems synchronized.
Subscriptions for Objects Content Management System (CMS)
This feature allows users to subscribe to entries to receive notifications when entries are updated. This addresses the need for real-time awareness and governance over content and data
Key Benefits:
Enhanced Data Integrity and Compliance: Users who rely on specific documents, legal disclaimers, or data records can be confident they are instantly alerted when that asset changes.
Audit Trail and Accountability: Notifications tied to events like Asset Updated or Asset Expired create an automated audit trail. The system ensures that stakeholders know when and what was changed, improving accountability across teams.
Reduced Notification Fatigue: By automatically inheriting the subscription status, the UI can prevent users from double-subscribing, which cleans up the interface and reduces unnecessary email clutter.
