Oracle Visual Builder: Applications That Outlive Their First Release · Module 5 · Data: business objects and external services
Object rules and triggers
Lesson 48 of 176 · 3 min
Logic that runs ON THE SERVER rather than IN THE BROWSER, and why that distinction is THE WHOLE OF MODULE 11 IN MINIATURE. A business object can carry rules that run when a row is created, changed or deleted — and where they run is the only thing about them that matters. EVERYTHING YOU HAVE BUILT SO FAR RUNS IN THE BROWSER, WHICH MEANS THE USER CONTROLS IT. A validation on a page is a courtesy: it tells somebody their input is wrong before they submit it. It does not PREVENT anything, because the endpoint is still there and can be called directly. AN OBJECT RULE RUNS ON THE SERVER, SO IT CANNOT BE BYPASSED. Whether the row arrived from your page, from another application, or from somebody with the endpoint and a bit of curiosity, the rule runs. That is the entire difference and it is the difference between…
The full lesson is part of the course
The video, the complete written lesson and the module quiz are included in Oracle Visual Builder: Applications That Outlive Their First Release, with a certificate on completion and a fourteen-day refund window.
In this module: Module 5 · Data: business objects and external services
- 1Business objects: your own database
- 2When to keep data here, and when not to
- 3Designing a business object
- 4Object rules and triggers
- 5Importing and exporting data
- 6The endpoints your objects expose
- 7External services: the other half
- 8Reference data and lookups
- 9What breaks: three data failures
- 10Lab briefing · Two sources, one screen