Now users can configure the values for the following properties from settings (system, instance or site settings):
session.timeout.auto.extend
session.timeout.auto.extend.offset
Release Notes
Now users can configure the values for the following properties from settings (system, instance or site settings):
session.timeout.auto.extend
session.timeout.auto.extend.offset
This feature allows you to leverage the functions of Liferay’s caching framework. Our current measurements indicate about 10%/30% performance increase in database writing operations, also 10 times faster reading performance!
When the Upgrade Report is enabled, the output directory of the report can be configured with the new portal property upgrade.report.dir
If this property is not set, the upgrade report can be found in the default directory:
portal-tools-db-upgrade-client/reports
for the upgrade tool.{liferay-home}/reports
if upgrade was executed on startup.With this feature we extending the SCIM implementation with User Group un/provisioning as well with the User Group membership un/provisioning.
Previously customers would add captchas using a TagLib. But this is no longer useful since customers are not deploying JSPs. The Captcha API enables this functionality to be used in arbitrary contexts.
The user experience of the Management Toolbar present in multiple applications (Web Content, Blogs, Documents & Media) has been improved:
Sell and manage SKUs by adding different Units of Measure to the SKU. Configure the Unit of Measure to optionally allow for sales in decimal quantities. Units of Measure have their own pricing and inventory. Once configured, they add to the shopping experience of the buyer who can now purchase SKUs in different Units of measure.
Now, users are able to fill out object entries in parts, allowing them to save data as draft and return at their convenience to complete.
Our new Bulk Permission Management empowers administrators to modify access rights for multiple pages effortlessly. This new feature offers a multitude of benefits:
The Category Facet uses assetVocabularyCategoryIds
field for aggregation. The required mapping and indexer changes have been available since 7.4 GA46/U46 (LPS-156503: Display, Scope and Filter Categories by Vocabulary in the Category Facet).
Note: Reindex is required after all upgrades.
A new set of tooling is being provided, to centralize all the different tooling into a single solution, therefore, stand-alone tooling like the Fragments Toolkit does not make sense anymore as a stand-alone tool. In addition to that, the fragment toolkit needed upgrades to prevent some vulnerabilities that could happen. Therefore, we recommend adopting other solutions for now. The Fragment Toolkit will remain available for a minimum of one year.
Now, if an asset type (for example, an Object definition) has several related Display Page Templates, and one of them is marked as Default
, we allow to map links to any of the existing Display Page Templates for that Asset Type, in addition to the Default
one.
This new possibility allows some interesting use cases for customers, such as:
Capabilities:
Benefits:
We have created a new application that helps developers to build APIs based on custom Objects in a Low Code/No Code UI. This new feature allows users to define the whole structure of the API, from the endpoint’s name to the data model of the request and response schemas.
And, because the persistence layer of the API Builder is Objects, all capabilities are available at the API layer and every object has its own CRUD API application created by default.
So, from the UI or from the API, now users can create custom API Applications from scratch.
The scope of this beta feature only covers the creation of GET methods to retrieve a collection of elements with the possibility of creating pre filters and sorts.
Admins now can define views and select fields that are localized, so users will access the corresponding translation when visiting the page. Additionally, the names of the columns and filters are also localizable.
In order to use this feature it is needed to enable “Translation Support for Object Entries” in the Feature Flags menu before enabling “Data Set Manager” in the beta section of the Feature Flags menu.
Reducing downtime, improving 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.
Now admins can define the default sorting for a dataset view. You can select the field to sort by when users access the page with the data set view as well as the direction (ascending or descending). It is possible to add more than one field. In this case, results will be sorted following the order of the fields, so it will start sorting based on the first field, for elements with the same value for that field, it will continue sorting based on the second field and so on.
Integrated Logging in Cloud Console for both Client Extension and DXP. Capabilities:
Benefits:
Capabilities:
Benefits:
New terms available in notification templates related to the current user and entry creator were added, in order to improve the power of dynamically generated templates.
Added terms:
[%CURRENT_USER_ID%]
[%CURRENT_USER_FIRST_NAME%]
[%CURRENT_USER_LAST_NAME%]
[%CURRENT_USER_EMAIL_ADDRESS%]
[%OBJECT_AUTHOR_ID%]
[%OBJECT_AUTHOR_FIRST_NAME%]
[%OBJECT_AUTHOR_LAST_NAME%]
[%OBJECT_AUTHOR_EMAIL_ADDRESS%]
Dynamic Data Lists is deprecated and replaced by Objects. DDL has been deprecated as of 7.3, and the Deprecation flag was added to prevent new integrations using DDL (customers that upgrade will still see it).
DDL is planned to be removed in 2024, please migrate your data to Objects before then.
This functionality is now available OOTB. For more information on this feature, please check out the DXP 2023.Q3 Release Notes. |
Compatibility with IBM WebSphere application server has been deprecated as of Q4.2023. Please migrate to another application server on the Compatibility Matrix. WebSphere compatibility is expected to be removed at the end of 2024.
Now the “JS Import Maps Entry” frontend client extensions is enabled by default.
Compatibility with Java JDK 8 runtime has been deprecated as of Q4.2023. Java JDK 11 is now the recommended runtime environment. All Java Technical Compatibility Kit (TCK) compliant builds of Java 11 are certified. DXP source compile and runtime compatibility for a higher Java JDK is expected in 2024.
Proxy Objects allows users to manipulate data directly in external systems, such as Salesforce. This feature provides the ability to always interact with live data, avoiding duplicating and conflicts between the systems.
Now, Liferay includes a connector to Salesforce for proxy objects. With it, you can integrate your proxy object with custom Salesforce objects, using Salesforce as an external storage system
Now the “Theme SVG Spritemap” frontend client extensions is enabled by default.
Now, users can build forms and content pages configuring them to trigger stand-alone actions with a click from the content page UI through the Page Builder.
We have added a new type of mapping that is available for editable type Action: you can see for example in a button fragment general options. To provide this out-of-the-box, we have evolved the button fragment to contain a configuration to switch between Link and Action buttons.
Before, changing cacheable
configuration of a fragment would imply a "save" action and potentially a changes propagation action (no changes indeed if only the cache configuration was changed). This caused problems in performance and other aspects (such as wrong modification date).
From now on, and to avoid that, Fragments Cacheable
property is managed in the Fragment options ellipsis menu: Fragment Sub-Elements Reference
This prevents fragment save + propagation when this configuration is modified, making it more efficient and resistant to issues.
In addition to that, we have added a cached label to better indicate which fragments have active cache.
IMPORTANT: BREAKING CHANGE as customers might expect the Cacheable configuration to be inside Fragments Editor, and now it’s placed in a different position.
Now it is faster to implement experiences that rely on forms to interact with a business process, specifically in scenarios in which our customers decide to create their own custom form fragments according to their own look & feel or behavior.
We have added a configuration for the user to decide which form fragments will be automatically mapped to each Object field type, when a form container is mapped to an object.
Improves the overall usability of the application and also the ability to reorder and add items. Also improve the accessibility of functionality:
This feature allows developers to add email notifications directly into the notifications queue. It is useful when the email notification templates do not support a necessary custom logic that the template requires without requiring customers to re-write the entire email engine logic.
Fragments now provide editable types to map Link to Page field types that can be found in structures.
As it was done with 404 feature, now this feature is enabling our customers to fully adapt their users' experience providing an OOTB 500 error page fully customizable and allowing creation of new ones from scratch.
This feature applies the GDPR rules to the object entries. When the admin chooses to delete User's Personal Data, the object entries related to that user will also be deleted.
Pleae check the Content Security Policy by clicking here.
特定の行動に基づいて、より詳細な顧客セグメントを作成できるようになりました。 セグメンテーション機能を拡張し、標準的なウェブサイト活動だけでなく、カスタムイベントを含むオーディエンスのセグメンテーションが可能になりました。 ターゲットを絞った顧客グループを作成し、よりパーソナライズされた体験を提供することができます。 さらに、Liferay DXPは、カスタムイベント基準が変更されたときにアラートを提供し、セグメントの正確性と関連性を保証します。 顧客分析をより詳細に管理し、より適切なコンテンツを配信できるようになります。
オブジェクトに基づいた新しいOut-of-the-Box(OOTB)メールの通知テンプレート。 このテンプレートは、注文ステータスが「保留」に変更されると、注文作成者に自動的に送信されます。
この通知には以下の内容が含まれています:
注文番号
注文日
アカウント名
配送先住所
注文商品の概要
注文合計
私たちはコマース通知を廃止し、新しい通知にはオブジェクトを使用します。
The portlets that are in the Contacts module will be deprecated.
These are:
In the first step, the modules were pushed to the maintenance mode.
Adds support for creating custom client extension development profiles in the same project.
For example, when the user creates a file called client-extension.dev.yaml
, a new task will be available to the user called deployDev
.