Embedding Redwood Apps into Oracle Fusion: A Step-by-Step Guide

So you’ve built your first Redwood-style app using Oracle Visual Builder (VBCS) — maybe a supplier lookup, approval dashboard, or even a smart HCM extension.

Now comes the exciting part: embedding that Redwood app into the actual Oracle Fusion interface — where users can interact with it seamlessly, just like they do with native Fusion pages.

Let’s walk through how to do this, step by step.

Why Embed a Redwood App in Fusion?

Embedding Redwood apps lets you:

• Deliver custom functionality without navigating away from Fusion

• Enhance standard flows with client-specific logic or UI

• Maintain a consistent Redwood user experience

• Eliminate the need for users to jump to external portals

Use cases include:

• Extended supplier onboarding

• Custom discount calculators in Order Management

• Visual dashboards for HR requests

• Quick creation flows for assets or projects

Step-by-Step: Embedding a VBCS Redwood App into Fusion

Step 1: Build and Test Your Redwood App in VBCS

Ensure the following:

• You’ve used a Redwood Web App template in VBCS

• Your app is responsive and mobile-friendly

• It connects to required REST APIs (Fusion, OIC, or others)

• All roles, data visibility, and validations are in place

Pro tip: Secure the app using Fusion’s SSO or OAuth 2.0

Step 2: Create a Sandbox in Oracle Fusion Apps

• Go to Configuration > Sandboxes

• Create a new sandbox and enable Page Composer

• Activate the sandbox

This allows you to make safe UI changes to Fusion apps without affecting production users.

Step 3: Identify the Target Page

Decide where your app should appear. Common examples:

• Supplier landing page

• Custom tab in Employee Info

• Sidebar on Journal Entry dashboard

Open the chosen page in Page Composer.

Step 4: Add the Redwood App via IFrame or HTML Component

In Page Composer:

• Click to add a component and select HTML or IFrame

• Paste your Redwood app’s deployment URL from VBCS

Example code:

<iframe src="https://vb-hostname.oraclecloud.com/your-app-path"
        width="100%" height="600px" style="border:none;">
</iframe>

Ensure proper visibility settings so the correct user roles can access the app.

Step 5: Save, Publish, and Test

• Save changes in Page Composer

• Publish your sandbox

• Test as an end user:

  • Does the app load correctly?

  • Is it consistent with Fusion’s session and security model?

  • Does it look and behave like a Redwood experience?

Things to Watch Out For

• Authentication: Use OAuth with implicit or authorization code flow

• Responsive Design: Test on different screen sizes

• Performance: Use lazy loading where needed to keep things fast

• Data Security: Align with Fusion role-based access and permissions

Optional Enhancements

• Add custom icons or Redwood buttons next to the embedded frame

• Pass Fusion context to the app (e.g., Employee ID) via parameters or session

• Add a loading indicator while the embedded app initializes

Conclusion

The Redwood experience isn’t limited to Oracle’s own apps. You can bring your own creativity into Fusion — cleanly, securely, and natively. With just a few steps, your custom-built Redwood app can feel like it’s part of Oracle’s core ✔