Skip to main content

Hello.

I’m trying to understand an event action but some informations I need are missing.

So basically, we have a custom event which sends an email with an attached PDF file but the PDF file needs a review.

This is the custom event that I could find : 

 

But how is generared the PDF file? 

As I’m now discovering IFS cloud, I think we are on 24R2, by clicking on technical documentation on the main menu, the 24R2 version is selected by default.

The event action is only performed when a specific Event occurs.  You should be able to see which Event this Event Action is connected to.  The Event should help you to see where the PDF is coming from.

If I had to guess, this Event Action is probably being performed from the PDF_CREATED or similar Event (i.e. when that Event is triggered), and the Event Action perhaps also has a Condition in the field in your screenshot that ensures it only sends this email when a specific type of PDF was created (i.e. you wouldn’t want to send this when an invoice PDF was created).

HTH,

Nick

I used to work on IFSAPP and the IFS cloud version is confusing me a lot as I don’t fully understand how that works.

I found this event :

About the condition, I see it’s filtered on the REPORT_TITLE field which is “Service Quotation” and it’s the only condition used.

About the report itself, how is it possible to update it? or is that a standard template?

actually, this event has 2 actions :

  • the first one has the condition “REPORT_TITLE = Service Quotation”
  • the 2nd one has the condition “PDF2_PARAMETER_2 = UNIFORM_PAYMENT_ADVICE_REP”

PDF_REPORT_CREATED is a standard/out of the box Event that triggers when a PDF report layout is created.  You can’t directly change this Event (without a mod).  You can change existing and create new report layouts used by reports (e.g. create a new layout for your report type (service quotations)), and details from that layout would then be available as PDF parameters.  Note that the various PDF Parameters the system, e.g. PDF_PARAMETER_2 are also predefined so while they will pick up details from the report layout, you can’t change them to point to something else.  For example, if PDF_PARAMETER_1 is the email address coming from the data that generated the PDF, you cannot make PDF_PARAMETER_1 be something else.

Fundamentally Events and Event Actions are not really any different than prior versions that you say you are familiar with.

​@NickPorter with further investigations, we noticed that the actual report used to send to the suppliers is correct and we won’t have to make a custom action for that, not even having to make a custom report.

Thanks

Terms & ConditionsCookie settingsAccessibility statement