機能ステータスの変更
「注目コンテンツ」提供フラグメントセットは非推奨となり、将来削除される予定です。
Release Notes
機能ステータスの変更
「注目コンテンツ」提供フラグメントセットは非推奨となり、将来削除される予定です。
機能ステータスの変更
アセットパブリッシャーのウィジェットはメンテナンスに入ります。
機能ステータスの変更
ユーザーは、ページのパフォーマンス問題を引き起こす可能性のあるコンポーネントを簡単に特定できます。ページ監査に新しいタブを追加し、異なるコンポーネントのバックエンドのレンダリング時間や、パフォーマンスの問題につながる可能性のある特定のコンポーネント構成を特定するのに役立つ警告をユーザーに表示するようにしました。これらの警告は編集モードにも表示されるので、ユーザーはページ作成中に起こりうる問題を認識できます。
AIアシスタントは、コンテンツ制作者の生産性を向上させ、ワークフローを合理化するために特別に設計された、多用途で強力なツールです。AIを活用したコンテンツ制作を単一の使いやすいアプリケーションに一元化することで、AIアシスタントは多様なタイプのコンテンツの生成・管理プロセスを簡素化します。ブログ、ナレッジベース記事、ページレイアウトなど、どのような作業であっても、AIアシスタントはツールや柔軟性を提供し、スマートで迅速な作業を支援します。
可用性: AIアシスタントは、マーケットプレイスで簡単にアクセスできるクラウドベースのアプリケーションであるため、既存のデジタル・エコシステムへの統合が容易です。そのクラウド・インフラストラクチャは信頼性の高いパフォーマンスとスケーラビリティを保証し、ユーザーに一貫したシームレスなアクセスを提供します。
Jakarta EEへの移行を控えているため、Jakarta EE 10に対応した新バージョンのリリースに備え、アプリケーションサーバーの現行バージョンをすべて非推奨としています。これは大きな変更であるため、新しいアプリサーバーのバージョンは古いバージョンに取って代わります。
非推奨:
Apache Tomcat 9
Wildfly 26.1
Jboss EAP 7.4
Weblogic 14
2025.Q3では、以下のアプリケーションサーバーのサポートを追加します:
Apache Tomcat 10.1
Wildfly 30
Jboss EAP 8.0
Weblogic 15 (Oracle社のリリース待ち)
データセットで一連の項目をフィルタリングする際にに、リレーションシップの一部であるフィールドをフィルタリングすることに関心がある場合があります。
この新しい機能により、複雑なオブジェクトの子オブジェクトによるフィルタリングをユーザーが選択できるようになりました。
近日リリース予定のLiferay Connector to OpenSearch 2.xのMarketplaceリリースは、Elasticsearchに代わるSelf-Hosted Liferay deploymentsを提供します。
重要: Liferay Enterprise SearchのLearning to Rank、クラスター横断レプリケーション、モニタリングアプリケーションは互換性がないため、OpenSearchではサポートされませんのでご注意ください。
The Centralized Products Eligibility and Configuration Management 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. Additionally, it enables faster and smarter management of product eligibility for channels, order types and accounts.
Key benefits:
1. Improved Catalog Management Efficiency:
Simplified product configuration editing via a centralized, flat table view.
Streamlined workflows for managing product attributes like visibility, minimum/maximum quantities, eligibility and much more.
Avoid duplicating products to manage specific configurations by modifying targeted configurations instead.
Perform batch updates on visibility, eligibility, and other product attributes for multiple products, whilst inheriting base setting from the Master catalog configuration
Leverage pre-filled default master configurations to ensure consistency and simplify product setup when adding new products in a catalog.
2. Enhanced Control over Product Eligibility and Visibility:
Define and manage eligibility rules tailored to specific customer groups, channels, and accounts
Quickly adjust product availability and settings for various markets and segments (e.g. B2B vs B2C).
Streamline the management of seasonal items or time-sensitive offerings using configuration scheduling.
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.
This feature focuses on rigorously aligning the User Management headless APIs with the established standards and best practices. This includes:
Comprehensive Functionality Testing: Verifying that all API endpoints (PATCH/POST/PUT) correctly update the expected fields in user records.
Custom Field Support: Ensuring seamless integration and proper functioning of custom fields within the API interactions.
Error Handling: Thoroughly testing error handling mechanisms and verifying that informative and user-friendly error messages are returned in all relevant scenarios.
Data Manipulation Capabilities: Confirming the correct and efficient functioning of sorting, filtering, and other data manipulation operations within the API.
Key benefits:
Enhanced User Experience: By ensuring the reliability and accuracy of the User Management headless APIs, we provide a seamless and efficient user experience for developers and integrators.
Increased Developer Productivity: Well-defined and documented APIs empower developers to build integrations quickly and confidently, reducing development time and effort.
Improved System Stability: Rigorous testing and alignment with standards minimize the risk of unexpected errors and system disruptions, leading to a more stable and reliable user management system.
Enhanced Data Integrity: By ensuring accurate data updates and consistent API behavior, we maintain the integrity and consistency of user data across the system.
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.
This release introduces in-context translation for text-based form fields (Text, Rich Text, and Textarea) 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. |
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.
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 display pages containing Object or Form widgets across environments
Key benefit:
Addresses a feature gap when moving content pages across environments
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.
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.