Oracle Visual Builder: Applications That Outlive Their First Release · Module 5 · Data: business objects and external services
Business objects: your own database
Lesson 45 of 176 · 2 min
What Visual Builder GIVES YOU, what it is GOOD FOR, and the fact that IT IS A REAL DATABASE WITH REAL CONSEQUENCES. Business objects are the product's own data store, and the phrase people use for them — "just a table for the app" — is the one that gets estates into trouble. WHAT YOU GET IS A TABLE WITH FIELDS, TYPES AND RELATIONSHIPS, CREATED WITHOUT A DBA. Rows persist, the tool builds a REST endpoint for it automatically, and a page can read and write it in minutes. For data that genuinely belongs to this application and nowhere else, that is exactly right and there is nothing to argue about. WHAT IT IS GOOD FOR IS THE THING FUSION DOES NOT HOLD. An approval note somebody typed, a checklist state, a local mapping between two systems' codes. Data whose only reader is this application, whose only writer is this…
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