Oracle Fusion: Configuration vs Extensibility

Decision Flow

Use this flow to triage any requested change. Keep SaaS core clean and push variability to configuration or the edge.

INTAKE

Start

Describe the need in user language. Identify module, actors, inputs, outputs.

CONFIGURATION

Can delivered configuration meet it?

Try FSM setup, roles and policies, flexfields, OTBI or BI Publisher, BPM approvals, Redwood branding.

Yes → Stop

Document setup. Add to configuration registry. Validate performance and security.

IN-APP EXTENSIBILITY

Need light UI or logic only?

Fields, conditional UI, approvals, simple validations using sandboxes, Page or App Composer, flexfields, rules.

Yes → Proceed in-app

Sandbox, promote with setup tools. Add telemetry and performance checks.

SIDE-BY-SIDE (PaaS)

Complex logic, new process, or heavy UI?

Build outside on PaaS. Integrate with REST, events, and OIC. Keep SaaS the system of record where appropriate.

Yes → Build outside

Use Visual Builder, OIC, Functions, DB services. Version, test, monitor. Avoid tight coupling.

Changing SaaS core?

Altering delivered objects or patching internals is prohibited. Redesign the requirement or move to PaaS.

Comparison Matrix

Path	What it is	Pros	Cons	Typical uses	Risk
Configuration only	Setup, roles and policies, flexfields, approvals, OTBI or BI Publisher, Redwood branding	Fast, upgrade safe, lowest TCO, supported	Limited for edge cases	Standard policies, small field adds, reports	Low
In-app extensibility	Page or App Composer, sandboxes, flexfields, declarative logic, approval rules	Upgrade safe, native UX, central governance	Can clutter UX, performance needs discipline, not for heavy logic	Extra attributes, conditional UI, nuanced approvals	Low to Medium
Side by side (PaaS)	OIC, REST APIs, events, Visual Builder, OCI services	Max flexibility, scalable, isolates change, DevOps friendly	Higher cost and skill, integration lifecycle to manage	New microflows, portals, orchestrations, advanced validations	Medium
Core code changes	Altering SaaS internals or delivered objects	None in SaaS context	Breaks support and upgrades; prohibited	Not applicable	Prohibited

Operating Guardrails

Intake triage classifies request as configuration, in-app extensibility, or PaaS.
Upgrade safety: sandbox, metadata based, documented promotion path.
Performance baseline for each change with rollback plan.
API first integrations using REST, events, and OIC patterns.
Lifecycle discipline with versioning, environment promotion, observability.

Legend and Acronyms

SaaS: Software as a Service. Cloud software delivered and maintained by the vendor; customers configure but do not modify core code.
FSM: Functional Setup Manager. Fusion’s guided configuration area for functional setup tasks.
OTBI: Oracle Transactional Business Intelligence. Real-time, subject-area reporting over live transactional data.
BI Publisher: Oracle BI Publisher. Pixel-perfect reporting tool used for documents, labels, and formatted outputs.
BPM: Business Process Management. Approval rules and workflows engine used to model and execute approvals.
UX: User Experience. The overall experience of using the product’s interface and interactions.
UI: User Interface. The visual layer of screens, pages, and components a user interacts with.
PaaS: Platform as a Service. Cloud platform to build applications and services alongside Fusion without altering the SaaS core.
OIC: Oracle Integration Cloud. Managed integration service for connecting Fusion with other systems using adapters, flows, and mappings.
REST: Representational State Transfer APIs. Web service style used by Fusion for CRUD operations and integrations.
OCI: Oracle Cloud Infrastructure. Oracle’s IaaS platform hosting services like Functions, databases, and networking.
Visual Builder: Oracle Visual Builder. Low-code tool to build web and mobile apps that integrate with Fusion data and services.
DB: Database. Persistent data storage service; here referring to OCI database services.
TCO: Total Cost of Ownership. Combined cost to build, operate, support, and upgrade a solution over time.
System of record: The authoritative data source for a given business entity or process.
Telemetry: Operational measurements like performance and usage that help monitor extensions.
Redwood: Oracle’s design system and visual theme for Fusion user interfaces.