Fusion Cloud extensibility
Extend Fusion without breaking the next update.
Visual Builder Studio, Redwood, Application Composer, Page Composer, Journeys and APEX: the sanctioned ways to make Fusion do what your business needs, built so quarterly updates never take them down.
Configuration
- Delivered options
- Flexfields & lookups
- Approval rules
Composers
- Application Composer
- Page Composer
- Journeys
Visual Builder Studio
Redwood app extensions & standalone apps
Git · pipelines · Fusion REST
Beyond the boundary
- APEX on ATP
- OIC
- OCI services
Overview
Extensions & Redwood, done properly.
Every Fusion customer hits the same wall: the process is ninety percent standard and the last ten percent is the part the business cares about. The wrong response is a workaround in a spreadsheet or an unsupported hack. The right one is Oracle's extensibility framework, used with discipline.
AMTEX builds extensions in the order Oracle supports them: configuration first, then Application Composer and Page Composer, then Visual Builder Studio for Redwood pages and standalone apps, then APEX or custom services on OCI when the requirement genuinely leaves the Fusion boundary. Every extension lives in VB Studio Git, is promoted by pipeline and is regression-tested each quarter.
Technologies
- Oracle Visual Builder
- Redwood UX
- Application & Page Composer
- Oracle APEX
- REST APIs
- Fusion Approval Workflows (BPM)
- GitLab CI
What we deliver
Capabilities
Everything AMTEX builds, configures and runs across Extensions & Redwood.
Visual Builder Studio
App extensions to Redwood pages, standalone web apps over Fusion REST, with Git-backed projects and environment promotion.
Redwood customisation
Business rules, page layouts, field visibility and dynamic containers in the new Redwood UX without forking the page.
Application Composer
Custom objects, fields, Groovy validation and triggers in CX, HCM and ERP where Oracle exposes them.
Page & Structure Composer
Sandboxed UI tailoring, navigation and role-based page variants that survive updates.
HCM Journeys & guided processes
Onboarding, transfers and leaver journeys with tasks, documents and integrations to identity and payroll.
Oracle APEX on ATP
Companion applications for what Fusion does not model: registers, trackers, approvals with audit trails, reading Fusion data via REST.
Fusion REST & SOAP services
Using and extending the Fusion API surface correctly: business objects, child resources, custom object APIs, BIP-backed reads.
Approval workflows (BPM)
Approval rules, stage design, escalation and delegation across Procurement, Payables, Expenses and HR transactions.
Sandboxes & update lifecycle
Sandbox strategy, publish discipline, quarterly regression against your extensions, and a fast path when Oracle deprecates something.
Security for extensions
Custom roles, data security policies and OAuth for extension apps so access is auditable, not inherited.
The hard parts
Where these projects become difficult
The places programmes slip, and what we do about each one.
- 01
Update breakage
The problem
A quarterly update changes a page or deprecates an API and the extension stops working the morning after.
How AMTEX approaches it
Extensions only through supported layers, a regression suite that runs in the test pod each quarter, and a review of Oracle's readiness notes before every update.
- 02
Sprawl
The problem
Dozens of sandboxes, unpublished changes and nobody knows what is live.
How AMTEX approaches it
One sandbox per change, VB Studio Git as the record, a catalogue of every extension with its owner and business reason.
- 03
Extension where configuration would do
The problem
Code written for something a delivered option already handled.
How AMTEX approaches it
Configuration-first triage on every request; we say no to custom work when Oracle already delivers it.
- 04
Leaving the boundary too late
The problem
Forcing complex logic into Groovy or page rules that belongs in a proper application.
How AMTEX approaches it
Clear criteria for when a requirement moves to APEX or an OCI service, with Fusion as the system of record and OIC as the bridge.
How we work
From first conversation to steady state
01
Triage
Configuration, composer, VB Studio or external app: the decision made explicitly, with reasons.
02
Design
Data ownership, security, update risk and test plan agreed before code.
03
Build
In VB Studio Git or a sandbox, peer reviewed, promoted by pipeline.
04
Sustain
Quarterly regression, catalogue kept current, deprecations handled early.
FAQ
Common questions
Related solutions
Oracle Fusion Cloud ERP
Financials, Procurement, Projects and Order Management, implemented and extended with the integrations, reporting and automation a real enterprise needs around them.
Oracle Fusion Cloud HCM
Core HR, Payroll, Absence, Talent and Recruiting on Oracle Fusion Cloud HCM, with the payroll, benefits, identity and time integrations that make it complete.
Oracle Integration Cloud
Application, scheduled and event-driven integrations on Oracle Integration Cloud, engineered with error handling, observability and CI/CD so they run for years, not just through go-live.
Process Automation & RPA
Oracle Process Automation for the human-task workflows around Fusion, and RPA for the steps that have no API: intake, approvals, exceptions, re-keying and legacy screens, orchestrated together through OIC.
Extensions failing after updates, or a requirement Fusion will not meet?
We will tell you which layer it belongs in and what it will take.