Feature Status Change

The Akismet is being deprecated and will be removed in the future.

Feature Status Change

With the upcoming move to Jakarta EE 10 and expansion of Client Extensions, DXP is focusing attention a new generation of customization options.

Liferay Faces support for JavaServer Faces (JSF) is being deprecated.

Feature Status Change

With the upcoming move to Jakarta EE 10 and expansion of Client Extensions, DXP is focusing attention a new generation of customization options. PortletMVC4Spring is being deprecated.

Feature Status Change

Deprecating the filter for lastLoginDate on the Headless Admin API because it negatively impacts search performance.

Controlled by feature flag LPD-36010.

New true/false filter hasLoginDate can be used to efficiently check if a user has already logged in to their account at least once.

Feature Status Change

The Liferay Theme tasks are being deprecated and they will be removed in the future. The feature is based in Gulp 4 which is also deprecated. Customers are encouraged to use third party tooling to substitute it.

Feature Status Change

The AMD Loader are being deprecated and they will be removed in the future. Liferay DXP officially supports ESM, which is the official standardized module system for JavaScript, while AMD was a third-party solution.

By adopting ESM, products align with the language's native capabilities and future direction. Modern browsers now natively support ESM, allowing for direct use without transpilation or additional loaders. This can lead to reduced bundle sizes, faster initial page loads and simplified development workflows. This will imply also the deprecation of Liferay-CLI.

Feature Status Change

The Liferay Talend Components feature is being deprecated and will be removed in the future.

Feature Status Change

The functionality for sharing widgets is being deprecated and it will be removed in the future. The feature has been deemed obsolete.

Feature Status Change

The functionality for Most Viewed Assets Collection Providers is being deprecated and it will be removed in the future in light of more advanced Analytics Cloud content tracking.

Feature Status Change

Scope of the widgets in a page: Page, Site or Global is being deprecated and it will be removed in the future.

Feature Status Change

The "Featured Content" contributed fragment set is being deprecated and it will be removed in the future.

When filtering a set of items on a Data Set, sometimes we will be interested in filtering for a field that is part of a relationship.
With this new capability, we enable users to choose to filter by children of complex objects.

Introducing new key improvements to the B2B Guest Checkout experience, enhancing the overall user journey and providing greater flexibility for both new and returning customers.

Guests now have the option to sign in or sign up during the checkout process, directly from the mini-cart. Once logged in, users can either select an existing account or create a new one, ensuring that they can move through the purchase flow smoothly without disruptions. Upon setting the account, guests, now logged-in users, will be redirected to the checkout, making the transition to completing the purchase seamless.

Additionally, if a guest decides to sign in without necessarily checking out, the guest cart will now be merged with their account after logging in. This ensures that any items added to the cart during the guest session are retained when they sign in or select an existing account, improving the continuity and experience for returning users.

Key benefits:

1. Enhanced User Experience: By allowing guests to sign in or create an account directly from the mini-cart, we provide a more intuitive and streamlined checkout process. Guests can complete their purchase with minimal steps, reducing friction and abandonment rates.

2. Cart Persistence: The ability to merge guest carts ensures that items are not lost when guests decide to sign in or register. This improves convenience for returning users and supports a smoother transition between sessions.

External Reference Code is now supported in Currencies.

It is also now possible to use the ERC to update and delete Currencies via their headless APIs.

Additional ERC support for the entities that have a relation with a currency has been added when creating new Catalogs, Channels, Price Lists/Promotions, Orders and Payments.

Key benefits:

• Enhanced Data Management;

• Improved Integration Capabilities;

• Enhanced System Scalability;

• Reduced Errors

Users can access a new Performance tab on the Content Dashboard, which provides detailed metrics for assets, including visitor behavior and the top pages where each asset is featured. Data can be filtered by anonymous or known visitors. These metrics are available for Blogs, Documents and Media, and Web Content and are exclusively accessible to users connected to Analytics Cloud.

• This functionality refers to segments that are static groups of users.

• That said, users can now utilize either user group-based segments or dynamic segments instead of static ones moving forward.

Default View and Download permissions for documents have been adjusted to match the behavior prior to the changes introduced in LPD-16744, restoring the expected user experience.

Highlights: 

• The View and Download permissions will be linked by default when uploading documents through the single and multiple file uploaders

• The Permissions configuration UI is improved so users can more easily recognize that the View and Download permissions are separate permissions

• The Download permission is now automatically included when a user shares a document and assigns permissions

We added several API endpoints for Documents & Media to improve programmatic management of these entities.

Highlights:

• Users can now add, delete, and retrieve document types via headless API (DocumentDataDefinitionType)

• Users can now add, delete, and retrieve document metadata sets via headless API (DocumentMetadataSet)

It is now possible to subscribe to documents and folders, allowing users to receive notifications when they are updated.

Highlights:

• Users can now subscribe to documents and folders through the “Subscribe” action and through the Subscribe icon in the Info Panel

• If a user subscribes to a folder, all documents and subfolders within it will be automatically subscribed to as well

• Users can select and reorder categories for a blog’s friendly URL, so they can preview the order of the categories in the friendly URL and determine how the categories will be presented in the friendly URL along with the title.

• Users are able to set different values for the asset types separators in the friendly URLs. Also, they are able to reset to default value, so for those asset types that they have clicked on this option, the separator will be the value defined by default for those specific asset types.

This set of improvements aims to simplify the manual work users must do to resolve conflicts when publishing a publication. Now, instead of raising a conflict to be resolved manually by the user, the system will try to overwrite conflicting changes in production with the modifications done in the publication, meaning that the Modification and Modification deletion conflict types won’t be presented for the user anymore.

In the case of a Deletion modification conflict, the system won’t resolve it automatically, but now it makes it easier to keep the modifications made in the publication. In the Conflicting changes screen, we added a button with the option to "Restore in Production" for conflicts in which the asset was deleted from production and is now in the Recycle bin.

Key benefits:

• Reduce the amount of manual work by automatically solving most of the conflicts.

• Improve user satisfaction and reliability on publications by ensuring that assets supported by Recycle Bin can be quickly restored, avoiding requiring the user to discard needed changes.

The updated Clay chart colour palette improves accessibility and usability by creating more contrast and adding more variations. Now users can easily distinguish charts, icons, and field sets, reducing confusion and improving clarity.
 

Key benefits:

• Now we have more design flexibility for Liferay’s current and future products.

• Accessible and distinguishable colours that will improve and unify the platform usability and UI.

The addition of new translations and locales ensures that users in regions like Macedonia, Norway, Belgium, Switzerland, and Austria can interact with the platform in their preferred language 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.

This improvement allows users to customise the appearance of their Liferay instance more effectively with new properties in the .yaml file for Theme CSS and CSS Client Extensions.

Key benefits:

• Admins can personalise the interface for both the admin panel and the entire platform.

• A more cohesive, branded appearance will improve usability and satisfaction for all users.

• Allows fine-grained control over where customisations are applied.

To ensure the quality, stability, and modernity of Liferay DXP, we've updated to React 18, bringing significant benefits in security, performance, and compatibility. This update is critical to maintaining DXP's status as a robust and future-proof platform.

Key benefits:

• Security Enhancements: Older library versions can expose vulnerabilities. Upgrading to React 18 mitigates these risks by incorporating the latest security patches.

• Performance Improvements: React 18 introduces features like concurrent rendering, which enhances responsiveness and load handling for better user experiences.

• Enhanced Compatibility: Upgrading ensures DXP aligns with modern tools and frameworks, minimizing integration challenges and future-proofing our development processes.

• Continued Support: Staying current with React’s ecosystem ensures ongoing access to community updates, bug fixes, and innovations.

We’ve introduced robust Content Security Policy (CSP) capabilities to enhance the security of your digital experience platform. This feature supports eight key directives, including script-src and style-src among others, ensuring secure handling of scripts, styles, images, and more. By leveraging these directives, developers can mitigate cross-site scripting (XSS) attacks and data injection risks. The CSP implementation aligns with modern web security standards, offering both flexibility and protection. Administrators can now enforce stricter security policies without compromising functionality.

Key benefits:

• Enhanced Security: Mitigates risks of XSS and data injection attacks by controlling resource loading and execution.

• Compliance-Friendly: Aligns with industry-standard security requirements, supporting stricter compliance protocols.

• Customizable Policies: Allows developers to tailor CSP directives to meet specific project or organizational needs.

• Improved Trust: Strengthens end-user trust by providing a more secure and reliable platform experience.

Official release of Liferay Data Sets, moving from Beta to Release! Data Sets are a powerful and flexible way to retrieve, manage, visualize, and interact with structured data in Liferay DXP. Built on top of Objects and leveraging Liferay’s robust ecosystem, Data Sets exemplify the “build Liferay with Liferay” philosophy. With seamless integration with compatible Headless APIs, administrators can easily configure Data Sets and empower end-users with a rich, customizable experience for consuming and interacting with data.

Key benefits:

• Retrieve Data: Fetch information from any compatible Headless API to use as a Data Set source.

• Manage Flexibility: Administrators can customize what parts of the API response are included, along with filters, sorting options, and available actions.

• Visualize Data: Multiple visualization options make it easier than ever for end-users to consume data meaningfully.

• Enable Interaction: End-users can interact dynamically with data using the filters, actions, and tools configured by administrator

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:

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

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

The Account Selector Customization feature has moved from BETA to RELEASE.

See also Composable Account Selector in the New Features section.

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.

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.

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.

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.

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.

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

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.

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.

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.

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.

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

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

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.

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.

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

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

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.

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.

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.

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.

The headless Search APIs (GET and POST /o/search/v1.0/search) become GA, enabled by default. No feature flag required.

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