Data Set Manager lets from now to map Array structures, so a given cell of a Data Set can show list of values, for example to list the roles of a user or the tags of a product.
Release Notes
Data Set Manager lets from now to map Array structures, so a given cell of a Data Set can show list of values, for example to list the roles of a user or the tags of a product.
When the users are facing a Frontend Data Set the items can show actions to interact with them that are set in the Data Set Manager. From now own, when the user navigates to a destination URL through an item or creation action, the current URL is added to the destination page, so the user can return to the Data Set after performing the action seamlessly.
The CX Filter allows developers to build their own filters, with on demand bussiness logic and UI, to be added to a Data Set in the Data Set Manager and then be used for end-users in the Data Set. With this new value, the Client Extension can be generic, and the same Client Extension can be used to build filters that filter by different fields.
User session replication has been optimized for the Tomcat application server.
Users can configure a reset for the number of guest submissions allowed in a given timeframe.
Users can add the necessary security layer to avoid misuse of scripting in Objects and Workflow Actions.
In Notification Templates, users will now be able to send emails based on Account, Organization and Regular Roles.
Notification recipients will follow the permission framework that is already in place.
|
Users can now create picklists beginning with capital letters. One key feature is that now users will be able to filter by Active and Inactive values.
This will be a new configuration under System Settings and when enabled, will allow notifications from the workflow to respect the scope of the site. |
Objects is used for a wide range of use cases, some of them more technical than others. This feature will allow users to configure where they want their objects to be listed. Thus, creating unnecessary complexity and reducing cognitive load on other users.
Users can now configure their objects to observe the guest user’s locale and send email notifications based on the guest user’s language preference.
The guest user’s language preference is determined by the language the guest user used when submitting the form. If a locale cannot be determined or a notification template does not exist, then the notification will be sent in the instance’s default language.
For those Objects that have the translation active, users can not get this entry information using GraphQL. In order to improve GraphQL capabilities, we have exposed the _i18n properties, so any user can retrieve it.
Liferay has expanded GraphQL capabilities to match the functionality of REST APIs for managing object entries. Users can now transition object entries from Draft to Approved status using GraphQL, providing more flexibility and control within the development process. |
For making the Sign In portlet related functions easily customizable for the end users we want to simplify the portlet as much as we can. We need to remove all it’s configuration or functionality that can be handled in higher level.
Currently, the customer has to resort to email reports to see their autoscaling. We are making this information much more available and searchable, allowing the user to better understand their autoscaling behaviour.
Liferay DXP provides a variety of developer tools that include a robust build script framework, lightweight CLI utilities, and IDE tools. We have recently released new versions of Liferay Workspace and the IDE tools, which include Liferay Developer Studio, Liferay Eclipse Plugin, and Liferay IntelliJ Plugin. The main benefits include:
Alignment with the platform itself: The tools now support our quarterly releases, giving access to development on Liferay DXP's latest features.
Latest Java version support: Compatibility with JDK 17 and 21 provides developers with enhanced security, improved performance, and the newest capabilities of the Java platform.
Liferay now allows users to sort Custom Objects entries based on data from related objects. This enhanced functionality provides greater flexibility and control when managing complex data structures, enabling users to organize information more effectively.
Feature Status Change
It is now possible to select Date Times as a product option type, configuring purchase options for products based on date, times, time zones, and durations, allowing for the sale of time slots.
Feature Status Change
Users can activate the content creation prompt with a single click by leveraging AI capabilities directly within the CKEditor for seamless and efficient content generation. Requires a valid OpenAI API key.
Feature Status Change
Manage contacts directly related to accounts like phone numbers, emails, websites, addresses.
A new Contact Tab in Account details page with 2 internals tabs was created:
Users with “Accounts > Account Entry: Manage Addresses” permission should be able to manage their contacts with all these actions:
Example of managing a phone number:
Users without “Accounts > Account Entry: Manage Addresses” permission should be able to only view the existing phone number entries.
Feature Status Change
Map individual specifications, choose the order, and create clear, informative product pages that drive sales and enhance the customer experience. Simplify product page creation and empower your business with this new feature.
Feature Status Change
Our new Bulk Permission Management empowers administrators to modify access rights for multiple pages effortlessly. This new feature offers a multitude of benefits:
Feature Status Change
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.
Feature Status Change
The goal here is to make the users able to move changes between publications. This is needed because sometimes users do not want to publish an entire publication, but also do not want to revert the changes which will not be published actually. With this feature users can move changes from one publication to another, creating subsets of changes, and publish them separately. For readers with technical knowledge: this is similar to cherry-pick-ing a commit in git from one branch to another.
Feature Status Change
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!
Feature Status Change
The Custom User Attributes functionality of Asset Publisher is sometimes difficult to understand for the customer, so we recommend the users use Content Sets + Experiences instead. |
Feature Status Change
The Headless Search API introduced as BETA in 7.4 U88 is now in RELEASE status.
Feature Status Change
Support for these application servers is removed for 2024.Q3 or later since they are no longer receiving updates from the vendor.
Wildfly 26.1 and Jboss EAP 7.4 remain fully supported.
Feature Status Change
With the new support of Java JDK 17 and 21 runtimes, Java 11 will no longer be supported for DXP runtime on 2024.Q3 or later.
Liferay Workspace offers support for re-compiling custom modules on JDK 17 or 21.
Feature Status Change
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.
Feature Status change:
Now the possibility of Export/Import Frontend Client Extensions is available by default.
Users can easily identify and filter fields that are already translated and those that still need translation within the content editor. Additionally, they can choose to mark a language as translated even if some fields are not yet translated. Users also have the option to reset a translation to its default values with ease. These features will streamline the translation process and enhance efficiency.
The selection filters of the Data Set Manager has been revamped to allow chosing different type of sources. On top of the picklist, now the admin user may select an API Headless as filter values source, so the filter values might be populated with the values coming from the API response. This allow users to have a more automated process on the filter creation.
Feature Status Change
The Message Board feature is being deprecated and will be removed in the future. To ensure data continuity, we recommend transitioning to alternative content management solutions like Liferay Objects or Web Content.
Feature Status Change
The Wiki feature is being deprecated and will be removed in the future. Wiki and its related widgets are now subject to the deprecation flag LPD-35013. To ensure data continuity, we recommend transitioning to alternative content management solutions like Liferay Objects or Web Content.
Feature Status Change
Users can now set a display date for the documents so they can scheduled them to be published in the future, just for one document or when uploading multiple documents.
Feature Status Change
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 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.
Feature Status Change
The Activities Widget is being deprecated and will be removed in the future.
Feature Status Change
The Directories Widget is being deprecated and will be removed in the future.
Feature Status Change
The XSL Content Widget is being deprecated and will be removed in the future.