You should read this example about customer invoice to verify if standard configuration is enough.

https://www.sagecity.com/support_communities/sage_erp_x3/b/sageerp_x3_product_support_blog/posts/how-to-setup-a-workflow-to-email-invoice-to-customer-contact

Thank you for the reply.

Thank you for the reply.

Thanks, this example can be usefull.
But we need to send the file without user interaction, just after the report file is generated.
In your example user interaction is needed, user needs to click 'Print'

using 4GL you can automate the file creation to PDF (needs destination set up as PDF). and set as a task.

however for newer versions I understand that there is no option for PDF destination

Generating the PDF is not an issue. We already do that using 4GL.

The problem is that we need to send the PDF that was really generated but no event is triggered / available. When you do that as task, your task will ends and trigger its termination but nothing guarantees that the PDF was really generated (it can be still pending). It can work whith light PDFs (that generates quickly) but doesn't work with larger PDFs that take time to build by Crystal.

1) You can just put in a sleep, I've seen that 15 seconds is enough for heavy pdf's

2) Create a loop and keep on checking if the pdf is in the location you specified

1) Already did that, unfortunately 15 seconds is not enough for some of our PDF

2) Already did that, unfortunately the file is there quickly (if you check existence), but it is still writing, so if you send it it will be incomplete. You can also imagine to check the file size, but this is variable, so not really a solution

The only way we found for now is : run a batch that generates PDFs and then, one or few hours later run a batch that sends files. But this has other inconvenients as you need to keep track of file names and oher information

It woud be much easier and reliable if a specific event would be triggerd when the file completes.

1) Already did that, unfortunately 15 seconds is not enough for some of our PDF

2) Already did that, unfortunately the file is there quickly (if you check existence), but it is still writing, so if you send it it will be incomplete. You can also imagine to check the file size, but this is variable, so not really a solution

The only way we found for now is : run a batch that generates PDFs and then, one or few hours later run a batch that sends files. But this has other inconvenients as you need to keep track of file names and oher information

It woud be much easier and reliable if a specific event would be triggerd when the file completes.

I agree it would be much easier if...