SR No  

Features

VB/VBCS (Standalone/OIC)

VBS(Embedded/Standalone)

Remarks

      1.

DB/Data Access

• It comes with Built-In DB(5GB) and can be connected to Oracle DBaaS(using ORDS) or ATP (Autonomous Transaction Processing) DB.
• Access data from
     *External secured REST services.
     *External database.
• Create your own DB and Bos.
• We get the Built-in DB, Business Objects and REST proxy in the VB standalone instance.

• It would be connected to Oracle Fusion cloud DB.  
• External data Access: No Built-In solution but there are some alternate solutions to access the external authenticated DB/Data.

Alt. Solutions : a)  App Composer=> Groovy Function=>Call Ext authenticated Rest Endpoint.   (Shared blog link below) b)  By using cloud native components such as OCI API Gateway,oracle cloud functions..etc.    (Blog: WIP )

• VBS can access external data but it needs to be unauthenticated
• You can’t create your DB and connect/create only FA DB (Custom objects in apps composer) and related Bos.
• VB app will get deployed to FA instance and therefore we don’t get the DB, Business Objects and REST proxy .

      2.

Organize the work

• No Built-in  Git Repository and CI/CD (build Jobs) .
• Visual application’s lifecycle (Agile board, issue tracker, team wikis,sprint managment..etc ) is not supported.

• Each Project has Git Repository and CI/CD (Build Jobs)  are integrated tightly and supported (Implicit).
• Project has tools to help/manage your visual application’s lifecycle ( Agile board, issue tracker, team wikis,sprint management..etc) .
• It has utilities that help manage infrastructure as code leveraging standards such as Docker, Kubernetes, and Terraform.

      3.

Visual Builder Business Object

We can use VB BO.

No, use FA custom objects

VB(B2B-CX) : No, use FA custom objects.

      4.

Federation

Stand alone VB is not pre-federated with FA.

Visual Studio and FA  pre-federated, with FA being the IdP

VB(B2B-CX) :VB and FA shares same IDCS

      5.

Integration

Applications built can be integrated with Fusion Applications using Page Integration/Composer through Sandbox.

VB App extensions can be deployed as “APP UIs” which are then deployed as part of fusion apps.

Note: Fragment (new feature) : Reusable component used across App Uis.

VB(B2B-CX) :Same as VBS.

      6.

Design Time (DT) and Runtime (RT) Servers/Instance

It has both DT and RT Server/Instance of VB.

The VB Studio you get with FA is just the design time, it doesn’t have the runtime server of VB.

Note: If you develop a standalone Visual Application with VBS the VB engine for preview is provided by VBS but you can’t deploy using build pipeline since it does not have VB instance runtime by default and need to be added as an env to VBS.

VB(B2B-CX) : Has it's own runtime.

      7.

REST Endpoints/REST API Access

We need to add fusion application backend manually.

it is tightly integrated with Fusion Applications .

      8.

App Outside FA

We can develop application outside the fusion application.

No. Within FA.

Supported in VB(B2B-CX) : No. Within FA.

     9.

Vanity URL and Apps with Custom Domains

Yes

Notes:

1)Mobile and PWA apps are not supported at this time. Custom domains(different URL than the one generated by Visual Builder) can only be used for web apps.

2) After you've configured the vanity URL, it's important you work with the visual app using its custom domain.

3)Working with a vanity app from a non-vanity host can cause issues so make sure you access the designer using custom domain.

No

(Vanity URL :use FA URL)

Supported in VB(B2B-CX)

   10.

Customized look and feel     

We can build apps with custom look and feel.

No, Restricted to FA Look and Feel.

Supported in VB(B2B-CX)

   11.

Run independently of FA

Yes

No

Supported in VB(B2B-CX) : Yes

   12.

Invoke External Rest APIs 

Possible to invoke/access external APIs through Rest proxy service.

Possible to invoke/access only APIs with no authentication

Supported in VB(B2B-CX) : Yes

Resources

Remarks

Scenario/Use case

Guidelines

VB(VBCS)

VBS

• Need access to Data in a standalone DB.
• Need to scale the VB middle tier*.
• Want a custom look and feel.
• Want full control and fully featured.
• Standalone or custom Mobile App in addition to a Fusion Extension.

(Additional cost for the runtime instance )

• Need access to authenticated non-FA resources.

     E.g. ORDS, SAP etc

• Need Custom and Vanity URLs support.

Note: Working with a vanity app from a non-vanity host can cause issues.

• Users not FA users.

• Recommended for SaaS Extensions.
• Extending existing FA VB User Interfaces.
• In case of accessing FA Resources.
• Restricting to FA look and Feel .
• Don’t want to purchase a VB License.
• Need integrated/collaborative project management with DevOps operations.
• Looking for simple inbuilt Identity federation     (VBS-Embedded).

          (IDP and SP are sharing the same IDCS)