Oracle Fusion Technical: Reports, Data, Integrations and Extensions · Module 13 · Groovy in Application Composer
What breaks: three Groovy failures
Lesson 135 of 177 · 2 min
Three failures, and each is a different kind of expensive. ONE: A NULL NOBODY GUARDED. The rule reads a field that has not been filled in yet and throws. The user sees an unhelpful error on save and cannot proceed, and it only happens on the path where that field is entered later — so it passed testing, where the form was filled top to bottom. Lesson 2's guard is one condition. TWO: A RULE THAT FIRES DURING A BULK LOAD AND STOPS IT. The rule is correct for a person entering one record and wrong for ten thousand arriving at once: it is slow, or it depends on a field the load does not supply, or it throws on one row and the load halts. The load fails, the message names the rule, and the connection between a validation somebody wrote months ago and a conversion failing at midnight…
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