Found some problems with jasper when using it to print orders/invoices:
1 - when setting the FileNamePattern as implemented on https://idempiere.atlassian.net/browse/IDEMPIERE-4753 - with a value like @DocumentNo@, when setting the filename the system throws a Cross-tenant error because the ID that receives is the order ID, and the table is the invoice ID
2 - jasper fails silently when the jasper or jrxml file does not exist - at least it must show error in log and save the error in AD_PInstance
modify "Process Order" workflow to send the invoice after the order is completed (before sending email there is a "Wait Commit" node
here we found two problems:
1 - the workflow is sending the invoice print format with the order ID - which leads to sending a PDF with wrong information (or empty if you add AD_Client_ID safety to the jasper query)
2 - the PDF in the email is sent with a name different than defined in the print format file pattern
Found some problems with jasper when using it to print orders/invoices:
1 - when setting the FileNamePattern as implemented on https://idempiere.atlassian.net/browse/IDEMPIERE-4753 - with a value like @DocumentNo@, when setting the filename the system throws a Cross-tenant error because the ID that receives is the order ID, and the table is the invoice ID
2 - jasper fails silently when the jasper or jrxml file does not exist - at least it must show error in log and save the error in AD_PInstance