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.

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

2. Elimination of Stale Resources: Hashed URLs prevents users from seeing outdated CSS 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, but updating their file name with a new hash when content changes.

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.

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

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.

• 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.

When administrators turn on CKEditor 5 feature flag (LPD-11235), the Email Configuration will use CKE5 as the default text editor.

Key Benefits:

• Consistency across DXP, enabling the CK Editor 5 is offered in one more experience that now is covered.

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

The following database versions have reached end of life from their vendors and are now under deprecation for DXP:

1. DB2 11.1

2. MariaDB 10.2

3. MariaDB 10.4

4. MySQL 5.7

5. PostgreSQL 12.x

6. PostgreSQL 13.x

7. SQL Server 2017

Please refer to the 2025.Q4 compatibility matrix for the full list of supported Databases.

The following Operating System versions have reached end of life from their vendors and are now under deprecation for DXP:

1. CentoOS 7

2. CentoOS 8

3. Debian 10

4. Debian 11

5. Oracle Linux 7

6. Red Hat Enterprise Linux 7

7. SUSE Enterprise Linux 12

8. Ubuntu 18.04

9. Ubuntu 20.04

Please refer to the 2025.Q4 compatibility matrix for the full list of supported Operating Systems.

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.

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.

Users are able to configure email and user notification templates to be sent to User groups, delivering significant benefits centered on efficiency, audience segmentation, and reduced administrative burden.

Key Benefits:

• Massively Improved Communication Efficiency: Eliminates the tedious, error-prone task of manually managing recipient lists.

• Precise Audience Segmentation: Ensures the right information reaches the right functional segment of the organization

• Clean Data and Reduced Notification Fatigue: by resolving users who are members of multiple selected groups. This keeps inboxes clean and reduces notification fatigue, making the alerts that are sent more likely to be read and acted upon

This release introduces the foundational layer for versioning object entries within the Liferay Objects framework. Versioning allows teams to track the full lifecycle of data changes, revert entries when needed, and ensure auditability — a key requirement for organizations dealing with regulated or collaborative content.

In this first phase, the versioning capability is available exclusively via API, giving developers immediate access to version history, preview, and restore operations. A dedicated configuration in Object Admin allows administrators to enable or disable versioning per object definition.

Key Benefits:

• Versioning brings greater control and safety to object data by keeping a full history of every change. It allows teams to recover previous states, avoid data loss, and meet audit or compliance needs. With API-first access, developers can immediately start using version history, preview, and restore in their applications

This release introduces scheduling capabilities to object entries, allowing users to define when an entry should go live, expire, or be reviewed. This brings Objects closer to real content lifecycle management — similar to what already exists in Web Content — and enables automation for time-sensitive data.

With this feature, object entries can be activated or deactivated automatically based on predefined dates, and optional review dates help teams stay compliant with legal, operational, or business rules.

Key Benefits:

• Scheduling gives users more control over when content or data becomes visible, expires, or needs review — reducing manual work and improving timing accuracy. It helps teams automate recurring tasks (such as publishing promotions or removing expired assets), avoid compliance risks, and ensure content stays up to date. With built-in notifications, users are always informed of upcoming actions, making lifecycle management simpler and more reliable.

This release introduces a new configuration that allows the owner of an Object Definition to decide whether it can be used inside Form Containers in Page Builder. While objects could already be mapped to forms before, administrators now have explicit control over which objects are exposed for page-level form experiences.

This provides a governance layer that helps avoid accidental exposure of internal, sensitive, or system-bound data structures, while still allowing selected objects to participate in dynamic form experiences when desired.

Key Benefits:

• This configuration gives object definition owners full control over whether their data can be used in Page Builder forms, improving security, reducing clutter in the selector, and preventing misuse of objects that were never intended for page-level experiences. Teams can now allow only the right objects to power form-based experiences, while keeping internal or backend-only objects protected.

This release introduces a new Assignee field type for Liferay Objects, enabling entry-level ownership and task assignment. With this field, object entries can now be assigned to Users or Roles, making Objects suitable for workflow-style, task-driven, and ownership-based applications.

Once assigned, the user or role automatically gains permission to edit the entry, even if they did not previously have it explicitly. This makes it possible to build review flows, approval processes, service desks, onboarding pipelines, partner applications, and more, all using native Objects.

Key Benefits:

• The Assignee field brings native task ownership to Objects, allowing teams to build assignment-based processes with automatic permissions, "My Entries" filtering, and full API and UI support. This reduces the need for custom logic, enables clearer responsibility tracking, and unlocks use cases like approvals, case management, service requests, onboarding workflows, and more.

This feature introduces a new permission that allows object administrators to control who can download files attached to object entries. With this enhancement, each attachment field can define its own download permission, ensuring that only authorized users are able to retrieve files — without blocking visibility or access to the entry itself.

Key Benefits:

• This feature adds granular control to file downloads, allowing administrators to manage who can retrieve sensitive attachments without restricting access to the rest of the entry. It improves security, supports compliance workflows, and aligns Object attachments with the permission flexibility already available in Documents & Media.

The FF changes from Released to GA