-
Improvement
-
Resolution: Fixed
-
Critical
-
5.2.4
-
None
-
None
With MGNLUI-2783 we introduced a way to run commands asynchronously. This should now be applied (on fresh installations as well as on updated ones) to:
- recursive publication
- deletion
as both of the actions involve versioning of content and can be time consuming
- is cloned by
-
MGNLDAM-441 (Potentially) long running actions should be configured to run asynchronously
-
- Closed
-
- is related to
-
MGNLUI-2783 User is blocked in his browser session after starting long running Action
-
- Closed
-
-
MGNLSCH-44 Set status of the job (success/failure) to the JobExecutionContext
-
- Closed
-
-
MGNLSCH-45 Improve and i18nize scheduler error messages
-
- Closed
-
-
MGNLUI-2855 Ansynchonous action (activation) should return better error message
-
- Closed
-
-
MGNLWORKFLOW-242 Enable workflow to run activation asynchronously after approval & publish
-
- Closed
-
- relates to
-
MGNLUI-3341 Avoid multiple asynchronous tasks and pulse messages when deleting multiple items at once
-
- Closed
-