Page History
...
This is currently solved by defining callback actions, and launching actions from inside an action by injecting the actionExecutor.
chaining actions. Instead of launching the workflow directly then clicking on publish (in CE this launches the activate action) we have configured a "startPublication" Action which opens a dialog for adding needed parameters and this dialog then calls back into the activate action, which launches the workflow command.
I don't think this is all wrong, but it is a total mess in the configuration tree and very hard to explain to customers and ends up in total craziness in the MVHs.
Proposals
Chained Actions
...
Here's an example of the configuration:
[SCREENSHOT]
...
The reason why I prefer this one is because it is generic and can be reused for confirmation dialogs. You want to open some sort of dialog before doing any action, just chain it.
Action Composition
Meaning building more complex code and the current Action API is not flexible enough to do it the right way IMO.
Overview
Content Tools