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.