Oracle Visual Builder Guide

Share

Introduction

Oracle Integration Cloud Visual Builder is a powerful low-code development platform within Oracle Cloud that enables consultants and developers to build responsive web and mobile applications rapidly. In modern Oracle Fusion Cloud implementations (26A), organizations are increasingly demanding custom UI extensions, lightweight applications, and seamless integration with backend services like HCM, ERP, and SCM.

From a consulting perspective, Visual Builder (VB) becomes critical when standard Oracle Fusion UI does not meet specific business needs. Instead of heavy customizations, we design extensions using Visual Builder that integrate with Oracle Integration Cloud (OIC Gen 3) and REST services.

In this article, we will explore Oracle Integration Cloud Visual Builder in a practical, implementation-focused way, exactly how it is used in real projects.

What is Oracle Integration Cloud Visual Builder?

Oracle Integration Cloud Visual Builder (VB) is a low-code/no-code application development platform used to create:

  • Web applications (browser-based)

  • Mobile applications

  • Oracle Fusion extensions

  • Process-driven applications

It provides:

  • Drag-and-drop UI design

  • Built-in REST API integration

  • JavaScript-based logic (for advanced use cases)

  • Integration with OIC Gen 3 services

  • Prebuilt templates and business objects

👉 Think of Visual Builder as the UI layer sitting on top of OIC integrations and Oracle Fusion APIs.

Key Features of Oracle Integration Cloud Visual Builder

1. Low-Code Development

Business users and consultants can design applications without heavy coding.

2. Built-in REST Integration

Directly connect to:

  • Oracle Fusion REST APIs

  • OIC integrations

  • External APIs

3. UI Component Library

Prebuilt components:

  • Tables

  • Forms

  • Charts

  • Layouts

4. Business Objects

Internal data storage with:

  • CRUD operations

  • REST exposure

5. Role-Based Security

Integration with Oracle Identity Cloud Service (IDCS)

6. Git-Based Version Control

Supports branching, merging, and deployments.

7. Mobile Responsive Design

Apps automatically adapt to mobile screens.

Real-World Integration Use Cases

Use Case 1: Employee Self-Service Extension (HCM)

A client wanted employees to:

  • Submit travel requests

  • Upload documents

  • Track approval status

Solution:

  • UI built in Visual Builder

  • Integration created in OIC Gen 3

  • Data pushed to Fusion HCM via REST APIs

Use Case 2: Vendor Onboarding Portal (ERP)

Procurement team needed:

  • Vendor registration portal

  • Document upload

  • Approval workflow

Solution:

  • Visual Builder app for vendors

  • OIC integration to validate and create supplier in Fusion ERP

Use Case 3: Inventory Dashboard (SCM)

Warehouse managers needed:

  • Real-time stock visibility

  • Alerts for low inventory

Solution:

  • Visual Builder dashboard

  • OIC pulls data from SCM Cloud

  • Charts displayed using VB components

Architecture / Technical Flow

Typical architecture in real implementations:

  1. User interacts with Visual Builder UI

  2. UI calls REST endpoints

  3. REST endpoints are:

    • Oracle Fusion APIs OR

    • OIC Gen 3 integrations

  4. OIC handles:

    • Business logic

    • Data transformation

    • Error handling

  5. Response is returned to Visual Builder UI

Flow Summary:

Visual Builder → REST Service → OIC Gen 3 → Fusion Cloud → Response → UI

Prerequisites

Before starting with Visual Builder:

1. Oracle Cloud Environment

  • Oracle Integration Cloud (Gen 3)

  • Visual Builder enabled instance

2. Access Requirements

  • Developer role in Visual Builder

  • Access to Fusion REST APIs

  • IDCS user setup

3. Integration Readiness

  • OIC integrations deployed

  • REST endpoints available

4. Basic Knowledge

  • REST APIs

  • JSON payloads

  • UI design basics

Step-by-Step Build Process

Let’s walk through a real implementation scenario:

Scenario: Build Employee Request Application

Step 1 – Access Visual Builder

Navigation:

Navigator → Visual Builder (via Oracle Cloud Console)

  • Login to Oracle Cloud

  • Open Visual Builder Studio

Step 2 – Create New Application

Click:

  • Create → Web Application

Enter:

  • Application Name: EmployeeRequestApp

  • Template: Starter Application

Step 3 – Design UI Page

Create a page:

  • Add components:

    • Input fields:

      • Employee Name

      • Request Type

      • Amount

    • Button: Submit

Use:

  • Form Layout

  • Input Text

  • Dropdown

  • Button component

Step 4 – Create Service Connection

Navigate:

Service Connections → Create

Enter:

  • Service Type: REST

  • Endpoint: OIC Integration URL

Example:

https://<oic-instance>/ic/api/integration/v1/flows/rest/submitRequest/1.0/

Authentication:

  • Basic Auth or OAuth

Step 5 – Bind UI to Service

  • Select Submit Button

  • Add Action Chain

Steps:

  1. Collect form data

  2. Call REST service

  3. Handle response

Example payload:

{ “employeeName”: “John”, “requestType”: “Travel”, “amount”: 5000 }

Step 6 – Add Business Logic

In Action Chain:

  • Validate inputs

  • Call REST API

  • Show success message

Example:

  • If amount > 10000 → Show warning

Step 7 – Deploy Application

Click:

  • Publish → Stage/Production

Application URL will be generated.

Testing the Technical Component

Test Scenario

User submits a request via UI.

Expected Flow

  1. UI sends request

  2. OIC receives payload

  3. OIC processes and calls Fusion API

  4. Response returned

Validation Checks

  • Data saved in Fusion HCM/ERP

  • Success message displayed

  • No API errors

Sample Test Payload

{ “employeeName”: “Ravi”, “requestType”: “Expense”, “amount”: 3000 }

Common Errors and Troubleshooting

1. Authentication Failure

Issue: 401 Unauthorized

Solution:

  • Check credentials

  • Verify OAuth configuration

2. CORS Issues

Issue: Browser blocks API call

Solution:

  • Enable CORS in OIC

  • Use proxy configuration

3. Incorrect Payload Structure

Issue: API fails

Solution:

  • Validate JSON format

  • Match API schema

4. Deployment Failures

Issue: App not accessible

Solution:

  • Check environment (Stage/Prod)

  • Verify roles and permissions

Best Practices

1. Use OIC as Middleware

Avoid calling Fusion APIs directly from UI.

2. Keep UI Lightweight

Handle business logic in OIC, not in Visual Builder.

3. Reusable Service Connections

Design generic APIs for reuse.

4. Follow Naming Standards

Example:

  • empRequestService

  • submitRequestAction

5. Implement Error Handling

Always:

  • Capture API errors

  • Display user-friendly messages

6. Use Version Control (Git)

Maintain versions for:

  • Development

  • Testing

  • Production

7. Optimize Performance

  • Avoid multiple API calls

  • Use pagination for large data

Real Consultant Tips

  • Always design API-first architecture

  • Don’t overload Visual Builder with logic

  • Use OIC for orchestration and transformations

  • Test APIs separately before UI integration

  • Maintain separate environments (DEV, TEST, PROD)

Frequently Asked Questions (FAQs)

1. Is Visual Builder a replacement for OIC?

No. Visual Builder is for UI development, while OIC handles integrations and backend processing.

2. Can Visual Builder directly connect to Fusion APIs?

Yes, but in real implementations, we use OIC as middleware for better control and security.

3. Is coding required in Visual Builder?

Basic apps can be built without coding, but advanced use cases require JavaScript.

Summary

Oracle Integration Cloud Visual Builder is a key component in modern Oracle Cloud architecture, enabling rapid development of custom applications and UI extensions.

From a real-world implementation standpoint:

  • Visual Builder handles UI

  • OIC Gen 3 handles integration and logic

  • Fusion Cloud handles data and transactions

By combining these three layers, organizations can build scalable, secure, and flexible solutions without heavy customizations.

If you are working on Oracle Fusion projects, mastering Visual Builder will significantly improve your ability to deliver end-to-end solutions.

For more detailed reference, you can explore Oracle documentation:

https://docs.oracle.com/en/cloud/saas/index.html


Share

Leave a Reply

Your email address will not be published. Required fields are marked *