Now, users are able to visually understand the structure of their objects and how they connect with each other to result in the platform model.

Liferay Labs is an innovation hub within Liferay Marketplace dedicated to exploring newer technologies and developing experimental features. It provides a wide range of useful applications developed by Liferay staff. These are available to the community from Marketplace.

Liferay Labs serves as a platform for rapid prototyping and testing new ideas. These apps may often be integrated as future Liferay features. Under Liferay Labs, you can also find all the legacy apps that are no longer under official support.

All apps offered by Liferay Labs are free but without support. However, you may give feedback on apps containing beta features as it helps in improving them for a future release.

Key benefits:

1. Innovation Hub: serves as a testing ground for new and experimental technologies within the Liferay ecosystem.
Enables rapid prototyping and exploration of novel ideas.

2. Community Access: provides a platform for sharing valuable applications developed by Liferay staff with the broader Liferay community.
Makes these applications readily available through the Liferay Marketplace.

3. Future Feature Roadmap:Acts as a proving ground for potential future features of the Liferay platform. Allows for real-world testing and user feedback on new functionalities before official integration.

4. Legacy Application Repository: serves as an archive for legacy applications that are no longer officially supported. Enables users to access and utilize these applications if needed, while acknowledging their limited support.

Enhance the user experience by allowing users to directly provision cloud applications from marketplace platform, simplifying application deployment.

Key benefits:

1. Streamlining Application Provisioning: Enable users to provision cloud applications directly from the Marketplace platform, eliminating the need for complex manual processes and without leaving the platform.

2. Intuitive User Interface: Provide an easy-to-use interface for installing and uninstalling cloud applications directly from the marketplace, including an intuitive form for inputting necessary information.

3. Efficient License Management: Offer a clear and intuitive interface for managing application licenses, ensuring compliance and optimizing resource utilization.

This release introduces a new Multishipping feature to the storefront, allowing customers to ship parts the same order to multiple addresses with a single checkout. Whether customers are sending gifts to different recipients or shipping products to various locations, the Multishipping feature offers a seamless and flexible shopping experience.

Administrators can allow multishipping in their site through a new configuration in the site’s Channel details page. The customers can access a new “Multishipping” tab in the Open Order Details page to easily manage the Delivery Groups and customize the quantity of each order item for every Delivery Group for the order before the checkout.

Please note that this feature is available through the existing “Commerce Classic Site Initializer” Beta feature flag. To enable it, open the Applications Menu → Control Panel → Instance Settings → Feature Flags → Beta.

Key benefits:

1. Easy to Setup: Multishipping can be activated for your site by enabling “Allow Multishipping” in your site’s Channel Details page.

2. Flexible Address and Delivery Management: Customers can easily set different shipping addresses or different delivery dates for the same address in the context of the same order.

Provided an option to turn the “Out-of-date” feature on/off. When turned on (the default behavior before this release), ongoing publications created in previous Liferay versions were labeled as “Out-of-date” after the upgrade and could not be modified or published. This feature is now off by default, and users can publish these publications without Liferay support.

Key benefit:

Increase manageability over publications and the ability to publish any previous modification, including after Liferay upgrades.

The two separate option menus currently displayed in the Web Content Display widget have been merged into a single, consolidated dropdown menu for content creators. This new menu will improve the user experience by reducing confusion and unnecessary clicks, ensuring all relevant widget actions (e.g., Hide Widget, Duplicate, Export/Import, etc.) are easily accessible.

Until now, there was no way in batch engine to export and import object entries and their permissions simultaneously. This new capability allows users to do that, streamlining workflows and reducing manual effort.

Key benefits:

• Execution in only one call.

• Possibility for users to choose to take into account (or not) permissions with object entries.

The batch engine's export endpoints now support filtering for object entries. This addresses a previous limitation where filtering was not applied to object entries during batch exports. This update ensures consistent data handling and filtering behavior across all entity types.

Key benefits:

• Object entries Personalization
• Equalize capabilities for all entities

Allow applications built on top of Service Builder to leverage the benefits of the Liferay Objects framework

Key benefit:
Applications built on top of Service Builder can now be migrated to Liferay Objects

In order to improve user experience and avoid difficulties with sharing and reporting insights from AC to other members of the organization, we are introducing the Download Reports feature. This functionality allows users to easily download their dashboards as PDFs and specific lists (e.g.: segment membership) as CSVs, streamlining the process of socializing this information with stakeholders.

This new feature provides the ability for the Order Manager to make refunds against on-line payments using the stand alone payment gateway. While the refund amount can be configurable, the refund is always made against the payment method of the original payment.

The Path Analysis tool has been enhanced with the addition of Exit Pages. This feature allows marketers to not only visualize users' entry points (referrer pages), but also their exit points (exit pages). With this user flow analysis, marketers can enhance user engagement and reduce bounce rates.

This feature decouples the payment gateway from the order engine in order to allow you to capture payments against objects and to support new payment methods via client extension.

We have expanded the capabilities of AB Testing to allow the selection of a Collection Display Fragment as the Click Goal of an AB Test. This will allow customers to AB Test the clickthrough rate of different Collections or Collection Providers, empowering them to optimize which content is shown to end users.

Added External Reference Codes for references in widget configurations in Commerce and User Management applications. This helps promote data integrity when pages and their widgets are migrated across environments.

Key benefits:

References within the following page widgets now use External Reference Codes instead of internal IDs:

• Cart

• Cart Summary

• Category Content

• Commerce Addresses

• Commerce Category Navigation

• Mini Cart

• Open Carts

• Option Facet

• Order Forecasts Chart

• Organization Management

• Placed Orders

• Product Comparison Bar

• Product Comparison Table

• Product Details

• Product Downloads

• Product Publisher

• Search Results(Commerce)

• Specification Facet

This feature enhances the filtering capabilities within the headless-admin-user endpoints by enabling filtering based on custom fields for Accounts and Account Groups.

Key benefits:

• Improved Data Retrieval Efficiency

• Enhanced Data Management

• Increased User Productivity

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

This release expands the support of the Timeline History feature to Blogs, Wiki pages, Bookmarks, Forms, Knowledge base, Message boards, and Categories. The feature enhances the publication toolbar with tools to detect and manage collaboration conflicts.

• A timeline icon shows recent modifications in the same asset, which may have been done in production or parallel Publications.

• The user can view, discard, or move these changes directly from the toolbar.

• Warning icons appear to make users aware of current conflicts in the Publication.

Key benefits:

• Enhanced context for content editors and managers for a streamlined collaboration.

• New capabilities to detect conflicts before publishing time, while users may have more time to decide how to resolve conflicts without the go-live pressure.

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.