To reduce confusion and improve transparency for SaaS customers, we’re updating the Analytics Cloud usage limits page. SaaS users will now be redirected to the Customer Portal when they access the Usage Limits menu in AC. This ensures they see the correct consumption metrics associated with their plan: Anonymous Page Views (APVs) and Monthly Active Logged-In Users (MALUs) as previously, the usage page displayed default limits based on Page Views (PVs) and Known Individuals (KIs), which do not apply to SaaS customers.

Highlights

1. Redirect for SaaS users: SaaS customers are now redirected to the Customer Portal when accessing the "Usage Limits" page in AC.

2. Accurate metric display: Customers will see the correct usage metrics—APVs and MALUs—instead of outdated PVs and KIs.

3. Eliminates confusion: Removes misleading limits that previously appeared for SaaS users.

To prevent token duplication in lower-level environments, we’re introducing a new portal property. When set to true in the portal-ext.properties file, this property will automatically clear the AC connection on startup. This ensures that if the production token is copied to a UAT environment during migration, it will be removed on startup—preventing data contamination, eliminating the need for manual disconnection, and preserving the integrity of the AC connection in production.

Highlights

1. Prevents data contamination between environments

2. Eliminates the need for manual disconnection

3. Preserves production data integrity

Analytics Cloud Cookie Control (LPD-10588)

Utility page for cookie policy lists and describes all cookies in use. Users can add and update cookies in the list with the cookie object. When the cookie manager is enabled, Analytics Cloud only tracks data from users who consent to statistics cookies.

This feature introduces customizable permissions for the "Owner" role and other user roles within Publications, allowing administrators to define exactly who can publish, edit, invite users, or manage permissions at the publication level. A new "Permissions" section has been added to the "Enable Publication" settings, along with an "Edit Permissions" button that opens the Publication permissions modal. Admins can now revoke the "Publish on Production" permission for any user on a publication-by-publication basis. Once revoked, the change is reflected immediately, the user will no longer be able to publish content to production, and the revoked status is saved and visible in the publication permissions settings. Only users with the Admin role or the specific permission to manage publication roles can make these changes. This enhancement provides granular control over user capabilities within each publication, helping teams better manage their content workflows and avoid accidental publishing.
 

Key benefits:

• Safeguard Production Changes: Blocks users from publishing or modifying production content via Publications unless explicitly granted.

• Enhanced Role Governance: Admins now have complete oversight of publication-level permissions for all user roles, including Owners.

A new warning has been added to the Publications configuration screen to alert admins when "Sandbox Only" mode is enabled but publication Owners still have permission to publish. In this scenario, any user who creates a sandbox publication can still push changes to production, potentially bypassing the intended protection. The system now displays a warning message when this configuration is detected, guiding admins to review and adjust permissions for the Owner role accordingly.
 

Key benefits:

• Prevent accidental publishing by alerting admins when Owner permissions still allow publishing in Sandbox mode.

• Increase visibility into role-based permissions that may unintentionally allow production changes.

We enabled navigation menus to be retrieved using their External Reference Code (ERC) through Liferay’s headless APIs. This enhancement enables a more precise and consistent identification of navigation menus across sites and environments, particularly useful in multi-site and content migration contexts. It complements the existing functionality by providing an alternative for IDs.
 

Key benefits:

• Improved data consistency: ERC-based retrieval ensures references remain valid across environments.

• Easier data migration: ERCs streamline the export/import process across different Liferay sites by providing a consistent identifier.

• Better filtering options: Admins can now export navigation menus based on creation or modification date range, giving finer control over headless operations.

As customers increasingly adopt HTML5 for content creation, there's a growing need to upgrade the current rich text editing capabilities and CKEditor 5 has been selected as the default editor for Liferay DXP to meet this demand. CK Editor 5 has been made available in DXP under Beta Feature Flag. (FF-11235):

• Web Content Description field

• Page Builder:

  • Paragraph

  • Forms → Rich Text

To help users build pages faster with more design options, Liferay now allows direct access to Marketplace fragments from within the page builder. In addition to native and already-installed fragments, users can now browse and install additional fragments available on the Marketplace—expanding their library without leaving the editor.

This gives customers the ability to use pre-built fragments shared by Liferay, technology partners, and the broader community, making it easier to create flexible, high-quality pages with less effort.

Users can translate text fields from Objects when using Text Input Fragments in Form Containers.

Dynamically show or hide configuration fields in a custom fragment based on user input values.

With the introduction of the new CMS approach for managing object entries, the existing 1:1 nested object entry functionality in the Page Builder (LPD-20213) is now deprecated and will be removed. This feature has proven to be complex and underutilized by end-users.

The new approach, being developed under the CMS 2.0 initiative, will offer a more intuitive user experience for object relationships, allowing users to configure child structures as repeatable or non-repeatable.

The new Side 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.

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

Description

• Embedded items now include actions (when the headless entity supports)

• Filter by Workflow Status via the filter request parameter.

  • Filter field: status

  • Examples: status eq 0, status eq 0 or status eq 2

Benefits

• Invoke available actions on the returned items

• Filter results by workflow status

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.

Deployments can operate their stack using the latest available, secure and stable version of OpenSearch 2.

Requires to install Liferay Connector to OpenSearch 2.

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.

Instead, configure Liferay to connect to Elasticsearch as a self-managed, standalone server or cluster of server nodes. 

Collections with Blueprints (FF: LPS-129412) available as since DXP 7.4 U88 is now in RELEASE status and can be enabled via Feature Flags > Release.

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:

  • Selected (active)

  • Hovered

  • Both at the same time

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.

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.

Allow users to call the {scopeKey} using the external reference code when creating a custom object with site scope.

Ex: /scope/{scopeKey}/...

Now, ID, Name and ERC are supported for scopeKey.

Users can now refer to their custom external reference codes for sites when interacting with object endpoints.

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.

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.

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.

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.

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.

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.

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.

There will not be a substitution.

The Captcha extension point allows customers to integrate custom or third-party CAPTCHA solutions into their system, enabling greater flexibility and control

Key benefits

1. Removes restrictions on supported CAPTCHA providers

2. Empowers customers to choose and configure CAPTCHA solutions that best suit their needs

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

1. Ensures real-time synchronization of user attributes and group memberships

2. Reduces administrative overhead by eliminating the need for pre-provisioning

3. Enhances security and compliance with up-to-date access control

4. Improves user experience by streamlining access without delays

We improved the password reset function on the Forgot Password Utility Page to prevent it from redirecting users to the old Forgot Password page.

Key benefits

Consistent page experience

The FF changes from Beta to Release

Users now have more access to several more metrics on their metrics page. Improving their visibility and troubleshooting capabilities.

Highlights

• New metrics visible in the metrics page;

• New metrics improve visibility of platform and infra elements, greatly speeding up troubleshooting and understanding of platform behaviour.

• The selection of metrics leverages our deep understanding

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:

1. In-place source code transformation from javax to jakarta for custom development projects using DXP-provided libraries

2. Liferay-specific dependency mapping

3. Portlet 4.0 conversion

4. Integration into Liferay Workspace

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

You can now have access to the event’s details when selecting a calendar event and be redirected to the already existing details page of that particular event. It is also possible to map a Calendar Event’s specific URL, along with some other fields, in order to use it in emails so the recipient can click on it and be redirected to the Event’s details.

We're introducing advanced script loading options for JavaScript Client Extensions in Liferay, providing developers more control over how JavaScript is applied to pages. This update allows the specification of async and defer attributes directly in the extension's configuration, optimizing the loading process and improving page performance.
Benefits for users:

• Improved Page Load Performance: by setting async or defer attributes, scripts can be loaded non-blocking, enhancing page responsiveness.
• Enhanced Control: developers can pre-set these attributes in the YAML configuration or through the UI, ensuring scripts behave consistently across all pages without further adjustment.
• Streamlined Configuration: once set, these attributes are locked at the extension level, eliminating discrepancies and simplifying script management.

Allow developers to specify additional attributes to the <script> tag when deploying in with the JS Client Extension.

Example usage in client-extension.yaml: liferay-portal/workspaces/liferay-sample-workspace/client-extensions/liferay-sample-global-js-2/client-extension.yaml at master · liferay/liferay-portal

    scriptElementAttributes:
        async: true
        data-attribute: "value"
        data-senna-track: "permanent"
        fetchpriority: "low"

Or, developers can configure the attributes via the create Client Extension UI too:

When configuring a JS CX on a page and async/defer Boolean attributes are present in the CX (set in the yaml / defined through the UI), the following behaviors apply in regards to the Load type options:

1. The attribute set in the CX will be used and the ability to change it when applying it on a page will be disabled.
2. When both attributes are set in the CX, async will be applied.
3. When async or defer is set to false in the CS, the related option will be removed from the Load selector. (e.g. if defer: false the load options available for the user will be default and async).

This feature introduces the capability to connect Liferay Objects with SugarCRM Objects, empowering users to synchronize and store their data efficiently between the two platforms. By bridging these systems, users can streamline their workflows, enhance data consistency, and leverage the robust features of both Liferay and SugarCRM.

Users can now, with low effort, connect their Liferay and SugarCRM environments, eliminating the need for manual data transfers and reducing the risk of errors. This enhancement not only simplifies data management but also enhances the overall user experience by providing a cohesive and integrated ecosystem for managing customer data.

We have improved the behaviour of an existing configuration to be able to properly publish a child page in a Staging process to Live site without its parent(s). This also improves the performance of publishing changes.

It is now possible to select Date Times as a product option type, configuring purchase options for products based on date, times, time zones, and durations, allowing for the sale of time slots.

Manage contacts directly related to accounts like phone numbers, emails, websites, addresses.

A new Contact Tab in Account details page with 2 internals tabs was created:

1. Addresses
2. Contact Information

Users with “Accounts > Account Entry: Manage Addresses” permission should be able to manage their contacts with all these actions:

• Add
• Edit
• Remove
• Mark as primary

Example of managing a phone number:

Users without “Accounts > Account Entry: Manage Addresses” permission should be able to only view the existing phone number entries.

The Server Administration interface provides powerful tools for controlling the server. As an added layer of security, CAPTCHA is now required for actions in Server Administration pages and the Gogo Shell page. Due to the sensitive nature of these controls, the system will still enforce CAPTCHA on these pages, even if the “Maximum Challenges” configuration is set to a negative number.

We are constantly working on improving performance of Publications. We have implemented improvement for Timeline and Conflict checking icons.

If a conflict appears between the scheduled publication and Production before or during publishing stage, we have added a functionality to provide more information inside Liferay notifications when this situation occurs.

This features creates a reviewer role that has read-only (and no update) permissions. It grants permission to review the draft of a content page, or the pages that are submitted through a workflow and are still pending approval and publication.

Page Creator now can efficiently manage permissions for their website, distinguishing between public and restricted pages. Key functionalities, such as unique designs and restricted access, are incorporated seamlessly.

Requirements include easy identification of page visibility, bulk permission management, and configuration options for both individual pages and entire branches.

Provide the option at Instance and Site settings to the XML sitemap to allow customers to customize the inclusion or exclusion of content according to the SEO technical requirements.

When the User reaches Control Panel → Instance Settings, a new menu item (SEO), under Platform, will be shown. By accessing this menu, the user will be able to include/exclude different content.

When the user has Download permission on a file, then the Documents and Media File result features a download link in the Search Results widget in all out-of-the-box widget display styles.

The Search Results widget Template Context has received a new field to obtain the download URL in custom display templates: ${entry.getAssetRendererURLDownload()}

Part of the recurring compatibility testing, Elasticsearch 8.13.x has been added to the compatibility matrix to the corresponding Liferay versions.

Note: Compatibility with newer Elasticsearch minor versions is always tested in two ways:

1. Latest-Latest: Testing the latest Liferay version with the latest available minor version of Elasticsearch → e.g. Master/2024.Q2 + Elasticsearch 8.13

2. Minimum-Latest: Testing the minimum Liferay version where Elasticsearch 8 compatibility was first made available with the latest minor version of Elasticsearch → DXP 7.4 U81/DXP 7.3 U31 + Elasticsearch 8.13

This way we can not only provide compatibility for the latest Liferay versions, but also backwards compatibility, allowing a broader customer base and deployments to operate their stack with an up-to-date search engine version.

As Elasticsearch is usually released a new Minor version roughly every two months, this is a recurring process and a planned activity for our team.

Liferay ships with an updated Elasticsearch connector using 7.17.18 as the client version. It is also for the development and testing purpose for Sidecar server.

The solution involves implementing advanced filtering options on the Builds and Deployments pages of the platform. This feature allows users to filter builds and deployments by key parameters such as date and environment. It is structured as following:

1. Date Filter: users can select a specific date or a date range from a calendar interface. This allows to view builds and deployments that were created or modified within that timeframe, facilitating quick access to historical data or recent updates.

2. Environment Filter: this filter enables users to select from pre-defined environment options (e.g. development, testing, production) viewing only the builds and deployments relevant to the chosen environment. This is particularly useful for teams managing multiple environments and needing to track their respective changes efficiently.

For custom objects, we have add the possibility to upload and save an attachment file in only one step. As another field of the entry, users can upload directly a document to an attachment field using Base64 format.

"AttachmentField1" : {

       "fileBase64" : "iVBORw0KGgoAAAANSUhEUgAAAD0AAAAXCAIAAAA3N9DuAAAAA3NCSVQICAjb4U/gAAAAEHRFWH",         "name" : "file.png"

}

And, to recover the values of the entry, they can do it in the same format using nested fields.

curl -X GET \ -u 'test@liferay.com:test' \ 'http://localhost:8080/o/c/mytestobjects/by-external-reference-code/users-computer-attachment-1?nestedFields=usersComputerAttachment1.fileBase64'

For sure, the previous options of uploading and downloading files of an entry are available too so the user can decide which to use in any case.

Until now, in GraphQL, it was not possible to create a query (or mutation) where the user could select the version to execute. Besides that, in case more than one endpoint had the same name but in different applications, you couldn’t select which one to use.

In order to make queries and mutations unique in GraphQL, we have created a new structure using a namespace with the following format:

Path + “_” + “v” + MayorVersion + “_” + MinorVersion ( 0 by default ).

query {

             structuredContents(siteKey: "20117") {

                    items {

                           title

                    }

              }

       }

VS

query {

         headlessDelivery_v2_0 {

                structuredContents(siteKey: "20117") {

                         items {

                                 title

                                    }

                          }

              }

}

Feature Status Change

New link added to the chart from the organization management admin pages. Chart now supports search functionality. Users with permissions can view or edit more details of the Organization, Account or User when it is selected on the chart.

Feature Status Change

The ability for a buyer or sales agent to edit a product bundle directly from the mini-cart has now been added. Previously, if a change had to be made the bundle had to be deleted from the cart and added again. This allows for more speedy alterations to be made before proceeding with check out.