Feature Status Change

Enabling this feature will allow users to work with base64 format in object attachments fields.

Feature Status Change

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

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.

This feature allows warehouse managers to define granular eligibility rules for accounts and account groups to access specific warehouses. This enables fine-grained control over which customers can see and purchase inventory from which warehouses.

Key benefits:

1. Improved Inventory Management:

• Prevent unauthorized access to inventory data.

• Strategically control product visibility based on inventory quantities and stock levels.

• Optimize inventory allocation across customer segments.

2. Enhanced Customer Experience:

• Provide a more relevant and personalized shopping experience.

• Improve customer satisfaction by prioritizing access for key customer segments.

3. Increased Revenue:

• Generate higher revenue from valuable customer segments by prioritizing their access to inventory.

4. Reduced Lost Sales:

• Minimize lost sales due to stockouts by limiting product visibility for certain customer groups.

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 enables users to export a CSV file containing detailed information about segment membership, including a list of all known individuals within a segment and their associated data, providing valuable insights for stakeholders.

Highlights:

• Export Capability: Allows users to generate a CSV file containing segment membership data.

• Comprehensive Details: Includes a list of all known individuals in a segment, with details such as names and email addresses.

• Actionable Insights: Equips stakeholders with valuable data for analysis and decision-making.

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.

Feature Status Change

The Social Networking Plugin 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

The Invite Members Widget 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. PortletMVC4Spring is being deprecated.

Feature Status Change

Users can easily identify components that may cause performance issues in their Pages. We have added a new tab on the Page Audit to show the users the back-end render times of the different components, as well as warnings to help identify specific components configurations that may lead to performance issues. Those warnings also appear on the Edit mode, so the user is aware of possible issues during the page creation.

The AI Assistant is a versatile and powerful tool designed specifically for content creators to enhance their productivity and streamline workflows. By centralizing AI-driven content creation into a single, easy-to-use application, the AI Assistant simplifies the process of generating and managing diverse types of content. Whether you're working on blogs, Knowledge Base articles, or page layouts, the AI Assistant offers the tools and flexibility to help you work smarter and faster—all in one place.

Availability: The AI Assistant is a cloud-based application readily accessible on the Marketplace, making it easy to integrate into your existing digital ecosystem. Its cloud infrastructure ensures reliable performance and scalability, providing users with consistent and seamless access to its capabilities.

Feature Status Change

The Asset Publisher widget is going into maintenance.

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

• This functionality refers to tracking events related to non-default asset types and visualizing the data on a dashboard. From now on, customers will no longer be able to use this specific method to track views of non-default asset types and visualize this data on a dashboard in Analytics Cloud

• Using custom event tracking is the recommended way to track your custom assets from now on.

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

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.

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

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

Previously, when managing complex data models, users must create scripts or code in order to make changes to multiple related objects. Now users are able to configure multiple objects as if they are one object. Related child objects now inherit permissions and account restrictions and more from the top level parent, making object management more convenient.

Key benefits:

Simplifies the management of multiple objects through a configuration on the relationship between objects

• Permissions and Account Restrictions for the child objects are inherited from the Top level parent

• API endpoints are nested under the same namespace of the top level parent

Allow users to move Object Definitions and Entries between environments

Key benefit:
Addresses a feature gap when moving applications built on Liferay between environments

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

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:

• Automated Real-Time Tax Calculation
  Eliminate manual tax logic. Taxes are calculated dynamically during checkout using Stripe’s robust tax engine, ensuring accuracy based on product, location, and applicable tax laws.
• Supports Complex U.S. Tax Scenarios
  This is particularly beneficial for merchants selling into the U.S. market, where tax complexity is high. Stripe Tax automatically accounts for state, county, and city-level rules—reducing the burden on sellers.
• Improved Buyer Experience
  Buyers see clear tax breakdowns at checkout, building trust and preventing cart abandonment due to surprise charges.
• Streamlined Operations for Sellers
  Taxes are included in transaction records without seller intervention. Sellers can access tax-inclusive transaction histories and focus on business growth.Streamlined Operations for Sellers
  Taxes are included in transaction records without seller intervention. Sellers can access tax-inclusive transaction histories and focus on business growth.

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:

• Flexible Address Management: B2B businesses can model complex customer hierarchies and logistical operations with precision. Define specific address roles that align with real-world use cases without being restricted to just billing and shipping.
• ERP Integration Ready: Custom sub-types allow seamless data synchronization with ERP systems like SAP, avoiding manual workarounds and ensuring that address roles like Sold-to, Bill-to, and Ship-to are preserved in external systems.
• Improved Order Fulfillment & Compliance: Tailoring address types to real operational needs supports more accurate order routing, fulfillment, and financial processing, while also aligning with internal compliance and invoicing requirements.

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.

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. In this release CK Editor 5 has been made available in DXP and installed in four different experiences under Beta Feature Flag. (FF-11235):

• Web Content

• Object entry (editing a Rich Text Field)

• Document Types (when adding a Rich Text field)

• Metadata Set (when adding a Rich Text field)

• Forms

• Element Sets

After this, CK Editor 5 will be included in other areas and experiences in the near future:

• Page Builder

• Commerce

• Web Content Description

Key Benefits:

Benefits when CK Editor is available across all DXP, note that current effort only includes Webcontent

1. Support modern web standards, including HTML5 and Content Security Policy (CSP).

2. Provide a seamless copy-paste experience from external tools.

3. Leverage OOTB features like the inline editor for a more flexible editing workflow.

4. Adopt a supported and actively maintained version of CK Editor.

5. Remove reliance on multiple editors and standardize the editing experience across Liferay DXP.

More highlights and benefits here

Improved the usability, functionality, and consistency of bulk actions in Frontend Data Sets across Liferay DXP. The selection behaviour of items has been refined, ensuring consistency in visualization modes, enhancing bulk action visibility, and making interactions more intuitive and efficient for end users.

Key Benefits:

• Preserve selection between pages of items so the user can easily select items from multiple pages.
• Add Select All and Clear buttons to allow users to easily work with large amount of items.
• Added contextual menu with access to all bulk actions available.
• Highlighted bulk actions to easily access more common actions.

Managing and synchronizing content across multiple environments just became easier and more reliable. With this release, Liferay expands the capabilities of the Batch Engine by introducing two powerful enhancements:

1. Batch Delete by External Reference Code – Users can now delete items using external reference codes instead of internal IDs, making batch deletions simpler and more consistent across environments.

2. Import Strategy Support for Deletion – When performing a batch delete, users can now define whether the operation should be partial (stop on error) or complete (continue even if some items fail), offering more control and fault tolerance during the process.

Together, these updates streamline how teams manage bulk deletions—especially in environments that rely on external identifiers or require consistent data maintenance across staging, production, and other instances.

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

We made sure to be able to configure the most relevant SCIM providers by implementing their specifications(Microsoft Entra, Cyber Ark, etc.)

Key Benefits:

Implementing SCIM endpoints from top identity providers streamlines and secures user management by enabling automated provisioning, deprovisioning, and syncing of user data across platforms. This enhances security, ensures compliance, reduces manual work, and improves consistency and user experience. With standardized interoperability, it also future-proofs integrations and boosts operational efficiency while offering better visibility and control over identity lifecycle events

In order to add more flexibility to every execution in batch engine, we have added a new parameter ( batchExternalReferenceCode ) to be capable to send it to the backend without updating the ERC of the import task.

Key Benefits:

• Simplicity of execution with one parameter for each purpose.

• Add new capabilities for all entities that supports batch.

Captcha engine needs to be configurable on instance level to satisfy the multi-tenant environments' need. That has to be possible to configure them for one instance without interfering with the configuration for other instances.

Key Benefits:

Enabling CAPTCHA at the Instance level adds flexibility in configurations without affecting global settings. This supports tailored security and user experiences, and enables compliance per instance, all while retaining centralized control when needed

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.

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

Allow users to move workflow settings between environments
 

Key benefit:
Addresses a feature gap when moving applications built on Liferay between environments

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

Allow users to move display pages containing Object or Form widgets across environments

Key benefit:
Addresses a feature gap when moving content pages across environments
 

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.

We’ve introduced a new bulk operations feature that allows you to select multiple changes within a publication and perform actions on them all at once. This feature streamlines the process of managing multiple changes, saving you time and effort when working with large publications.

Key Benefits:

• Efficiency: You can now select multiple changes and perform bulk actions (like moving or discarding them) without needing to handle each change individually. This is particularly helpful in large publications where managing changes one at a time can be cumbersome and time-consuming.
• Improved Workflow: The ability to select and execute multiple operations at once significantly reduces the number of steps needed to manage your content, improving your overall workflow and productivity.

Users can now generate and download a PDF report of their event analysis, enabling seamless sharing of key insights with stakeholders.

Key Benefits:

• The PDF format ensures consistency when sharing insights across teams.
• The feature is accessible directly from the Event Analysis interface, simplifying the download process. 
• Users can optionaly choose to add a date range while downloading their pdf

When a user is deleted from DXP, the deletion now happens simultaneously in Analytics Cloud. To enable this, we’ve developed an API that automatically removes the same list of users from both DXP and AC in real time, ensuring data consistency across both systems.

Key Benefits:

• Processing Time: Depending on the number of users deleted, the process may take some time in Analytics Cloud. You can track the progress in Data Control & Privacy > Request Log under “Request Status.”
• Suppression Before Deletion: Each deleted user must first be suppressed before being permanently deleted in Analytics Cloud. As a result, you will see two requests per user—one for suppression and another for deletion.

In this release a new type of Data Set called System Data Sets is introduced, which will allow admin users to clone Java/Code Data Sets, making them editable and customizable through the Data Set Manager, which allow to customize any administration part of DXP built with a customizable Java/Code Data Set.

In this release the Data Sets from Order Pages have been made available as System Data Sets:

• Pending Order Items

• Placed Order Items

• Order Returns

• Pending Orders

• Placed Orders

In the next releases more and more Data Sets will be added to the list.
 

Key Benefits

• This epic increases the flexibility of Liferay DXP by enabling partial customization of previously hardcoded Data Sets.

• Admins will have more control over the user experience, enhancing the platform's ability to meet diverse and evolving business requirements.

• This also reduces the need for custom development efforts to modify or replace hardcoded Data Sets.

When an admin user is managing a Data Set, they might create sorting options, filters and actions. Until now, if the admin user chose not to show them to the end-user, they had to be deleted. From now on, these sub-entities can be deactivated, hiding them from the end-user without losing editing progress.

Key Benefits:

• Easier management of sub-entities without requiring deletion and recreation.
• Improved usability by allowing admins to configure visibility dynamically.
• More flexibility in defining experiences without modifying underlying data.

The Concurrent and Sync Reindex Modes, providing high-availability, introduced in Liferay DXP 7.4 Update 98 / Liferay DXP 2023.Q4 are now GA.

Reduce downtime, improve operational and resource utilization efficiency with the new Concurrent and Sync reindex execution modes providing high-availability in search capabilities while the operation is running.

When issues happen during maintenance periods, end users saw an unbranded default maintenance page. This leaves part of the user flow unattended, with customers unable to forward users to the correct next steps. Setting up and managing maintenance pages that work when DXP is down requires technical skills that not all customers possess, making it impractical for many.

Now we allow customers to upload a maintenance page they designed, fitting their brand and instructing customers on what to do. The implementation functions indepedently from their DXP instance so, as soon as they detect a downtime, they can enable the maintenance page in their Cloud Console to be displayed for their users while they address the issue that caused the downtime.

Configuring the scaling behaviour of Liferay is not simple. Customers are required to have a deep understanding of how their application' metrics behave to set their thresholds. Since charges are also incurred depending on the hours and instances scaled, customers can feel confused on the value they are being invoiced. 

That’s why we allowed for customers to set the maximum and minimum number of scaled instances in their Cloud Console scaling page. This means non-technical customers now can control how little or how much they want to spend in scaling their application. Allowing them pinpoint precision when balancing between improved user experience with more instances, and the increase in costs associated with that.

It’s going to be available without enabling the BETA flag, and from now it’s officially supported.

The Liferay Developer Studio installer now includes JDK 21 as a selectable option if it’s available, simplifying the initial setup and providing a more convenient and user-friendly experience for developers wanting to use the latest Java version supported by Liferay.

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.

Elasticsearch 8.17 has been tested and added to the compatibility matrix.

Liferay Self-Hosted deployments can update the Elastic stack to this version. For Liferay PaaS projects, as usual, a new Elasticsearch image will be provided under Liferay Cloud’s Docker Hub account.

As it was first highlighted in the Release Notes of 2024.Q3, per Elastic’s product lifecycle, Elasticsearch 7.17.x versions are supported and maintained until Elasticsearch version 9 is released.

While Elastic does not provide specific release dates for future releases, for Elasticsearch 9.0.0, the new release is anticipated in early calendar year 2025.

Compatibility with Elasticsearch 8 is available on Liferay DXP 7.4 U81+: Operating Liferay 7.4 GA/Update 81+ with Elasticsearch 8 - Liferay.

Note: The Elasticsearch 8.x compatibility is provided through the bundled Elasticsearch 7 connector and the REST API Compatibility of Elasticsearch 8.

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

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.

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:

1. Enhanced Buyer Experience: Buyers can shop and view prices in their familiar local currency, leading to increased trust and potentially higher conversion rates. This localized experience can significantly reduce cart abandonment caused by unexpected currency conversions at checkout.
2. Centralized Currency Management: The new "Currencies" tab in the channel configuration offers a dedicated space for administrators to manage and restrict available currencies, providing a clear and intuitive interface for controlling currency settings.

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

1. Enhanced Product Presentation: Control which product specifications are visible to customers, allowing for a cleaner and more focused product presentation on the storefront.

2. Improved Data Accuracy and Relevance: Hide internal or less relevant specifications, ensuring that customers only see information pertinent to their purchasing decisions.

This release introduces in-context translation for all the form fields directly within the page editor. This empowers content creators to easily create localized form experiences for their users, enabling them to complete forms in their preferred language. Only designated localizable form fields will be translated, ensuring precise control over localized content.

Key Benefits:

• Faster time to publish localized forms: Translating directly in the editor reduces the steps needed to launch forms in multiple languages.

• Reduces reliance on external tools or workflows: Content teams can manage translations within the same interface they use to build pages, simplifying the process.

• Improves accuracy and consistency: Only the form fields marked as translatable are included, so there's less risk of translating the wrong content or missing something important.

• Better experience for global audiences: Visitors can complete forms in their preferred language, which can increase completion rates and engagement.Gives teams more control over localization: Editors can choose exactly what gets translated and when, without needing developer support.