GENEXUS Rule Triggering Events

Rule Triggering Events

Most transaction rules allow us to add a triggering event or time to them whenever necessary.

By adding a triggering event or time to a rule, we will be indicating that the rule will have to be executed at the particular time specified.

Rule Triggering Order

When a Transaction has been confirmed, the events will be triggered in the following order:

• BeforeValidate
• Check Extended Table (Internal GeneXus triggering event; Refcall rules are triggered here).
• Confirm data
• Check Optimistic Concurrency (Internal GeneXus triggering event; Record modification and locking are checked in this event).
• AfterValidate (first level)
• BeforeInsert / BeforeUpdate / BeforeDelete
• DB is updated
• AfterInsert / AfterUpdate / AfterDelete
  
  • BeforeValidate Level
  • Confirm data
  • AfterValidate Level
  • BeforeInsert/Update/Delete Level
  • AfterInsert/Update/Delete Level 
• AfterLevel Level
• DB is updated; the success message is displated ('Data has been successfully added')
• BeforeComplete
• Commitment of the LUW
• AfterComplete