Oracle Fusion Technical: Reports, Data, Integrations and Extensions · Module 13 · Groovy in Application Composer
Validation rules that help rather than annoy
Lesson 130 of 177 · 2 min
Write a rule whose MESSAGE TELLS THE USER WHAT TO DO. That is the difference between a validation and an obstacle. "Invalid value" is a refusal. "A cost centre is required for expense lines over 5,000; ask your finance contact if you do not know which to use" is a rule that gets satisfied. The user cannot see your condition, and every second they spend guessing what you meant is a second the rule cost the business. THE DIFFERENCE BETWEEN BLOCKING BAD DATA AND BLOCKING WORK is the judgement this lesson exists for. A rule that refuses a save is absolute: it applies to the correction as well as the mistake, to the exception as well as the rule, and to the person doing something legitimate that nobody anticipated. So before writing a validation, ask what happens to the legitimate exception. A rule saying an invoice date cannot be in…
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