Release Notes
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:
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.
Data imports, using batch engine, now allows users to preserve content creator information (if required). Previously, imported content with batch was always assigned the user performing the import, resulting in loss of original authorship data when moving content. This update ensures accurate attribution of content ownership (if required).
Key benefits:
Able to keep critical user information during data promotion between environments
Can be configured separately per import process
Implemented proactive access token management with automated email notifications. Users will now receive alerts 1 month, 10 days, and 1 day prior to token expiration, allowing for timely renewal and preventing service disruptions. Notifications are automatically cancelled if a new token is generated.
Key benefits:
Users are notified before token expiration, allowing for timely renewal and uninterrupted access.
Reducing administrative overhead, as automated notifications eliminate the need for manual monitoring and intervention.
By prompting timely renewals, the risk of using expired and potentially compromised tokens is minimized.
The vendor has deprecated OpenSSO/OpenAM, so there's no reason for us to keep it. The alternative, which is PingAM can be integrated using our existing OpenID connector or SAML Authentication.
The SSL Certificate Management view now provides expiration alerts for certificates nearing expiration (e.g., within 30 days) and those that have already expired. Certificates must now be defined exclusively through the LCP.json file, simplifying management and ensuring consistency across deployments. This update reduces manual errors and ensures secure and uninterrupted deployments.
Highlights:
Expiration Alerts: Notifications for certificates nearing expiration and those already expired, with clear visual indicators.
Exclusive LCP.json Configuration: Certificates can only be defined through the LCP.json file.
Improved Visibility: Organized list view showing certificate names, types, associated domains, and expiration dates.
Proactive Management: Tools and alerts to help users maintain secure SSL/TLS configurations.
The Marketplace release of the Liferay Connector to OpenSearch 2 provides an alternative to Elasticsearch for Self-Hosted Liferay deployments.
This connector integrates Liferay DXP with OpenSearch 2.12+, the open source and enterprise grade search engine. OpenSearch offers lexical search for text data, robust scalability and extensibility, and vector search for applications using embeddings, such as Liferay's Semantic Search.
The installation of this app requires specific configurations covered in the official documentation. For detailed compatibility information, see the Search Engine Compatibility Matrix.
The OpenSearch integration is currently a Beta feature with the intention to make it GA in the future.
Liferay Cloud now provides CI/CD support for Client Extensions on Liferay PaaS. Developers can integrate Client Extensions into their Git-based CI/CD pipelines, ensuring automatic builds and deployments alongside core Liferay services. This update enables automated validation, independent deployments, and faster release cycles for Client Extensions.
Highlights:
Dedicated CI/CD Pipeline: Separate build pipeline for Client Extensions to prevent conflicts with core Liferay services.
Automated Builds: Every commit triggers a new Client Extensions build, packaged as a LUFFA archive.
Independent Deployments: Client Extensions builds deploy separately, improving release flexibility.
Seamless Integration: Works with existing Git-based workflows on Liferay PaaS.
Zero Downtime Deployments: Deploy client extensions without affecting the main Liferay service.
Liferay 7.4 introduces the ability to manage language translations directly within client extensions. This enhancement allows developers to provide multilingual support for custom labels and properties without relying solely on OSGi bundles.
Key benefits:
Developers can now define and manage language keys and translations within the client extension itself, ensuring that all labels and custom properties are displayed correctly across different languages.
This feature eliminates the issue of untranslated labels with dashes, providing a consistent and professional appearance on multilingual sites.
Simplifies the process of adding translations, reducing the need for manual intervention and external OSGi bundles, thus accelerating the development and deployment of multilingual features.
Empowers developers to create more flexible and fully localized custom elements and themes, enhancing the overall versatility of the Liferay platform.
Seamlessly integrate cloud payment method apps into the DXP. Allow users to directly download and install these apps available in the Marketplace from within the DXP, eliminating the need to leave the platform. This enhanced integration ensures users have access to a wider range of payment methods, addressing potential limitations that may exist within their current DXP instance.
Available only for Payment Method Free cloud apps.
Note: Before using the feature, ensure that the user has teh right permissions to view and install the payment methods needed.
Key Benefits:
This feature enhances flexibility and convenience for users by allowing them to easily expand their payment method options within the DXP. Users can seamlessly discover, purchase, and integrate new payment methods availbale in the Marketplace directly from the DXP, eliminating the need to navigate external platforms or seek manual solutions. This streamlined process empowers users to quickly adapt to evolving market demands and offer a wider range of payment choices to their customers, ultimately improving their overall user experience.
Publishers can now easily upload and offer low-code fragment configurations via an intuitive workflow on the Liferay Marketplace. In this initial phase, customers can download these fragments directly from the Marketplace. The next quarter will introduce seamless installation of fragments within the Liferay DXP page builder (LPD-34938).
This update also allows publishers to list Client Extensions and Composite Apps on the Marketplace. Customers can then download and install these app types directly into their Liferay instances, following the developer guidelines provided on the app details page.
Key Benefits:
This feature allows buyers to actively select their preferred currency from a list of currencies enabled by the administrator for the specific sales channel they are interacting with. Once a currency is selected, all prices will be displayed in that chosen currency throughout their shopping experience.
Changing the currency automatically creates a new order in the newly selected currency.
Crucially, this feature allows merchants to better manage their international pricing strategies (e.g. smart pricing per currency), fine tuning prices when not relying on exchange rates only.
Key Benefits:
Easy Currency Selection: The new Currency Selector Fragment provides a user-friendly interface for buyers to change their preferred currency at any point during their shopping session.
A new toggle has been added within the Specifications and Product Specifications sections of the admin UI.
This toggle allows Catalog Managers to easily show or hide individual specifications associated with a product. This functionality provides the flexibility to curate the information displayed to customers on product detail pages.
Key Benefits:
Improved Data Accuracy and Relevance: Hide internal or less relevant specifications, ensuring that customers only see information pertinent to their purchasing decisions.
This feature introduces the ability to define and manage custom address types as sub-types of the main address categories—Billing, Shipping, or Billing & Shipping—in Commerce - Account Addresses. This significantly enhances address management flexibility for B2B businesses operating across multiple locations, departments, or stakeholders.
Previously, address management was limited to only two hardcoded types: Shipping and Billing. With this release, businesses can now define additional sub-types (e.g., Ship-to Party, Sold-to Party, Ordering Address, Payer, Disti Branch Officer, DC Delivery Address) through a newly introduced Picklist-based configuration system. These sub-types are configurable and can be mapped directly under one of the three main categories.
This approach ensures compatibility with common ERP systems like SAP, which already support a range of address roles in the order-to-cash process.
Key Benefits:
This release introduces a new Stripe Tax connector, now available in the Liferay Marketplace, designed to integrate directly with Liferay Commerce’s core transaction flows. This connector enables dynamic, automated tax calculation powered by Stripe Tax, replacing manual or static tax setups with an automated, accurate, and globally compliant solution.
Once installed and configured, the connector calculates taxes automatically at checkout based on the buyer’s shipping address and the seller’s tax registration settings. The integration is especially valuable for businesses operating in tax-complex regions like the United States, where tax rates and rules can vary dramatically between states, counties, and even cities.
By leveraging Stripe Tax through this connector, merchants benefit from seamless tax compliance, transparent pricing for buyers, and simplified tax reporting for administrators.
Key Benefits:
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.
It is now possible to view where a document is being displayed on a page.
Key Benefits:
Users now have the ability to update folder names and other details without being able to modify the workflow settings. This ensures there are no security issues and that all content within the folder follows the correct workflow process.
Key Benefits:
Granting “Advance Update” Permissions: Granting “Advance Update” permissions to a role enables the user to update the workflow associated with a folder. The folder's properties, such as name and description fields, remain disabled and cannot be edited.
Microsoft no longer supports Sharepoint versions 2010/2013. See SharePoint Server 2013 - Microsoft Lifecycle and Microsoft SharePoint Server 2010 - Microsoft Lifecycle.This feature has been in maintenance mode for a very long time and there is just a very small user base. Considering the high costs for us in terms of tests maintenance, we decided to deprecate it.
Users can now generate and download a PDF report of their event analysis, enabling seamless sharing of key insights with stakeholders.
Key Benefits: