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.
Feature Status Change
Support for these application servers is deprecated for 2024.Q2 or later since they are no longer receiving updates from the vendor.
Wildfly 26.1 and Jboss EAP 7.4 remain fully supported.
The current Announcements and Alert features are being flagged for deprecation as part of our move the Objects framework which will offer support for these use cases within its Notification capabilities.
This release will allow users to generate a version of Liferay Workspace that is compatible with Gradle 8.
With our latest enhancements, Content Admins will enjoy effortless content organization, regardless of folder structures, along with enhanced filtering capabilities for precision content management discovery.
Features added in this Release:
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 other 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.
The Path Analysis tool has been enhanced with the addition of Exit Pages. This feature allows marketers to not only visualize users' entry points (referrer pages), but also their exit points (exit pages). With this user flow analysis, marketers can enhance user engagement and reduce bounce rates.
We have expanded the capabilities of AB Testing to allow the selection of a Collection Display Fragment as the Click Goal of an AB Test. This will allow customers to AB Test the clickthrough rate of different Collections or Collection Providers, empowering them to optimize which content is shown to end users.
In order to improve user experience and avoid difficulties with sharing and reporting insights from AC to other members of the organization, we are introducing the Download Reports feature. This functionality allows users to easily download their dashboards as PDFs and specific lists (e.g.: segment membership) as CSVs, streamlining the process of socializing this information with stakeholders.
We continue to improve the API Builder by adding new endpoints: GET single element. With the GET single element new endpoint, we allow users to create a GET endpoint that only retrieves a single element using a path parameter.
One particular thing is that users can select as a path parameter any unique custom field defined in the object apart from ID and External Reference Code.
New POST endpoint inside API Builder to add the possibility not only of recovering information of the entries but also of creating them.
As in the GET methods, users can define the schema to use for the request and the response. Both can be the same or two different ones. And can even be one already used previously on another endpoint definition.
Company and Site scope is available too.
The POST method only works for creating new entries of the main object . No entries for the related objects can be created yet at the same time.
We have 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.
We have introduced a configuration feature within the Asset Library, enabling users to decide whether a Vocabulary created there is solely required at the Asset Library level or if it extends to the connected Sites as well.
Users now have the ability to restrict channel access to certain Accounts via the eligibility tab on the channel admin pages. The ability to restrict certain Account Addresses to be used on certain channels has also been added. This is managed via an Eligibility tab on the address that allows the user set channel usage.
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.
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 more speedy alterations to be made before proceeding with check out.
The allowable size of an Account Name has been increased to 250 characters in line with industry standards.
When adding validations in Objects, many times it is necessary to validate dates against the current date.
Key Features:
Dynamic Date Comparison - Users can compare a selected date with the current system date. This empowers you to create rules that trigger based on the relationship between a date field and the present date.
Versatile Date Range Checks - Validate whether a date falls within a specified date range relative to the present date.
Users can add validations to verify field values that, when used in combination, are unique.
Limitation: numeric fields such as Integer, Long Integer, Decimal, Precision Decimal will be stored as null.
Validate relationships to prevent duplicate names in child objects.
This development introduces the ability for the user to set the file size at asset library’s level. This settings will override the already existing one at System level when the latter is bigger. As a general rule, when both are set the lowest applies.
To reduce the maintenance costs of providing a full document’s preview, the following changes are being introduced:
“No preview available” state when the file size exceeds the preview size limit.
Merge “File Entries” and “PDF Preview” settings under “File Preview Limits”
Rename "File Size Limits" to "File Upload Limits" with a reviewed and more understandable Description copy
The user is being informed that the generated preview may not correspond to the entire document
We refactored the way Liferay scripts were managed, so admins can define stricter policies like:
script-src '[$NONCE$]'; script-src-attr 'unsafe-inline';
Limitations: If a policy like the one above is configured, the parts of the product that uses a rich-text editor will not work correctly. Analyze your scenario to identify how strict your policy can be in order to make the solution work.
Now users can configure the values for the following properties from settings (system, instance or site settings):
session.timeout.auto.extendsession.timeout.auto.extend.offset
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.
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.
Allow clients to request a quote for individual products instead of setting a price. Includes the option to use a Price List or a Promotion to price the Product as "Price on Application". There is also the ability to activate the "Request a quote" option on a fully priced cart for a particular channel.
New Account Type of Supplier. A Supplier can be linked to a catalog and to a channel to allow the supplier manage their own products, price lists, promotions, catalogs, discounts, inventory and channel in order to be able to fulfill orders for their own products.
Used in Conjunction with Supplier Accounts, this object's rule, once configured, splits Commerce Orders automatically by the Catalog that each Product belongs to. The Channel on the Order is updated to be the channel linked to the same supplier that the catalog is linked to. The order splitting rule effectively allows the supplier to manage orders for their own specific products.
Now, users are able to visually understand the structure of their objects and how they connect with each other to result in the platform model.
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.
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.
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.
Our new Bulk Permission Management empowers administrators to modify access rights for multiple pages effortlessly. This new feature offers a multitude of benefits:
With our latest update, you can define access permissions and schedule content publishing in one convenient step, saving you valuable time and effort. Take full control over content visibility and publication timing, ensuring your content reaches the right audience at the right time. Publish with greater precision and efficiency - try the new Manage Permissions and Scheduling feature today!
Simply provide a descriptive prompt and let DALL-E generate the perfect image to complement your content strategy, saving you valuable time and resources. Leverage AI to spark new ideas and generate unique concepts that perfectly align with your content needs. Explore a world of visual possibilities!