Oracle Fusion Technical: Reports, Data, Integrations and Extensions · Module 13 · Groovy in Application Composer
Triggers and the order they fire in
Lesson 131 of 177 · 2 min
BEFORE and AFTER, on CREATE and on UPDATE — and the sequence determines whether your field has a value yet. A BEFORE trigger runs while the record is still being assembled. That is where you SET things: default a field, derive a value, normalise an input. Setting a field in a before-insert trigger works because the record has not been written yet. An AFTER trigger runs once the record exists. That is where you do things that need the record to be real: create a related record that references it, send a notification, update something else. Setting a field on the current record in an after trigger is the classic mistake — the write has happened, and depending on the object your change either does nothing or causes a second write. THE SEQUENCE PROBLEM IN ONE SENTENCE: a field populated by another trigger, or by a formula, or by the…
The full lesson is part of the course
The video, the complete written lesson and the module quiz are included in Oracle Fusion Technical: Reports, Data, Integrations and Extensions, with a certificate on completion and a fourteen-day refund window.
In this module: Module 13 · Groovy in Application Composer
- 1Where Groovy runs, and where it does not
- 2The language subset, quickly
- 3Validation rules that help rather than annoy
- 4Triggers and the order they fire in
- 5Object functions and reuse
- 6Performance: the rule that runs a million times
- 7Debugging without a debugger
- 8What breaks: three Groovy failures
- 9Lab briefing · A rule, and its performance