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.
Release Notes
When the access token is near the expiration date, the portal sends notifications to the System Administrator about it.
Feature Status Change
Object Layouts are going into maintenance.
Feature Status Change
Object Views are going into maintenance.
Feature Status Change
The Contacts Center Widget is being deprecated and will be removed in the future.
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 Commerce Search feature is going into maintenance.
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:
- Filter Data: Apply specific filters to narrow down the results
- Select Fields: Choose the exact fields you want to retrieve
- Flatten Responses: Simplify complex data structures
- Search for Specific Terms: Find relevant information quickly
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:
- Admin Configuration: Fields and Actions tab settings
- End-User Interactions: Filter and sort options selected in the UI
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.
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.
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.
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.
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
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 Notifications feature is being deprecated and will be removed in the future. |
Feature Status Change
The Commerce Modals feature is being deprecated and will be removed in the future.
Improved Disk Space Utilization for Elasticsearch and OpenSearch Deployments
To reduce disk space usage on the search engine side, we have optimized default field mappings which no longer use stored fields. Instead, the platform uses the fields parameter as the default document field retrieval method.
Important Considerations for Administrators:
- Review Advanced Settings: Administrators should carefully examine the "Additional Type Mappings" and "Override Type Mappings" settings within the search engine connector configuration.
Compare with Defaults: After reviewing the advanced settings, compare the existing mappings to the new defaults to identify potential adjustments. While stored fields are still supported, they are not recommended.
Potential Impact on Custom OSGi Modules:
While most users should experience seamless transitions, developers of custom OSGi modules that utilize Liferay's Java Search APIs may encounter changes in search response behavior. This could occur if the modules rely on specific fields being included in the search response. In such cases, developers may need to make adjustments to their modules to ensure correct functionality.
OpenAI can now be configured as a Text Embedding Provider for Semantic Search.
OpenAI offers two powerful third-generation embedding models promising lower costs, higher multilingual performance, and stronger overall performance compared to the predecessor models.
If your organization is already utilizing OpenAI's ChatGPT or other OpenAI Platform APIs, now you can take advantage of OpenAI's Vector Embeddings capability to deliver semantically more relevant search results through Liferay's semantic search feature (BETA) without the need to sign up for another service.
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.
The Data Set Manager sorting tab has changed its purpose. From now on, the sorting options created under this section will be added to an Order Drop Down that is added to the Management Bar. This way, users will be able to sort by different criteria, even if those criteria are not visible in the Data Set items.
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
Segments that are just static groups of users
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
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
The Invite Members Widget is being deprecated and will be removed in the future
Feature Status Change
The My Subscriptions Widget is being deprecated and will be removed in the future.
Feature Status Change
The Shared with Me Widget is being deprecated and will be removed in the future.
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 Walkthrough is being deprecated and it will be removed in the future. Liferay will investigate new ways to offer this functionality.
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 XSL Content Widget is being deprecated and will be removed in the future.
Feature Status Change
The Media Gallery Widget is being deprecated and will be removed in the future.
Feature Status Change
The Microblogs is being deprecated and will be removed in the future.
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
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
Deprecating the filter for lastLoginDate on the Headless Admin API because it negatively impacts search performance.
Controlled by feature flag LPD-36010.
New true/false filter hasLoginDate can be used to efficiently check if a user has already logged in to their account at least once.
Feature Status Change
With the expansion of Objects functionality, Custom Fields are going into maintenance.
Feature Status Change
Users can easily identify components that may cause performance issues in their Pages. We have added a new tab on the Page Audit to show the users the back-end render times of the different components, as well as warnings to help identify specific components configurations that may lead to performance issues. Those warnings also appear on the Edit mode, so the user is aware of possible issues during the page creation.