Skip to main content
Question

History Log tab Custom Event is not working

  • March 14, 2026
  • 1 reply
  • 37 views

Forum|alt.badge.img+1

Hi,

I wanted to keep track of custom events that are modified by any user, and then send an email notification. I planned to do this through the History Log, as it will log details about the changes. I created an event on the History Log entity so that whenever a change is logged, it will send an email to a specific user. However, the issue is that when this event is enabled, logs are not even being written to the table, but when it is disabled, everything works fine. Even after simplifying the event action to just NULL, the event is still not being triggered. Could anyone please help me identify the cause of this problem?

Thanks in Advance

Regards

 

 

1 reply

Forum|alt.badge.img+7
  • Do Gooder (Partner)
  • April 3, 2026

Hi ​@Tharshan ,

What’s happening

You created event on:

  • LU: HistoryLog
  • Table: HISTORY_LOG_TAB

But:

History Log is not a normal transactional LU

 It is:

  • system-generated
  • written internally by framework

 So:

  • Custom Events are not reliably triggered on this LU

 Why your event is not firing

In IFS:

  • Custom Events trigger on:
    • business LUs (CustomerOrder, PurchaseOrder, etc.)

But for:

  • HISTORY_LOG_TAB

 Insert is done via:

  • internal logging mechanism
  • sometimes bypasses event framework

 What people usually do

✔ Option 1 (recommended)

Create event on actual business LU, not HistoryLog

Example:

  • CustomerOrder
  • PurchaseOrder
  • WorkOrder

 Then:

  • trigger email when change happens

✔ Option 2

Use History Log only for:

  • reporting
  • auditing

NOT for triggering events

✔ Option 3 (advanced workaround)

If you must use history:

  • Create event on:
    • original LU
  • Check:
    • changed attributes

 Mimic history logic instead of depending on it

 Important check

Also verify:

  • “Event Enabled” = ON
  • Event type = New / Modify (correct)
  • Conditions are not too restrictive

But since:

even NULL action doesn’t trigger

 confirms:

  • event is not firing at all