Skip to main content
Solved

Custom Event on HISTORY_LOG_TAB

  • November 19, 2021
  • 7 replies
  • 410 views

COVJAMIEB
Hero (Partner)
Forum|alt.badge.img+11

Hello!

---Applications 9

---History Logging Enabled for a number of tables.

Today I have created an Event against the HISTORY_LOG_TAB. As soon as the event is enabled records stopped being created by history logging. Disable the event and the history logging begins working as expected.

Anyone came across this before?

Thanks,

Jamie

Best answer by knepiosko

Hi @MitJamieB 

 

Please check predefined event: HISTORY_LOG_MODIFIED. Try this achive your goal.

 

View original
Did this topic help you find an answer to your question?
This topic has been closed for replies.

7 replies

NickPorter
Superhero (Customer)
Forum|alt.badge.img+18
  • Superhero (Customer)
  • 354 replies
  • November 19, 2021

Could depend on how your event is configured.

If you set it to run BEFORE the write to the table, you could then prevent it from completing the write, depending on what you event/action was defined to do.

Nick


COVJAMIEB
Hero (Partner)
Forum|alt.badge.img+11
  • Author
  • Hero (Partner)
  • 218 replies
  • November 19, 2021

Hi Nick. Thanks for the response. 
 

the event is set to trigger after a new record is created. 


Forum|alt.badge.img+12
  • Hero
  • 217 replies
  • November 19, 2021

Could there be some sort of failsafe against recursive effects? If your event does something that writes to a table with history logging turned on, your event could cause an infinite loop, no? Not sure how IFS would know that, though, unless Oracle has built-in circular reference checks.

 

Joe Kaufman


COVJAMIEB
Hero (Partner)
Forum|alt.badge.img+11
  • Author
  • Hero (Partner)
  • 218 replies
  • November 19, 2021

Hi Joe,

 

I did think they initially, however I checked this by creating a custom LU and updating that instead. Custom LU didn’t have logging on and still the same issue ☹️


Forum|alt.badge.img+6
  • Sidekick (Customer)
  • 17 replies
  • December 16, 2021

I am having the same issue so I’m also interested if someone has a solution for this :)

 


Forum|alt.badge.img+16
  • Superhero (Partner)
  • 446 replies
  • Answer
  • January 25, 2022

Hi @MitJamieB 

 

Please check predefined event: HISTORY_LOG_MODIFIED. Try this achive your goal.

 


durette
Superhero (Customer)
Forum|alt.badge.img+19
  • Superhero (Customer)
  • 534 replies
  • February 17, 2022

“After” triggers will still cause the whole transaction to fail if something goes wrong. If you feel comfortable posting your event action code, we might be able to help you more.


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings