Allow users to move workflow settings between environments
 

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

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.

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

Added External Reference Codes for references in widget configurations in Commerce and User Management applications. This helps promote data integrity when pages and their widgets are migrated across environments.

Key benefits:

References within the following page widgets now use External Reference Codes instead of internal IDs:

• Cart

• Cart Summary

• Category Content

• Commerce Addresses

• Commerce Category Navigation

• Mini Cart

• Open Carts

• Option Facet

• Order Forecasts Chart

• Organization Management

• Placed Orders

• Product Comparison Bar

• Product Comparison Table

• Product Details

• Product Downloads

• Product Publisher

• Search Results(Commerce)

• Specification Facet

We added External Reference Codes for references in widget configurations in Content Management applications. This helps promote data integrity when pages and their widgets are migrated across environments.

Highlights:

References within the following page widgets now use ERC’s instead of internal ID’s:

• Announcements
• Web Content Display
• Category Filters
• Questions

We added External Reference Codes for Categories and Tags and their associated API’s, improving their portability for data migration scenarios.

Highlights: 

• Users can now perform CRUD operations using a Tag’s ERC through its headless API (Keyword)

• Users can now perform CRUD operations using a Category’s ERC through its headless API (TaxonomyCategory)

We added several API endpoints for Documents & Media to improve programmatic management of these entities.

Highlights:

• Users can now add, delete, and retrieve document types via headless API (DocumentDataDefinitionType)

• Users can now add, delete, and retrieve document metadata sets via headless API (DocumentMetadataSet)