Oracle Fusion Technical: Reports, Data, Integrations and Extensions · Module 13 · Groovy in Application Composer
Where Groovy runs, and where it does not
Lesson 128 of 177 · 2 min
Four execution points, and each is intended for something specific. Using the wrong one is where most Groovy trouble starts. TRIGGERS run when something happens to a record — before or after an insert, an update, a delete. They are for side effects: setting a field, creating a related record, sending a notification. VALIDATION RULES run when a record is saved and can REFUSE the save. They are for enforcing a rule, and they are the only execution point that can stop somebody. FORMULAS calculate a field's value from other fields. Read-only, derived, recomputed — and the right answer whenever somebody asks for a field that is always the sum or difference of two others. OBJECT FUNCTIONS are reusable logic you call from the others. They do not run on their own; they exist so a rule used in three places is written once. AND WHERE GROOVY DOES NOT RUN…
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