topic Re: Fire a registered action from a custom html link in Alfresco Archive

Fire a registered action from a custom html link

mtsiak — Thu, 22 Sep 2016 09:53:14 GMT

The idea is to simplify the document's view. One task is to separate the most used actions (our custom and alfresco' s built in actions) with the rest. One thought is to create a custom panel (Favorite Actions) in the document-details page, above the Document Actions.How can we add (javascript) acti

Re: Fire a registered action from a custom html link

sujaypillai — Thu, 22 Sep 2016 10:29:06 GMT

You may check out this tutorial here.

Re: Fire a registered action from a custom html link

mtsiak — Thu, 22 Sep 2016 11:03:01 GMT

Sujay thank you for your reply. We have created a doclib javascript action with success, using the above tutorial.

But these actions can be set visible only in available actionGroups, such as 'document-details'.

The question is how could i set visible this action in our custom panel above the 'Document Actions'. Or what javascript action is actually been fired, so as to hardcode it in our panel's ftl.

Re: Fire a registered action from a custom html link

sujaypillai — Thu, 22 Sep 2016 11:16:57 GMT

Does this help you ... Add, remove or replace components on Share’s Document Details page | Erik Winlöf's blog

Re: Fire a registered action from a custom html link

mtsiak — Thu, 22 Sep 2016 11:24:41 GMT

I have read that as well and guided me to create the custom panel. Thank you.

But how do I add actions in the acme-sample sub-component? And not in the document-details? Should I extend the DefaultDoclistActionGroupResolver and will work?

Re: Fire a registered action from a custom html link

mtsiak — Thu, 22 Sep 2016 11:46:41 GMT

I hardcoded in the ftl of the custom panel

<div class="my.doclib.action.id" id="myJavascriptFunctionNameThatCallsAWebScript">
<a title="a title" class="action-link" href="#"
style="background-image:url(/share/res/components/documentlibrary/actions/document-assign-workflow-16.png)">
<span>my action</span>

</a>
</div>

and the action is called as it was in the document actions panel. It is a partial solution as we can not use the evaluators.