...

The solution must be flexible and allow dynamic replacing of the behavior, e.g. by the workflow modules.

Proposal

Activation / Deactivation commands from the (old) admin interface module will be moved to the new admin-interface-legacy module and used to do the back-end workA fundamental premise here is that in M5 workflow will be an EE feature only. In CE only direct activation/deactivation will be available (no workflow engine involved).

The Activation / Deactivation actions will be created and linked to proper buttons in the action bar of required apps. Actions will execute 'activate' and 'deactivate' commands defined in appropriate catalogs (or the default ones) by calling CommandsManager.executeCommand(String catalog, String command, Map<String,Object> parameters) method.

The activation module will implement the basic CE de/activation operations by means of commands.

The workflow module will implement those commands using a workflow engine.