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.
Release Notes
Generally Available (aka OOTB)
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:
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.
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.
Generally Available (aka OOTB)
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.
Only available for Custom Objects fields.
Release Flag (opt-in)
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 ).
Users can choose between using the previous structure ( always execute the last version or the first endpoint created) or the new one ( allow to select exactly what to execute using the namespace ). Both are available.
query {
structuredContents(siteKey: "20117") {
items {
title
}
}
}
VS
query {
headlessDelivery_v2_0 {
structuredContents(siteKey: "20117") {
items {
title
}
}
}
}
Generally Available (aka OOTB)
Until now, for a translatable object fields, there was no way to get the values in different languages and always returned the default one. With this change, by adding the Accept-Language header, users can get the selected values properly. This change affects to Rest API and GraphQL.
Generally Available (aka OOTB)
Feature Status Change
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.
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 Use the platform's configurable purchasing rules to dictate which product options need to be purchased together when setting up products with options. You can set which product options must be purchased together and/or which product options cannot be combined together to create a valid product bundle. You can also limit the number of products from a particular group of products that can be purchased together. |
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.
Feature Status Change
Ability to add new steps to the checkout process via client extension. |
Feature Status Change
We've introduced case-sensitive tagging for page creators, allowing tags to be saved and displayed exactly as created, whether in uppercase or lowercase. The feature ensures case sensitivity for tag creation, case-insensitive searching, and autocomplete, while maintaining backward compatibility for existing tags.
Feature Status Change
In response to user feedback, several enhancements have been introduced for content creators. The first functionality addresses the challenge of easily finding and managing Web Content created within specific structures, allowing creators to review and edit content more efficiently. The rest of functionalities enable refined filtering and searching options, including the ability to search in the title, filter by categories and tag, filter search results and multi-select filters.
Feature Status Change
Now the configuration through the Client Extensions for Rich Text Editors is available by default.
Feature Status Change With the new support of Java JDK 17 and 21 runtimes, Java 8 will no longer be supported for DXP runtime on 2024.Q2 or later. Because JDK 11 was flagged for deprecation in the 2024.Q1 release, migration to one of the newly added versions is recommended. |
Feature Status Change
With the removal of JDK 8 runtime, DXP is no longer compatible with WebSphere. Migration to another application server on the Compatibility Matrix will be required for 2024.Q2 or later.
機能ステータスの変更
掲示板機能は非推奨となっており、将来的に削除される予定です。データの継続性を確保するため、Liferay ObjectsやWebコンテンツなどの代替コンテンツ管理ソリューションへの移行をお勧めします。
機能ステータスの変更
アクティビティウィジェットは非推奨であり、将来的に削除される予定です。
機能ステータスの変更
XSLコンテンツウィジェットは非推奨であり、将来的に削除される予定です。
機能ステータスの変更
ディレクトリウィジェットは非推奨であり、将来的に削除される予定です。
機能ステータスの変更
グループ統計ウィジェットは非推奨であり、将来的に削除される予定です。