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.