The Liferay Developer Studio installer now includes JDK 21 as a selectable option if it’s available, simplifying the initial setup and providing a more convenient and user-friendly experience for developers wanting to use the latest Java version supported by Liferay.
Release Notes
Previously, when managing complex data models, users must create scripts or code in order to make changes to multiple related objects. Now users are able to configure multiple objects as if they are one object. Related child objects now inherit permissions and account restrictions and more from the top level parent, making object management more convenient.
Key benefits:
Simplifies the management of multiple objects through a configuration on the relationship between objects
Permissions and Account Restrictions for the child objects are inherited from the Top level parent
API endpoints are nested under the same namespace of the top level parent
Allow users to move Object Definitions and Entries between environments
Key benefit:
Addresses a feature gap when moving applications built on Liferay between environments
Allow applications built on top of Service Builder to leverage the benefits of the Liferay Objects framework
Key benefit:
Applications built on top of Service Builder can now be migrated to Liferay Objects
Allow users to move display pages containing Object or Form widgets across environments
Key benefit:
Addresses a feature gap when moving content pages across environments
The batch engine's export endpoints now support filtering for object entries. This addresses a previous limitation where filtering was not applied to object entries during batch exports. This update ensures consistent data handling and filtering behavior across all entity types.
Key benefits:
- Object entries Personalization
- Equalize capabilities for all entities
Until now, there was no way in batch engine to export and import object entries and their permissions simultaneously. This new capability allows users to do that, streamlining workflows and reducing manual effort.
Key benefits:
Execution in only one call.
Possibility for users to choose to take into account (or not) permissions with object entries.
Implemented proactive access token management with automated email notifications. Users will now receive alerts 1 month, 10 days, and 1 day prior to token expiration, allowing for timely renewal and preventing service disruptions. Notifications are automatically cancelled if a new token is generated.
Key benefits:
Users are notified before token expiration, allowing for timely renewal and uninterrupted access.
Reducing administrative overhead, as automated notifications eliminate the need for manual monitoring and intervention.
By prompting timely renewals, the risk of using expired and potentially compromised tokens is minimized.