Allow users to move workflow settings between environments
Key benefit:
Addresses a feature gap when moving applications built on Liferay between environments
Release Notes
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