In order to be familiar with this functionality, login to the application.  Go to either customer order or purchase order screen. While on the header of either screen, press F1. This will get you the help and on the header portion of the help screen there is a link to about email reports. Follow the instructions and you will see which action will fetch which PDF values and you should be able to get a detail information.

I also would suggest you to pay attention to your event variables. 

Hi @Lakmal Vithanachchi , Thank you for your suggestion. The event is currently working when I print the report. I was able to fetch required data using result key as a work around. But PDF_PARAMETER_1, PDF_PARAMETER_2 .. variables don’t fetch any value as you can see it in the above screen print. I was able to use those variables in some other environments. Data would be more accurate if I could get data from those variable.

Hi @MitDenukN 

I face exactly the same problem with PDF Variables empty.

They are populated when I manually print the PDF.

They are empty when I programmatically print the PDF.

Did you ever got a soluition for it, or is it indeed a bug in UPD12?

H @dominikdurrer , I got a workaround from the following community post.

Please let us know if you got something new on this issue.

https://community.ifs.com/framework-experience-infrastructure-cloud-integration-dev-tools-50/documentation-for-the-parameters-in-the-pdf-report-created-event-10199?postid=36799#post36799

Now we are struggling to find this issue again as we found an environment even this workaround also not working.

Hi @dominikdurrer , were you able to find a solution for this issue?

Hi,

there’s something that has helped us.

We’ve set the values in the RDF-File, of course at a point of time, when all values are available.

Important: Delete all values from the Pdf_Report_Event_Param_Tab before creating new parameters:

In text:

DELETE Pdf_Report_Event_Param_Tab
         WHERE report_id = '&VIEW';

         Pdf_Report_Event_Param_API.New_Parameter ('&VIEW', 'PDF_EVENT_PARAM_1', 'STRING', Contact_Util_API.Get_Supp_Comm_Method_Value(header_rec_.vendor_no, header_rec_.doc_addr_no, header_rec_.contact, 'E_MAIL'));
         Pdf_Report_Event_Param_API.New_Parameter ('&VIEW', 'PDF_EVENT_PARAM_5', 'STRING', header_rec_.authorizer);
         Pdf_Report_Event_Param_API.New_Parameter ('&VIEW', 'PDF_EVENT_PARAM_15', 'STRING', header_rec_.authorizer_email);
         Pdf_Report_Event_Param_API.New_Parameter ('&VIEW', 'PDF_EVENT_PARAM_6', 'STRING', next_order_no_);  

Hope this helps,

cheers,

Stephan

Thank you for the suggestion @stephan.lueck .

Those customers using the standard rdf and as I know, it is not allowed to do modifications to those.

Are you suggesting me to create a new report? Kindly advise me.

Those reports used to work properly earlier :( 

Hi @MitDenukN ,

yes, you’re right, we’ve modified the standard RDF.

We’ve been allowed to do this because this is part of our customization requirements.

As far as I know, modifications of the IFS standard RDF are allowed if the IFS given rules are followed.

At least that’s what I’ve done when working for an IFS partner in Germany.

So I would suggest that you check what could be possible for you - if creating a new report is the only option, OK, I don’t know. I’ve modified the IFS standard.

Cheers,

Stephan

Thank you so much for your opinion and I will check this & let you know :)