VBCS · Fusion · Intermediate
Oracle Visual Builder: Applications That Outlive Their First Release
Nineteen modules, nineteen labs, and an application delivered end to end
Building the first screen in Visual Builder takes an afternoon. What takes the rest of the project is everything that follows: where state lives once four pages need it, what happens to your service connections when Fusion changes shape, why the filter you put on a table is not security, and how any of it survives a quarterly update. This course is about those. It is for the consultant or developer who has been asked for a screen Fusion does not have — and it starts by asking whether you need one at all. It assumes you can read JavaScript and JSON and know what a REST call is. It does not assume you have opened Visual Builder.
EGP 3,000
176 lessons · 503 min
What you will be able to do
- Decide whether a requirement needs an application at all, or a personalisation you already have.
- Build pages, flows and navigation that somebody else can find their way around.
- Choose where a piece of state lives, and say why, before four pages depend on it.
- Connect to Fusion through service connections that survive the data changing shape.
- Write action chains that are readable six months later and fail in a way somebody can act on.
- Secure an application on the server side, knowing that anything the browser received is the user's.
- Move an application between environments without carrying test endpoints into production.
- Read a quarterly update for the two things that actually break a Visual Builder application.
What you should know first
- You can read JavaScript and JSON, and you know what a REST call is and what it returns.
- You have seen a Fusion implementation from the inside, or have taken the Fusion Technical course.
- A Visual Builder instance you can build in. A trial covers everything except the environment-promotion module.
- No prior Visual Builder, JET or front-end framework experience is assumed.
What you will cover
1. Module 0 · Orientation
What this course covers, what it deliberately does not, and the environment you will need.
- 1What you will be able to do3 min
- 2What this course is not3 min
- 3The environment you need3 min
- 4How to use the labs3 min
2. Module 1 · What VBCS is, and when you need it
The longest orientation module in the catalogue, because the honest answer is often that you do not need this at all.
- 1What the product actually is2 min
- 2The four things people ask it to do3 min
- 3When you genuinely need Visual BuilderFree preview3 min
- 4Personalisation first: what you already have2 min
- 5Visual Builder against APEX3 min
- 6The maintenance bill nobody quotes3 min
- 7Where it sits in the Oracle estate3 min
- 8What breaks: the application that should not exist3 min
- 9Lab briefing · Six requirements, one recommendation each3 min
3. Module 2 · The workspace and your first app
The designer, the parts of it you will live in, and a trivial application built end to end so the moving parts are visible.
- 1The designer, and the four places you will live3 min
- 2Applications, flows and pages3 min
- 3Your first application, start to finish3 min
- 4Preview, and what it is not2 min
- 5The visual designer and the code behind it3 min
- 6Naming, and why it matters more than it should3 min
- 7The browser tools are your real debugger3 min
- 8What breaks: the first-week mistakes2 min
- 9Lab briefing · Build it, run it, break it3 min
4. Module 3 · Pages, flows and navigation
How an application is put together, and the structure decisions that are cheap now and expensive at page fifteen.
- 1Flows: the unit that decides your structure3 min
- 2Navigating between pages2 min
- 3Passing data when you navigate3 min
- 4The shell page and what belongs on it3 min
- 5Deep links and the URL3 min
- 6Layouts, and the page that grew2 min
- 7Building for somebody who did not build it3 min
- 8Accessibility, from the start3 min
- 9What breaks: three navigation failures3 min
- 10Lab briefing · Four pages that hang together3 min
5. Module 4 · Variables, types and where state lives
FLAGSHIP. The decision that shapes every module after it. State put in the wrong scope is not a bug you fix — it is a rewrite you postpone.
- 1What a variable is here3 min
- 2The scopes, and what each one meansFree preview3 min
- 3Choosing a scope, deliberately2 min
- 4Types, and why you should declare them3 min
- 5Types that mirror a service3 min
- 6Computed values and expressions3 min
- 7Variables that persist3 min
- 8The event that fires when state changes3 min
- 9State that four pages need3 min
- 10Naming state so it is findable3 min
- 11What breaks: four state failures3 min
- 12Lab briefing · Move state and watch it break3 min
6. Module 5 · Data: business objects and external services
Where your data actually lives, and the decision between keeping some of it here and reading all of it from somewhere else.
- 1Business objects: your own database2 min
- 2When to keep data here, and when not to3 min
- 3Designing a business object3 min
- 4Object rules and triggers3 min
- 5Importing and exporting data3 min
- 6The endpoints your objects expose3 min
- 7External services: the other half3 min
- 8Reference data and lookups3 min
- 9What breaks: three data failures3 min
- 10Lab briefing · Two sources, one screen3 min
7. Module 6 · Connecting to Fusion
FLAGSHIP. The connection layer decides your data contract, your credentials and your performance. All three are expensive to change later.
- 1What a service connection is3 min
- 2Creating one against a Fusion REST APIFree preview3 min
- 3Authentication, and whose identity is used3 min
- 4Why a shared service account is usually wrong3 min
- 5Query parameters, filtering and fields3 min
- 6Pagination, properly3 min
- 7Writing back to Fusion3 min
- 8When the shape changes underneath you3 min
- 9Calling an OIC integration instead3 min
- 10Handling a service that is down3 min
- 11CORS and the errors it produces3 min
- 12What breaks: four connection failures3 min
- 13Lab briefing · Connect, over-fetch, then fix it3 min
8. Module 7 · Binding data to the page
Getting data onto a screen and back off it, which is most of what an application does and where most of the small daily problems are.
- 1Binding, and what the framework does for you3 min
- 2Tables and lists3 min
- 3Forms and two-way binding3 min
- 4Formatting: dates, numbers and currency3 min
- 5Arabic and right-to-leftFree preview3 min
- 6Conditional display3 min
- 7Sorting, filtering and searching3 min
- 8Empty, loading and error states3 min
- 9What breaks: three binding failures3 min
- 10Lab briefing · One screen, every state3 min
9. Module 8 · Action chains and events
FLAGSHIP. Where the business logic ends up whether or not anybody planned it, and where an application becomes unreadable one convenient shortcut at a time.
- 1What an action chain isFree preview3 min
- 2Events: what can start one3 min
- 3The common actions3 min
- 4Conditions and branching2 min
- 5Chains that call chains3 min
- 6Waiting: asynchronous steps3 min
- 7Failure inside a chain3 min
- 8JavaScript, and when to reach for it3 min
- 9Keeping a chain readable3 min
- 10Debugging one that misbehaves3 min
- 11Logic that does not belong here3 min
- 12What breaks: four action chain failures3 min
- 13Lab briefing · A chain that survives being read3 min
10. Module 9 · Fragments, components and reuse
Building something once, and the point at which reuse stops paying for itself.
- 1The component library you already have3 min
- 2Fragments: a piece of page you reuse3 min
- 3When to make one3 min
- 4Custom components3 min
- 5Sharing across applications2 min
- 6Theming and staying consistent3 min
- 7What breaks: two reuse failures3 min
- 8Lab briefing · Extract a fragment properly3 min
11. Module 10 · Validation and error handling
Telling a user what is wrong in a way they can act on, and knowing which of your checks actually stop anything.
- 1Where validation can live3 min
- 2Client-side validation is a courtesyFree preview3 min
- 3Field-level and form-level3 min
- 4Messages a user can act on3 min
- 5Reading an error from a service3 min
- 6Errors in Arabic3 min
- 7Failing without losing the work3 min
- 8Logging, for somebody who is not there3 min
- 9What breaks: three validation failures3 min
12. Module 11 · Security: who sees what
FLAGSHIP. A Visual Builder application runs in the browser, so anything it was sent is the user's. Every control that matters is on the other side of that line.
- 1Where the trust boundary is3 min
- 2Filtering in the UI is not securityFree preview3 min
- 3Hiding a field sends it anyway3 min
- 4Filter at the source2 min
- 5Identity propagation, properly2 min
- 6Roles inside your application3 min
- 7Securing business object endpoints3 min
- 8Secrets do not go in an application3 min
- 9What ends up in a log or a URL3 min
- 10What breaks: four security findings3 min
- 11Lab briefing · Attack your own application3 min
13. Module 12 · Responsive and mobile
The same application on a phone, and the honest question of whether a phone is what was actually being asked for.
- 1Responsive, or a mobile application3 min
- 2How the layout responds3 min
- 3A table on a phone3 min
- 4Touch, and what changes3 min
- 5Testing at real sizes3 min
- 6Right-to-left on a small screen3 min
- 7What breaks: two mobile failures3 min
- 8Lab briefing · Make one screen work on a phone3 min
14. Module 13 · Extending Fusion applications
Changing a Fusion page rather than building beside it. A different model with a different lifecycle, and the boundary the Technical course draws from the other side.
- 1Extending against building beside2 min
- 2What an extension can change3 min
- 3The workspace and the lifecycle3 min
- 4Where this meets Page Composer2 min
- 5Sandboxes and coordination3 min
- 6Testing an extension3 min
- 7Surviving a quarterly update3 min
- 8When to stop extending3 min
- 9What breaks: three extension failures3 min
- 10Lab briefing · Extend, then update3 min
15. Module 14 · Source control, environments and publishing
Getting an application from your screen to somebody else's, repeatedly, without carrying test endpoints into production.
- 1What a publish actually doesFree preview3 min
- 2Versions, and living with two3 min
- 3Source control, and why a visual tool still needs it2 min
- 4Branching and more than one developer3 min
- 5Environments, and what differs between them2 min
- 6Making endpoints configurable3 min
- 7The promotion checklist2 min
- 8Rolling back3 min
- 9Automating it3 min
- 10What breaks: four promotion failures3 min
- 11Lab briefing · Promote and prove it is isolated3 min
16. Module 15 · Performance
Why an application is slow, which is almost always what it asked for rather than how it was built.
- 1Measure before you change anything3 min
- 2Over-fetching: the usual cause3 min
- 3Too many calls3 min
- 4Rendering a large list3 min
- 5What to load, and when3 min
- 6Caching, and when it lies3 min
- 7What breaks: three performance failures3 min
- 8Lab briefing · Ten times the data2 min
17. Module 16 · Testing an application with no test framework
What "tested" means when there is no unit test to write, and how to make it mean something anyway.
- 1What "tested" means hereFree preview2 min
- 2Choosing data that would fail3 min
- 3Testing without the other system3 min
- 4Testing the failure paths3 min
- 5Testing both locales3 min
- 6Accessibility and keyboard3 min
- 7What breaks: the sign-off that proved nothing3 min
- 8Lab briefing · A test plan somebody would sign3 min
18. Module 17 · Quarterly updates and VBCS
Visual Builder updates, Fusion updates, and your application sits between two calendars it does not control.
- 1Two calendars, not one2 min
- 2Reading a release note for risk3 min
- 3Component and runtime versions3 min
- 4A regression pack for an application2 min
- 5Testing in the update window3 min
- 6What breaks: after the update3 min
- 7Lab briefing · Assess a real release note2 min
19. Module 18 · Capstone: one application, delivered
A realistic brief taken from requirement to handover, with every module in this course applied where it belongs.
- 1The brief2 min
- 2Deciding before building2 min
- 3Building it3 min
- 4Proving it3 min
- 5Publishing and handing over2 min
- 6Where to go next3 min