Release Notes
Admins can now leverage Data Set actions to send targeted requests to a specified endpoint. This enables dynamic updates to persisted objects, such as changing a user's status to "Inactive." While the request body content is currently static, this powerful feature provides a flexible way to manage and modify data within your system.
Data Sets now offer even greater customization power. Admins can directly add manual query parameters to the endpoint URL, enabling fine-grained control over data retrieval.
This flexibility allows you to:
By tailoring the endpoint response, admins can provide a more curated and user-friendly experience for end-users.
Behind the Scenes:
The platform seamlessly reconciles these manual parameters with those generated by:
This ensures a consistent and efficient data retrieval process.
On top of that, admin users can also add or map fields manually to be displayed in the Data Set, so they will be able to bring the information back for those endpoints that don’t have the fields properly typed in the response.
The Database Upgrade Report is now enabled by default and offers expanded information compared to previous releases.
After running a database upgrade, check the reports/ directory for reports about what occurred in the system during the upgrade. The new upgrade_report_diagnostics file includes further details to diagnose any possible issues.
New properties and configurations have been added to allow control over the default user created for new virtual instances.
The instance admin user can be defined by the system admin upon instance creation or be disabled completely. This adds an immediate additional layer of security to a new virtual instance.
This update enhances the transparency and accountability of your Process Builder definitions. By tracking modification dates and user information, you can easily identify changes, troubleshoot issues, and ensure compliance. With this improved version history, you can effectively manage your processes and make informed decisions.
Currently, in Liferay Forms, users can customize field labels for ease of reference in the page’s HTML.
Now, users are able to fully customize and reference in the HTML the remainder of the Form.
This new feature allows users to configure Collection Providers based on Liferay System Objects, such as Users and Accounts. |
Here we added the capability to expose ERC and Scope for Attachments added to Object Entries. We plan to use this during Moving Object entries between environments. |
We added the permissions assigned to Custom and Modifiable Object Entries to the Objects Entries APIs' nested fields. This will be useful when we export/import Object Entries with permissions through Batch.
When the access token is near the expiration date, the portal sends notifications to the System Administrator about it.
Liferay Cloud currently supports Java JDK 8 and 11, but the industry is moving towards newer Java versions like JDK 17 and JDK 21. To ensure that Liferay Cloud remains modern, allows our customers to leverage the newest security patches, and boosts overall performance.
A pack of improvements to the usability of the logs page. Clients now can troubleshoot more effectively, be it by better handling multiple filters or by selecting/copying logs without the use of the log inspector.
The customer now has more visibility regarding quotas and usage of the resources they purchased. We added the visualization of their daily builds, which will help them better organize their releases and avoid problems when trying to build above their quota. Another improvement was for their database storage size to also be visible now. |
Feature Status change:
Tracking events related to non-default asset types and visualizing this data on a dashboard
Feature Status Change
Segments that are just static groups of users
Feature Status Change
SCIM provides a unified, RFC compliant way to keep user/group data in sync between different applications. Liferay is a service provider and enables clients to be connected. Though the defined RESTful APIs and schemas, clients can perform CRUD operations to keep resources in sync.
Feature Status Change
The vendor has deprecated OpenSSO/OpenAM, so there is no reason for us to keep it. The alternative, which is PingAM can be integrated using our existing OpenID connector or SAML Authentication.
Feature Status Change
Enabling this feature will allow users to dynamically populate fields using expressions with information created from data filled and provided by other fields.
Feature Status Change
The Forms feature is going into maintenance.
Feature Status Change
Object Layouts are going into maintenance.
Feature Status Change
Object Views are going into maintenance.
Feature Status Change
This feature introduces the ability to create and manage custom picklists for product specifications. Users can now define specific values for product attributes, improving data consistency and efficiency. The feature includes the option to create new picklists or add existing ones directly on the specification page.
Feature Status Change
A new out-of-the-box (OOTB) email notification template based on Objects. This template will be automatically sent to the order creator when an order status changes to 'pending'.
The notification includes:
Order number
Order date
Account name
Shipping address
Order item summary
Order total
We will move away from Commerce notifications and deprecate them and we will use Objects for the new ones.
Feature Status Change
Roles Managers can now define permissions for Object entries directly within the Roles UI. A new “Objects” main menu item has been added to the Define Permissions tab, listing all Custom Objects, allowing easier granular permission assignment.
Feature Status Change
The Commerce Modals feature is being deprecated and will be removed in the future.
Feature Status Change
|
The Commerce Notifications feature is being deprecated and will be removed in the future. |
Feature Status Change
The Commerce Accounts feature is being deprecated and will be removed in the future. To ensure data continuity, we recommend transitioning to Portal Accounts.
Feature Status Change
The Commerce Addresses feature is being deprecated and will be removed in the future. To ensure data continuity, we recommend transitioning to Postal Addresses.
Feature Status Change
The Contacts Center Widget is being deprecated and will be removed in the future.
Feature Status Change
The Commerce Search feature is going into maintenance.
Feature Status Change
The Commerce Search Results widget is going into maintenance.
Feature Status Change
|
The Product Details widget is going into maintenance. |
Feature Status Change
The Product Publisher widget is going into maintenance.
Feature Status Change
Users can easily configure the friendly URLs for the different asset types, updating URL separators. In addition to that, they are able to select and reorder categories within a blog’s friendly URL so the users can easily identify by the URL what is the main topic of the page they are visiting.
Feature Status Change
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.
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
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
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
The My Subscriptions Widget is being deprecated and will be removed in the future.
Feature Status Change
The Social Networking Plugin is being deprecated and will be removed in the future.
Feature Status Change
The Subscription Manager Widget is being deprecated and will be removed in the future.
Feature Status Change
In a future release, DXP will be moving to modern Enterprise Java API, Jakarta EE 10. Announcing the JavaEE deprecation to give time to prepare for this significant breaking change scheduled to occur in the 2025 calendar year.
Moving to Jakarta EE will require:
Feature Status Change
With the upcoming move to Jakarta EE 10 and expansion of Client Extensions, DXP is focusing attention a new generation of customization options.
Liferay Faces support for JavaServer Faces (JSF) is being deprecated.
Feature Status Change
With the upcoming move to Jakarta EE 10 and expansion of Client Extensions, DXP is focusing attention a new generation of customization options. PortletMVC4Spring is being deprecated.
Feature Status Change
With the expansion of Objects functionality, Custom Fields are going into maintenance.
Feature Status Change
The Liferay Theme generator is being deprecated and it will be removed in the future. Customers are encouraged to use Theme Client Extensions or third-party tooling to generate themes.
Feature Status Change
The AMD Loader are being deprecated and they will be removed in the future. Liferay DXP officially supports ESM, which is the official standardized module system for JavaScript, while AMD was a third-party solution.
By adopting ESM, products align with the language's native capabilities and future direction. Modern browsers now natively support ESM, allowing for direct use without transpilation or additional loaders. This can lead to reduced bundle sizes, faster initial page loads and simplified development workflows. This will imply also the deprecation of Liferay-CLI.
Feature Status Change
The Liferay Talend Components feature is being deprecated and will be removed in the future.
Feature Status Change
The functionality for sharing widgets is being deprecated and it will be removed in the future. The feature has been deemed obsolete.
Feature Status Change
The functionality for Most Viewed Assets Collection Providers is being deprecated and it will be removed in the future in light of more advanced Analytics Cloud content tracking.
Feature Status Change
The "Featured Content" contributed fragment set is being deprecated and it will be removed in the future.
Feature Status Change
The Asset Publisher widget is going into maintenance.
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.
You can now have access to the event’s details when selecting a calendar event and be redirected to the already existing details page of that particular event. It is also possible to map a Calendar Event’s specific URL, along with some other fields, in order to use it in emails so the recipient can click on it and be redirected to the Event’s details.
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.
We're introducing advanced script loading options for JavaScript Client Extensions in Liferay, providing developers more control over how JavaScript is applied to pages. This update allows the specification of async and defer attributes directly in the extension's configuration, optimizing the loading process and improving page performance.
Benefits for users:
async or defer attributes, scripts can be loaded non-blocking, enhancing page responsiveness.Allow developers to specify additional attributes to the <script> tag when deploying in with the JS Client Extension.
Example usage in client-extension.yaml: liferay-portal/workspaces/liferay-sample-workspace/client-extensions/liferay-sample-global-js-2/client-extension.yaml at master · liferay/liferay-portal
scriptElementAttributes:
async: true
data-attribute: "value"
data-senna-track: "permanent"
fetchpriority: "low"
Or, developers can configure the attributes via the create Client Extension UI too:
When configuring a JS CX on a page and async/defer Boolean attributes are present in the CX (set in the yaml / defined through the UI), the following behaviors apply in regards to the Load type options:
async will be applied.async or defer is set to false in the CS, the related option will be removed from the Load selector. (e.g. if defer: false the load options available for the user will be default and async).
This feature introduces the capability to connect Liferay Objects with SugarCRM Objects, empowering users to synchronize and store their data efficiently between the two platforms. By bridging these systems, users can streamline their workflows, enhance data consistency, and leverage the robust features of both Liferay and SugarCRM.
Users can now, with low effort, connect their Liferay and SugarCRM environments, eliminating the need for manual data transfers and reducing the risk of errors. This enhancement not only simplifies data management but also enhances the overall user experience by providing a cohesive and integrated ecosystem for managing customer data.