Allow users to move workflow settings between environments
 

Key benefit:
Addresses a feature gap when moving applications built on Liferay between environments

Allow users to move Object Definitions and Entries between environments

Key benefit:
Addresses a feature gap when moving applications built on Liferay between environments

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 display pages containing Object or Form widgets across environments

Key benefit:
Addresses a feature gap when moving content pages across 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

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.

Data imports, using batch engine, now allows users to preserve content creator information (if required). Previously, imported content with batch was always assigned the user performing the import, resulting in loss of original authorship data when moving content. This update ensures accurate attribution of content ownership (if required).

Key benefits:

• Able to keep critical user information during data promotion between environments

• Can be configured separately per import process