Here are the practical ways to get only your custom logic (most of this from ChatGPT, so don’t shoot the messenger ):

1. Turn off (or replace) the standard event action

• Go to Solution Manager → Configuration → Events, open the event, then Show Actions. If the standard action is editable in your setup, disable it; otherwise duplicate it and use your copy (custom-defined) instead, then leave the original disabled/not subscribed. Note that system-defined event actions are read-only except for subscription settings, so you typically can’t change their logic/conditions. Events - Technical Documentation For IFS Cloud

2. Use a “Before / Validation” Workflow to block the transaction (if your goal is to prevent the underlying transaction from proceeding)
   Create an Event Action of type Workflow, set Type = Validation and Timing = Before. If your validation fails, the transaction is rolled back and subsequent actions (standard ones included) won’t run. This is the supported way to stop processing rather than “short-circuiting” actions. Manage Event Actions - Technical Documentation For IFS Cloud

3. Avoid double notifications when mixing mechanisms
   If your duplicates come from using PDF_REPORT_CREATED (event action) and a Report Rule – Email report, pick one path. Using both can result in two emails because rules don’t override existing event-based notifications. The docs also recommend the Report Rule approach for future-proofing. https://docs.ifs.com/techdocs/25r1/050_reporting/000_reporting/251_operational_reporting/021_report_output/110_email_reports/

Hello IFS Community,

I created a custom event action, PDF_REPORT_CREATED, and it is working properly according to the request. However, the standard IFS action is also being triggered, causing the recipient to receive two emails.

Does anyone have advice or ideas on how to disable the default IFS action? I am specifically referring to the NCR.

 

 

 

Thank you,

Can I see the implementation of your custom event action?