Release Notes
We have implemented a new translation status feature in the web content editor, labeled "Translating," which provides information about the number of translated fields and those still requiring translation. This feature helps users to quickly identify areas needing translation. Additionally, all translatable fields, including metadata, are now conveniently displayed on the left side of the screen, reducing the likelihood of overlooking them.
Users can readily spot content that is not visible to Guest users through an icon, whether it's in list or table view or within the web content editor. Additionally, this feature is accessible in the item selector, empowering users to discern which content is not viewable by Guest users.
Now it is possible to easily identify the content you have created and any recent content you generated. This enhancement streamlines and optimizes this workflow.
Easily configure the friendly URLs for the different asset types, updating URL separators. In addition to that, now users are able to set categories within a blog’s friendly URL and easily identify by the URL what is the main topic of the page they are visiting.
This feature aims to refine the Analytics Cloud Usage Page. Alongside UI enhancements for a better user experience, we focused on enhancing data accuracy and real-time precision. Our efforts aimed to eliminate data discrepancies and prioritize transparency for the users.
Key Changes:
To promote pricing transparency, we removed the outdated prices from the Workspace settings and implemented a clear message prompting users to reach out to their Customer Success Manager for information on upgrading their plan.
Aiming to simplify the interface and highlight pertinent subscription details, some changes were made to the UI of the Subscription and Usage menu, focusing on displaying relevant information to the customer related to their current plan.
To create Sign In, Forgot Password, and Create Account utility pages, it's necessary for these three views of the Login portlet (i.e., Sign In widget) to be available as individual widgets, which can be placed on pages separately. As a result, Sign In, Forgot Password, and Create Account are now accessible as separate widgets.
It's worth noting that the Sign In widget retains its previous functionality.
We aimed to facilitate seamless navigation between various Utility pages, whether there are multiple or just one.
It allows users to map fields on the first level of related elements or any hierarchical structure through a tree view which is searchable and expandable.
In addition, it is possible to map leaf fields, the common use case, but also parent fields which include all the children data to be rendered through a Client Extension.
Until now the Data Set was always rendered as a table with one column for each mapped field. From now on, the admin user can define up to three different visualization modes for the same data: Table, List and Cards.
These visualization modes share the configurations about: filters, actions, sorting and pagination. However, each visualization mode can have different mapped fields decided by the admin users.
Also, a new Settings tab to select the default mode has been added.
Final users will be able to view the visualization modes created by Admin Users and they will be able to change between them to discover the data in the way they want.
The Data Set for actions has been improved to provide new capabilities to the users:
The autocomplete attribute grants the user agent permission to provide automated assistance in filling out form fields. This feature can significantly speed up the form-filling process, especially for repetitive or standard information like names, addresses, and email addresses. This also allows screen readers which use standard attributes such as autocomplete to assist users navigating websites.
Incorporating the HTML autocomplete attribute into your forms is a simple yet powerful way to enhance user experience. By leveraging autocomplete suggestions, you can streamline the form-filling process, reduce errors, and ultimately create a more user-friendly environment. Experiment with different values, test across browsers, and watch as your users appreciate the improved efficiency of your forms.
When publications go out of date, they are completely useless and all changes made to them can not be leveraged in any capacity. The changes in this feature allow publications users to move changes from an out of date publication to another publication. This allows users to salvage changes after an upgrade.
This feature prevents portal from being unusable when a change-tracked entity being modified in a publication is removed from production. If an entity is being modified in a publication, it cannot be removed from production. If a deleted entity in a publication is being modified in another publication, the publication with the deletion cannot be published.
Boost the performance of reverting changes , when the DB has huge amount of records. This way the usability of Publications further increases.
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.
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
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