Event action PDF_REPORT_CREATED and parameters

As far as I have seen many of them are always blank, so that’s normal. 

I don’t know about formal documentation, but its easy to create an event action to email yourself (hardcode the recipient email) and put all the parameters in the content so you can see their values.  Just be sure to put a prefix (e.g. “1:” before each parameter otherwise you won’t know which value comes from which when you get the info.  This way, regardless of what the docs say, you’ll know what’s coming from where with your data.

Nick

​@romsar 

You can find information on the IFS documentation about how the parameters in the PDF_REPORT_CREATED event are filled for standard reports, and the basic data setup needed.

I couldn’t find the link for Apps10 since the documentation is now moved but search for ‘E-Mail Reports’.

https://docs.ifs.com/ifsclouddocs/26r1/?openpage=https://docs.ifs.com/ifsclouddocs/26r1/Procurement/AboutEmailReports.htm

If the report you try to send is not included here, it’s highly likely that the PDF_PARAMETER fields are not used on those reports.

Cheers!

Damith

You can also trigger a first request to get the list of variables by including the following in the body : 

EVENT_DATETIME: &EVENT_DATETIME

LANGUAGE_CODE: &LANGUAGE_CODE

LAYOUT_NAME: &LAYOUT_NAME

MAIL_SUBJECT: &MAIL_SUBJECT

MAIL_TEXT: &MAIL_TEXT

NOTES: &NOTES

PDF_FILE: &PDF_FILE

PDF_FILE_NAME: &PDF_FILE_NAME

PDF_FILE_SENT_TO: &PDF_FILE_SENT_TO

PDF_PARAMETER_1: &PDF_PARAMETER_1

PDF_PARAMETER_10: &PDF_PARAMETER_10

PDF_PARAMETER_11: &PDF_PARAMETER_11

PDF_PARAMETER_12: &PDF_PARAMETER_12

PDF_PARAMETER_13: &PDF_PARAMETER_13

PDF_PARAMETER_14: &PDF_PARAMETER_14

PDF_PARAMETER_15: &PDF_PARAMETER_15

PDF_PARAMETER_2: &PDF_PARAMETER_2

PDF_PARAMETER_3: &PDF_PARAMETER_3

PDF_PARAMETER_4: &PDF_PARAMETER_4

PDF_PARAMETER_5: &PDF_PARAMETER_5

PDF_PARAMETER_6: &PDF_PARAMETER_6

PDF_PARAMETER_7: &PDF_PARAMETER_7

PDF_PARAMETER_8: &PDF_PARAMETER_8

PDF_PARAMETER_9: &PDF_PARAMETER_9

PRINT_JOB_ID: &PRINT_JOB_ID

PRINTER_ID: &PRINTER_ID

REPLY_TO_USER: &REPLY_TO_USER

REPORT_ID: &REPORT_ID

REPORT_PARAMETERS: &REPORT_PARAMETERS

REPORT_TITLE: &REPORT_TITLE

REPORT_TITLE_TRANS: &REPORT_TITLE_TRANS

REPORT_VARIABLES: &REPORT_VARIABLES

RESULT_KEY: &RESULT_KEY

STATUS: &STATUS

USER_DESCRIPTION: &USER_DESCRIPTION

USER_IDENTITY: &USER_IDENTITY

USER_MAIL_ADDRESS: &USER_MAIL_ADDRESS

USER_MOBILE_PHONE: &USER_MOBILE_PHONE

Hello ​@dsj 

I have to send customer invoices.

So in address / General Address info / Comm method, I added a contact, email communication method type, both with the default per method and default method & address checked filled, I don’t manage to get my email address on the event

I believe that customer email parameter would be &PDF_PARAMETER_1

If that’s not coming through with a value, double check your Customer setup

Hi ​@romsar 

Try the general parameter &#USER_EMAIL#. This is a generic parameter which returns the email address of the user who performed the action.

I’m not sure if the user persists for PDF_REPORT_CREATED or it replaces with the IFSPRINT user information. But worth the try.

/Damith

​@NickPorter from what I understand from the online IFS cloud documentation, it’s indeed the &PDF_PARAMETER_1 variable that I need to use but from my tests.

​@dsj I haven’t used that email address for my tests, in the “to” field, I just put my own email address so I could easily debug the different variables that IFS can provide.

​@NickPorter ​@dsj I have made a new test in which I used the create customer invoice function, on my first customer order, the event didn’t run, on my 2nd one, it ran and I’m wondering if the use of the PDF_REPORT_CREATED event is a good solution, but a report rule. What do you think?

Well, the PDF_REPORT_CREATED event will only run when a PDF is actually generated.  If you want to attach a copy of the invoice as a PDF to the email then this is the best way to go, because the invoices have to have been generated in PDF to make that happen.