Hi Pietro,
this behaviour is actually expected in Magnolia 5.2.x even though it's going to
change in 5.3 (whose release is due this year in June) with the introduction of
Pulse tasks which will replace messages for workflow items. If you want to know
more about it, we've just published a blog post and a screencast with the
outcome of the latest development sprint
http://dev.magnolia-cms.com/blog/?p=811
In the meantime, what you can do is to extend
info.magnolia.ui.admincentral.shellapp.pulse.message.MessagePresenter, the
class responsible for displaying the message detail and in there override the
start(..) method. MessagePresenter gets MessageActionExecutor injected which
extends AbstractActionExecutor. So you can use its isAvailable(..) method to
apply the action availability rules. Finally, in your custom module descriptor
you will need to declare a component implementation like the one below. The
component needs to be under a container whose id is "admincentral". This should
override the declaration in the ui-admincentral module.
[code]<component>
<type>info.magnolia.ui.admincentral.shellapp.pulse.message.MessagePresenter</type>
<implementation>my.module.MyCustomMessagePresenter</implementation>
</component>[/code]
HTH,
Federico
--
Context is everything:
http://forum.magnolia-cms.com/forum/thread.html?threadId=94cc3681-817f-4779-91f8-46f62f16dbc7
----------------------------------------------------------------
For list details, see http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------
