topic DocumentListComponent action handler customization not working in Alfresco Forum

DocumentListComponent action handler customization not working

jameswu1818 — Thu, 06 Sep 2018 19:09:26 GMT

Someone please help us. In DocumentListComponent, we want to run our customized code for download action. so that we can run our code before calling the default ‘download’ handler; or not calling the default handler at all. According to documentshttps://alfresco.github.io/adf-component-catalog/compo

Re: DocumentListComponent action handler customization not working

dvuika — Fri, 07 Sep 2018 08:39:55 GMT

You can take full control over the action execution using "(execute)" event. In that case you won't need hacking services:

<content-action
  target="all"
  title="Custom actions"
  (execute)="runCustomAction($event)">
</content-action>‍‍‍‍‍

And in the controller class:

runCustomAction(event) {
  console.log(event);
}‍‍‍

Re: DocumentListComponent action handler customization not working

jameswu1818 — Fri, 07 Sep 2018 14:14:35 GMT

Thank you for your answer. But why handler does not work though. Since it is documented, there must be a reason to use it. In our case, we want to reuse the default download code.

  customDownloadBehavior(obj: any) {
    if (do_something_in_our_biz_logic(obj)) {
     this.originalDownloadHandler(obj);

}
}

Re: DocumentListComponent action handler customization not working

dvuika — Fri, 07 Sep 2018 14:22:12 GMT

Maybe related to "this" context and how you invoke the old one. Anyway, you can check the source code: alfresco-ng2-components/document-actions.service.ts at development · Alfresco/alfresco-ng2-components · GitHub The only thing the "download" handler does is calling this line of code:

this.nodeActionsService.downloadNode(obj);‍

You can make that call from your handlers as well, or step thought the code in the debugger to see what's going on.

Re: DocumentListComponent action handler customization not working

SébastienVallet — Sat, 30 Jan 2021 17:14:57 GMT

Same issue here, I followed the documentation and my custom handler "delete" is not calling my custom behaviour.

I then used the "execute" event, but I needed to rewrite the DocumentActionsService#delete method myself.