Extend Oracle Fusion Safely With Sandboxes And Visual Builder Studio
how to extend Oracle Fusion with Visual Builder and sandboxes
Also searched as
- Oracle Fusion sandbox setup for customization
- Visual Builder Studio vs Application Composer Fusion
- publish sandbox changes Oracle Fusion
- Oracle Fusion custom page Visual Builder extension
Short answer
Fusion customizations - a new field, a validation rule, a redesigned page layout, or a standalone custom app - are built inside a sandbox, an isolated workspace that lets you make and test changes without affecting other users until you explicitly publish. Application Composer handles fields, objects, and business rules; Visual Builder Studio builds new standalone pages and full custom applications that can embed inside or sit alongside Fusion.
Applies to: Oracle Fusion Cloud ERP, SCM, and HCM, all monthly updates; Application Composer and Visual Builder Studio (VBS)
Build and publish a Fusion extension safely
- 1Open Navigator > Configuration > Sandboxes (or the Setup and Maintenance sandbox tool) and create a new sandbox scoped to the tools you need - Application Composer, Page Composer, or Visual Builder.
- 2Activate the sandbox; while active, your session shows the isolated version of the application, and changes you make are invisible to other users until publish.
- 3For field-level or object-level changes - a custom field, a formula field, a validation rule, a new child object - use Application Composer inside the active sandbox.
- 4For UI layout changes to an existing page - rearranging, hiding, or renaming regions and fields on a standard page - use Page Composer, also scoped to the sandbox.
- 5For a new standalone page, embedded component, or a fuller custom application, open Visual Builder Studio, create or open a VB application, and build against Fusion's REST APIs or a Fusion-provided business object.
- 6Test thoroughly inside the sandbox - functional behavior, security, and any integration touchpoints - since sandbox testing is your only safety net before the change becomes visible to everyone.
- 7Publish the sandbox once validated; publishing merges the change into the mainline and makes it visible to all users - there is no per-user rollback after publish, only a new corrective change.
- 8For Visual Builder applications, use VB Studio's separate deployment lifecycle (dev, test, production environments) rather than treating a Fusion sandbox as the VB app's own environment management.
What A Sandbox Actually Isolates
A sandbox is a metadata-level isolation layer: your changes to fields, page layouts, or business rules exist only within that sandbox's context until published, so other users continue seeing the current production configuration. It is not a separate database or a full environment clone - transactional data is shared and live throughout, only the customization metadata is isolated.
Application Composer Vs Page Composer
Application Composer changes the data model: new fields, objects, relationships, validation rules, and object workflow rules that affect how data behaves regardless of which page displays it. Page Composer changes presentation only: which fields show on a specific page, their order, labels, and visibility, without touching the underlying object. A requirement that sounds like a UI change sometimes actually needs an Application Composer field first, with Page Composer only placing it on the page.
When To Reach For Visual Builder Studio Instead
Application Composer and Page Composer extend existing standard pages and objects. When the requirement is a genuinely new page, a mobile-friendly custom form, or an application that combines Fusion data with an external source, Visual Builder Studio builds it as a proper application - with its own REST-based data model, UI components, and deployment pipeline - that can be embedded in Fusion navigation or run standalone.
Publishing Discipline
Because publishing a sandbox is a one-way merge visible to everyone, treat sandbox testing as seriously as any pre-production testing cycle: verify with realistic data, check security role visibility for the new field or page, and confirm the change does not break an existing integration that depends on the object's prior shape. A bad publish is corrected with another published change, not a rollback.
Common pitfalls
- !Making changes directly without an active sandbox where the tool allows it, losing the isolation and testing safety net sandboxes exist for.
- !Confusing a presentation change (Page Composer) with a data model change (Application Composer) and building the wrong one for the requirement.
- !Publishing a sandbox without testing security role visibility for a new field, so it either leaks to users who should not see it or is invisible to users who need it.
- !Treating a Fusion sandbox as if it were a full environment clone with isolated transactional data - it is not; live data is shared throughout.
- !Building a genuinely new page or application inside Application Composer's limits instead of using Visual Builder Studio, fighting the tool for a requirement it was not designed for.
- !Letting multiple people work unscoped changes in the same sandbox without coordinating, causing conflicting or overwritten customizations at publish time.
How an ERP-grounded AI assistant handles this
For a customization request, ERPray grounded on your Fusion configuration can tell you upfront whether it needs an Application Composer field, a Page Composer layout change, or a full Visual Builder Studio page - and check whether a similar field or rule already exists - so a team is not building a sandbox change that duplicates existing metadata or picks the wrong tool for the requirement.
Frequently asked questions
Can two people work in the same sandbox at once?
Technically yes if they both activate it, but it is risky - unscoped concurrent changes in one sandbox can overwrite or conflict with each other at publish time. Most implementations scope sandboxes per change or per developer and merge carefully, rather than sharing one sandbox freely.
What happens to my sandbox changes if I never publish them?
They remain isolated indefinitely and never affect other users; you can also explicitly discard a sandbox to remove the changes entirely if the customization is abandoned, without any cleanup needed in production.
Do Visual Builder Studio applications live inside the same sandbox as Application Composer changes?
No. VB Studio applications have their own project and environment lifecycle (dev, test, production) separate from a Fusion sandbox, even though a VB application can be embedded into Fusion's navigation and call Fusion's REST APIs or business objects.
Can I roll back a published sandbox change?
Not directly - publishing merges the change into the mainline for all users. If a published change needs to be undone, you create and publish a new corrective sandbox change rather than reverting to a prior state automatically.
Related
Fix Wrong Row Counts When Joining Across OTBI Subject Areas
Most subject areas in Oracle Fusion OTBI are self-contained and only support reliable analysis within their own folders; dragging a folder from a second subject area into the same analysis without a genuine shared join key silently produces duplicated or missing rows because OTBI has no way to correctly relate the two fact grains. Fix it by staying inside one subject area where possible, or by explicitly using a subject area that Oracle designed to cross domains, rather than combining arbitrary folders yourself.
Error fixFix The Oracle Fusion "You Don't Have Access To This Data" Error
This generic Oracle Fusion security message means the function privilege and the data security scope did not both line up for that user on that record - most often the job role is assigned but the matching data role, security profile, or business unit and ledger context in Manage Data Access for Users is missing. Fix it by checking data access setup for the user's role, not by re-granting the same job role again.
How-toConnect Oracle Integration Cloud (OIC) To Fusion ERP
OIC connects to Fusion ERP primarily through the prebuilt ERP Cloud Adapter, which wraps Fusion's REST and SOAP web services with OAuth-based authentication and pick-list discovery of available business objects and operations, instead of you hand-building every REST call. Use the adapter for standard integrations; drop to a generic REST or SOAP adapter only when the ERP Cloud Adapter does not yet expose the specific service you need.
Error fixFix FBDI Import Failures From Interface Table Validation Errors
When a Fusion FBDI import job errors out, the cause is almost always bad data in the interface tables (an invalid value set, a wrong date format, or a missing required column), not the ESS job itself. Open the process's Interface Errors Report or the Correct Import Errors spreadsheet to see the exact rejected rows and reason codes, fix the source data, and resubmit from the interface tables instead of re-running the whole FBDI load.
Error fixClear An Oracle Fusion ESS Job Stuck In Blocked Status
A Blocked status on an Oracle Fusion Enterprise Scheduler (ESS) job almost always means an earlier instance of the exact same job is still running or stuck, and the job definition does not allow simultaneous requests. Find and finish, or cancel, the earlier request first; only then does the Blocked request move to Running.
How-toOTBI vs BI Publisher: Which One Should You Use
Use OTBI when a business user needs ad hoc, self-service, real-time analysis with no fixed layout. Use BI Publisher when you need a pixel-perfect, scheduled, high-volume, or externally distributed document such as an invoice, check, or statutory report. Most Fusion implementations end up using both, not one instead of the other.
AI for ERPFusion Cloud ERP AI: OCI Generative AI Service vs. a Private LLM
Oracle's OCI Generative AI Service is a real option for Fusion Cloud ERP, but not the only one. Compare it honestly against a private LLM for sensitive data.
AI for ERPOracle ERP AI Consulting: What a Partner Should Deliver
What to demand from an Oracle ERP AI consulting partner across EBS, JD Edwards, NetSuite, and Fusion Cloud: interface tables, APIs, and buyer questions.
Stuck on Oracle Fusion Cloud ERP?
Talk to engineers who work inside Oracle Fusion Cloud ERP every week, and who build private AI that answers these questions from your own ERP data.