New Features in Oracle Visual Builder Studio
Here's an overview of new features and enhancements added recently to Oracle Visual Builder Studio (VB Studio).
Topics:
- Release 21.04.1 - March/April 2021
- Release 21.04 - February 2021
- Release 21.01 - November 2020
- Release 20.10 - September 2020
- Release 19.4.3 - August 2020
As soon as new and changed features become available, VB Studio instances are upgraded in the data centers where Oracle Cloud services are hosted. You don’t need to request an upgrade to be able to use the new features—they come to you automatically.
Release 21.04.1 - March/April 2021
Area | Feature | Description |
---|---|---|
Visual Applications | Index a business object field | You can now index a business object field to add a non-unique index to the field's database column and improve performance when you search for the field's value via REST requests or Groovy code. See Index a Field. |
Identity/Access Control | Automatic VB Studio access with some Oracle Cloud Applications roles | Some Oracle Cloud Applications roles are now preconfigured to grant VB Studio IDCS roles to users. After a user is assigned a preconfigured role, there's no need to assign a VB Studio IDCS role manually. Oracle Cloud Applications automatically synchronize user updates with IDCS, but it may take up to 12 hours. As soon as the sync is complete, the Oracle Cloud Applications user can access VB Studio. See Set Up VB Studio Users. |
Release 21.04 - February 2021
Some new Visual Builder Studio features can’t be used until you’ve upgraded your Visual Builder Runtime to 21.04. See Features Requiring Visual Builder Runtime 21.04 for more information.
Area | Feature | Description |
---|---|---|
DevOps | Auto-create environment using single instance in a tenancy | Creating a new project is now simpler when your tenancy includes only one Oracle Cloud Applications or Visual Builder instance. Instead of having to select your instance and specify other values, the New Project wizard automatically creates your environment using this instance and populates default values for the Git repository, workspace, and branch. See Create a Project for Application Extensions and Create a Project for Visual Applications. |
![]() |
Trust certificates for your environment | You can now add trust certificates to your environment's Visual Builder instance for external service connections. If your service or endpoint requires a special certificate, you can get it from the service you're trying to connect to and upload it from the Certificates tab on the Environments page. See Manage Trust Certificates in an Environment Definition. |
![]() |
Guidelines for using large files and binaries | Several recommendations are offered to help you understand the choices you need to make when storing large files and binaries in projects. See Best Practices for Storing Large Files and Binaries. |
![]() |
Publish JS packages to NPM registry | You can now manually upload JS packages to a project’s NPM registry from the NPM page, instead of using the command line. See Publish JS Packages to VB Studio's NPM Registry. |
![]() |
More options for default reviewers | In the New Merge Request wizard, users can now avoid populating Reviewers with all default reviewers. They can select default reviewers for protected branches individually, instead of en masse. See step 11 in Create a Merge Request. |
![]() |
Project deletion | More users would delete their projects when they are done with them if they could find the Delete button more easily, not just under Project Administration > Properties. Owners can now also delete projects from the Projects tab on the Organization page. See Delete a Project from the Organization Page. |
![]() |
New look for usage metrics | Usage statistics under Project Administration > Usage Metrics have a new easy-to-read card-based layout. See View Your Project’s Usage Metrics. |
![]() |
Build VMs |
|
![]() |
Webhook build trigger based on directory filter | In addition to build triggers based on branches and tag names, users can now trigger builds in a Jenkins pipeline when changes to files in directories are detected too. See step 10d in Configure a Webhook in VB Studio to Trigger a Jenkins Job on a Git Repository Update. |
![]() |
Other updates |
|
Visual Applications | Service connection and backend enhancements |
|
![]() |
Key usability improvements |
|
![]() |
Extended Git functionality | You now have additional options within a workspace to help you manage your application code branches in a Git repository:
|
![]() |
Declarative support to create custom types from code | It's now much easier to use your own type, such as a type class written in JavaScript or a typescript class, with a variable in VB Studio. Using a new From Code option in the Types editor, you can import your type definition to declaratively plug in any Oracle JET type class or a custom type class and create an instance of that type class, then use it with a new category of variable known as an InstanceFactory variable. See Create a Custom Type From Code. |
![]() |
New UI to manage resource imports | It is now possible for you to add, update, or delete imported resources, such as custom CSS files, modules, and components. You can create references to these imports at the page, flow, and application level using the new Imports tab from the Settings editor. See Import Components, CSS, and Custom Modules for an Application. |
![]() |
Enhanced support for JS functions | It is now easier to call custom functions defined in JavaScript modules and imported module objects. These functions become available for selection in an action chain using the Call Function action and in a component's property (both in the Expression editor and the Variables picker). See Work with the JavaScript Editor. |
![]() |
Code editor improvements | The code editors in the Designer—HTML, JSON, JavaScript, and Code view in the Page Designer—are now based on Monaco, the same editor that provides extensive code-editing capabilities in Visual Studio Code.
The HTML and JSON editors leverage this update as follows:
Note that code insight has changed—you now need to trigger it in an editor by typing Ctrl+Space or by typing a trigger character, such as the dot character (.) in JavaScript. See Work With Code Editors. |
![]() |
Improvements to the Action Chain editor |
When you define an action's properties in an action chain, its default ID is now regenerated to provide a more descriptive identifier. For example, a single Call REST Endpoint action added to a chain has an initial ID of callRest. If you configure the actions endpoint, say, to call the Petstore IDs are regenerated for the following actions: Call Action Chain, Call Function, Call REST, Fire Event, Navigate, and Call Component. |
![]() |
Improvements to the Variables and Types editors |
|
![]() |
Business object relationship | When your business object includes a reference type field, you can now view and edit the relationship directly from the referenced field's properties. |
![]() |
New camera component | You can now use the new camera component when you want your application to access the camera capabilities of the devices on which it is installed. The camera component offers more configuration options than the Take Photo action, and does not require you to add a separate action to trigger taking a photo. See Add Camera Component to a Page. |
Application Extensions | Enhanced support for objects in layouts | You can now add one-to-many sub-object fields and polymorphic objects and their discriminators to layouts in rule sets, and modify the order that the object's fields are rendered in the component. See Create a Layout for a Dynamic Form or Table. |
![]() |
Duplicating base app templates | You can now duplicate templates defined in the base app and use them as the basis for a new template. When you duplicate a template, the event listeners and action chains used in the template are automatically copied to your app extension. Variables referenced in the template are also automatically modified to work in the extension app. |
![]() |
Added listenable vbEnter event
|
You can now create event listeners for the vbEnter lifecycle event in your dynamic component and use them to trigger action chains when the page is opened. See Create Event Listeners for Events.
|
![]() |
Improved support for adding and using resources | It is now easier to create, import and edit resources such as JavaScript, CSS and image files in your extension application:
|
Features Requiring Visual Builder Runtime 21.04
This release of Visual Builder Studio uses Oracle JET 9.2 libraries and components. We recommend that you upgrade your Visual Builder applications to this latest JET version, as well as to the 21.04 Visual Builder Runtime, to take advantage of the full spectrum of 21.04 features. For example, in JET 9.2, new slots (Action, Navigation, and Quarternary) have been added to the List Item Layout component, making it even easier to produce great-looking content for your ListViews. To see everything that's new in JET 9.2, see the Release Notes.
Here are the features that require the 21.04 VB Runtime:
Feature | Description |
---|---|
New dynamic service connections | You can now create a service connection to dynamically retrieve the service's OpenAPI definition, instead of copying the definition and storing it as part of your visual application's sources. A dynamic service connection creates a pointer to the service definition at a remote location. This keeps your application in sync with the latest service definition and enables you to re-use external definitions that aren't customized for your app. See Service Connections: Static Versus Dynamic. |
Declarative support to create custom types from code | It's now much easier to use your own type, such as a type class written in JavaScript or a typescript class, with a variable in VB Studio. Using a new From Code option in the Types editor, you can import your type definition to declaratively plug in any Oracle JET type class or a custom type class and create an instance of that type class, then use it with a new category of variable known as an InstanceFactory variable. See Create a Custom Type From Code. |
You can upgrade to the latest JET and Visual Builder Runtime versions from your visual application's Settings editor. See Manage Runtime Dependencies for Visual Applications.
Release 21.01 - November 2020
Area | Feature | Description |
---|---|---|
DevOps | Oracle Redwood Design Language | The Redwood look and feel that we introduced for the Designer in the last release now extends to VB Studio pages that let you plan and manage your development processes. Redwood is the new Oracle design language standard, which provides a refreshing color palette and a more streamlined user experience. |
![]() |
Built-in free VM | In some OCI regions, VB Studio offers a built-in free VM to run builds. The built-in free VM offers 50 GB (decimal) storage space for build artifacts. You can't increase the storage space. See VB Studio's Built-in Free Account. |
![]() |
Customization set migration | You can now configure jobs and a pipeline to package and deploy an app extension to the Oracle Cloud Application's production sandbox (which was created when you imported CSM data to the production instance). See Create and Configure Jobs to Migrate Your Oracle Cloud Application’s Customizations. |
![]() |
Support for provisioning failures | If a provisioning failure occurs after a Visual Builder or FA service instance is added to an environment, the status icon in the Environments page now reflects one of the following states: failed provisioning, provisioning, or timed out. You can then take steps to retry provisioning. See Manage an Environment. |
![]() |
Personal Access Tokens | You no longer require a personal access token to add an Oracle Cloud Applications instance or a Visual Builder instance to an environment, or to authorize a job to deploy to the instance. All you need are credentials of a user who can access the instance. Information about using personal access tokens with environments was removed from Using Visual Builder Studio and Administering Visual Builder Studio. |
![]() |
Workspace in a new browser tab | You can now open a workspace in a new tab by right-clicking the workspace link on the Project Home page and selecting Open in New Tab. On the Workspaces page, you can get to the same option by right-clicking the workspace link or by using the action menu. Right-clicking a workspace link opens a custom context menu that displays all of the same options as the action menu. This new menu replaces the native browser menu. See What Is a Workspace? and Manage Workspaces. |
![]() |
Document reorganization | Managing Your Development Process with Visual Builder Studio has been restructured to better meet the needs of developers and project owners who aren't working with visual applications or applications that extend Oracle Cloud Applications. The guide is retitled to Using Visual Builder Studio to more clearly differentiate it from the administration guide. |
Visual Applications | Recovery mode | When a visual application fails to upgrade because of syntax errors, the Designer now goes into recovery mode. In this mode, you can use tools such as Code View to fix syntax errors and then upgrade your visual application. See Resolve Issues that Prevent Upgrade of Visual Application. |
![]() |
Sitemap for a web application | You can now add a sitemap to a web application's resources to provide search engines information about your application's pages for intelligent crawling and search indexing. See Add a Sitemap to a Web Application's Resources. |
Application Extensions | Form templates for dynamic forms | You can now create and apply form templates to dynamic form layouts. You can use form layouts to control how fields in a layout are rendered, as well as the fields the layout contains.
The Templates tab now lists the field templates and form templates that can be used in the dynamic UI artifact's layouts, and you can now create field and form templates from the tab. The new form template designer allows you to add components from the Components palette to your form templates. See Control How a Form Layout is Rendered on the Page. |
![]() |
New Help Hint properties for fields | When editing properties for fields, the Property Inspector now contains property fields for Help Hint Definitions and Help Hint URLs. |
![]() |
Column Span property for field groups | When editing the properties for groups in the dynamic UI layout editor, you can now specify the group's Column Span property in the Property Inspector. |
Release 20.10 - September 2020
Area | Feature | Description |
---|---|---|
DevOps | Build VMs |
|
![]() |
Projects |
|
![]() |
Change workspace ownership | Project owners and workspace owners can assign new owners to workspaces they own. See Manage Workspaces. |
![]() |
Visual Builder instance's release version and URL | After adding a Visual Builder instance to an environment, in the Service Instances tab, users can now click Expand to see the Visual Builder instance's release version and URL. See Add a Visual Builder Instance to an Environment. |
![]() |
NPM |
|
![]() |
Vulnerability analysis for Gradle projects | VB Studio adds support for vulnerability analysis for Gradle projects, similar to what has been offered for Maven and Node.js/JavaScript projects before. The documentation has been merged together, now covering all three types of projects. See Generate a Dependency Vulnerability Analysis Report and Resolve Reported Vulnerabilities Automatically |
![]() |
Manage Build Actions | With one mouse click, users can now disable a plugin instead of spending much longer to actually delete it in the job configuration. In addition, users can also quickly and easily remove a job configuration, even if it has been disabled. See Manage Build Actions. |
![]() |
Build parameters and reserved words | Users can quickly look up characters and reserved words that shouldn't be used in parameter names. See Use Build Parameters and Reserved Words that Shouldn't Be Used in Build Parameter Names. |
![]() |
Pipeline instance log | Users can now display the pipeline instance log without leaving the UI. See Manage Pipelines. |
![]() |
Create Git merge requests from the command line | You can now create merge requests and add reviewers from the command line using git push options. Use the mr.target option to create a merge request for publishing changes from your local branch to a remote branch, and include either the mr.add.reviewer option or the mr.add.defaultReviewers option to add reviewers. See Create a Merge Request from the Command Line.
|
![]() |
Trigger a job based on an included or excluded fileset | When you've enabled a job to be triggered either on each SCM commit or according to a polling schedule, it's now much easier to configure the job to run based on an included or excluded fileset. Use the job's Advanced Git Settings to specify a list of files and directories to be polled in the Git repository; only changes to these files determine whether a build is triggered or not. See Include or Exclude Files to Trigger a Build. |
![]() |
Wercker build step | We will remove support for the Wercker build step from VB Studio in a future release. We recommend that you configure pipelines that currently use the Wercker build step to use VB Studio’s pipelines instead. See Design and Use Job Pipelines. |
Visual Applications | Oracle Redwood Design System |
Web apps that you create using this release of VB Studio now use the Redwood theme, a theme created with the Oracle Redwood Design System. Oracle Redwood Design System is the new Oracle standard for application look and feel. The Designer within VB Studio has also adopted a Redwood theme. See Develop Applications. |
![]() |
Manage runtime dependencies | Your applications are no longer automatically upgraded to the new major runtime versions of Visual Builder Runtime and Oracle JET after you instance of VB Studio is upgraded. You decide when to upgrade your applications using the UI that has been introduced for this purpose. See Manage Runtime Dependencies for Visual Applications. |
![]() |
Business object data caching | You can now define a caching strategy to safely store your business object's data and improve performance, by editing the Resource Cache Control setting on a business object's Endpoints tab. Because all application data is deemed sensitive, by default, no data is cached. See Control Data Caching for Business Objects. |
![]() |
Version input field in the visual application's Settings editor | The Settings editor for visual applications now includes a Version input field where you can modify the value for the version property in the visual-application.json file. See Set Version Information for Your Application.
|
![]() |
Audits |
|
![]() |
Horizontal text tabs for artifacts in the Designer | The artifact section tabs for page flows, event listeners, and so on now appear as horizontal text tabs above the artifact instead of as a vertical icon bar. See Understand the Designer. |
![]() |
Status icons in the Designer’s Navigator and Git Panel | A series of status icons have been introduced to provide a visual indicator of the status of an application’s file. These icons indicate if a file has yet to be committed to the workspace’s current branch, contains modifications that have yet to be committed, or conflicts with changes from other team members. The Git Panel also includes a new Options menu that provides access to a subset of the Git commands available from the Designer toolbar. See Manage Your Visual Applications With Git. |
![]() |
Create variables | You can now create variables from within the Assign Variables dialog that you open from the Action Chains editor. See Add an Assign Variables Action. |
![]() |
Mobile applications |
|
![]() |
Action chain tests |
The |
![]() |
Upgrade the Oracle Sample R13 SaaS LightBlue Theme | If your application uses the Oracle SaaS R13 Light Theme, you need to upgrade the theme in your application before you run the application using this release. See Update Your Oracle SaaS Application Template Theme. |
Application Extensions | Redesigned workspace creation |
The "Designer" item in the main menu has been renamed "Workspaces". The process for creating workspaces for an app extension has been simplified. |
![]() |
Redesigned dynamic UI artifact pages |
The dynamic UI artifact page has been restructured to improve usability for navigating to rule sets, fields, templates and editor tabs for working with the layout model. |
![]() |
Support for layout programming model |
Support has been added for events, variables, types, action chains, and JavaScript within dynamic component templates. Dynamic layouts now expose additional components to their programming model. Each dynamic template can bind to events, action chains, variables and functions defined within its layout model. Editors for working with the layout model have been added as tabs to the dynamic UI and page artifact pages. A variables picker and Events tab have been added to the Property Inspector for components in dynamic templates In dynamic layout templates, you can now trigger an action chain defined within its layout model. Within the layout's action chain, a "FireCustomEvent" action can now fire a custom event with the new "dynamicComponent" behavior type that you use within the context of a dynamic layout. |
![]() |
Improved dynamic UI rule set editor |
The following improvements have been made to the dynamic UI rule set editor:
|
![]() |
Create custom fields for dynamic layouts | A Fields tab has been added to the dynamic UI artifact page, with an editor for creating custom fields by editing the artifact's metadata. You can now also modify the fields used in the dynamic layout on the client-side by augmenting or replacing the metadata. See Create a Custom Field in Your Dynamic Form or Table. |
![]() |
Dynamic form field templates |
A Templates tab with a template designer has been added to the dynamic UI artifact page. You can now create your own field templates for customizing how fields in dynamic forms are rendered, and apply your field templates to form fields in dynamic layouts. The template designer supports nearly all of the Page Designer features, including the Components palette, Structure View, canvas and Property Inspector. The Templates designer supports working with the layout programming model, including support for events, variables, and action chains within templates. See Control How a Field is Rendered on the Page. |
![]() |
Improved Page Designer |
The Page Designer is now a tab in the page artifact page. The Property Inspector now provides improved support for working with extendable constants, variables and dynamic containers. |
![]() |
Support for dynamic containers |
Dynamic container components are now supported in pages:
|
![]() |
Expanded support for constants | The default value of constants can now refer to expressions that contain variables. |
Release 19.4.3 - August 2020
Area | Feature | Description |
---|---|---|
DevOps | Configure authorization credentials for the build job | The Publish Changes dialog now notifies you if you need to configure authorization credentials for the build job associated with the merge action of your master branch. It also provides a link to navigate to the build job. See Deploy a Visual Application. |
Visual Applications | Backend service catalog for Oracle Integration Cloud | If the Visual Builder instance that you use in your environment is provided by Oracle Integration, visual applications in VB Studio now inherit the catalog of Integration and Process backend services ready-to-use, without the need for you to manually enter instance URLs in the visual application's Settings editor. You can use the Settings editor to override settings for the inherited catalog. See Manage Backend Services in Your Visual Application. |
![]() |
Corrupted business object resource files | Business object resource files that may have been corrupted due to, for example, invalid syntax can now be restored to a valid state by opening a source editor to edit the JSON. See View a Business Object's Endpoints. |
New Features in Oracle Visual Builder Add-in for Excel
The Oracle Visual Builder Add-in for Excel version bundled in VB Studio 21.04 is 2.4. For details of what's included in this release, see New and Changed Features.
Supported Browsers
VB Studio supports most modern HTML5–compliant browsers.
VB Studio complies with the Oracle Software Web Browser Support Policy and supports the latest version of the browser available, and in the case of IE and Safari, one previous major release. Oracle support is available for all platforms that the browser vendor supports. For mobile device operating systems, Oracle provides support only for the most recent browser delivered by the device operating system.
The following table describes the platforms supported by the Visual Builder runtime:
Operating System | Chrome | Firefox | Microsoft Browser | Safari |
---|---|---|---|---|
Android |
Supported* |
Not Supported |
N/A |
N/A |
iOS |
Not Supported |
Not Supported |
N/A |
Supported |
Mac OS X |
Supported |
Supported |
N/A |
Supported |
Windows |
Supported |
Supported |
Supported |
Not Supported |
* Chrome for Android only, not native Android browser
JavaScript must be enabled for all browsers.
Note:
The Visual Builder Studio Designer is supported by the Chrome browser running on Mac OS X and Windows. Other browsers and platforms are not supported.Note:
Visual Builder runtime has deprecated the use of Internet Explorer 11. Users who try to access a deployed Visual Builder application from Internet Explorer will now see a deprecation warning. In addition, Oracle Support will no longer address issues pertaining to Internet Explorer 11.Deprecated Features
Take note of features that have been deprecated and are no longer supported in VB Studio:
Area | Feature | Description | Release |
---|---|---|---|
DevOps | Oracle ACCS deployment |
VB Studio no longer supports deployment to Oracle Application Container Cloud Service (ACCS). An ACCS service instance can't be added to an environment and ACCS deployment can no longer be configured from the Oracle Deployment build step. |
21.04 - February 2021 |
![]() |
OSN webhook |
VB Studio dropped webhook support for Oracle Social Network (OSN), after the service was decommissioned. |
21.04 - February 2021 |
Visual Applications | Internet Explorer 11 |
Visual Builder runtime has deprecated the use of Internet Explorer 11. Users who try to access a deployed Visual Builder application from Internet Explorer will now see a deprecation warning. |
19.4.3 - August 2020 |
Oracle Support will no longer address issues pertaining to Internet Explorer 11. |
21.04 - February 2021 |
Upgrade Policy
We strongly suggest that you upgrade and republish your apps from time to time, not only to take advantage of the new features, bug fixes, and performance enhancements that come with each new release, but also to reduce the risk of possible incompatibilities between the Visual Builder Runtime and JET libraries you built your app with in the Designer, and the Visual Builder instance to which you deployed your app in Oracle Cloud. What does this mean? Suppose you built and deployed your app using Visual Builder 18.4.1. Since then, Visual Builder has upgraded its target deployment environment several times—from 18.4.1 to 18.4.5 to 19.1.3 and so on—and your app has continued to run on those instances with no issues. However, when the 19.4.3 instance becomes available (for example), your app suddenly stumbles on an incompatibility between your 18.4.1 runtime dependencies and your 19.4.3 deployment environment—simply too much has changed between the time you built the app and the capabilities in the latest target deployment instance. To avoid this, it’s a good idea to upgrade and re-publish your apps as frequently as your schedule allows. This entails opening your app in the Designer to uptake a new Runtime Version/JET library (and, optionally, taking advantage of some of the latest features), testing it with the latest Visual Builder deployment target, then republishing your app to that instance.
Getting Oriented
VB Studio brings you all the functionality previously available with Oracle Developer Cloud Service. You also get the ability to build web and mobile applications in the Visual Builder Designer, as well as to extend certain Oracle Cloud Applications to customize the UI for your business needs.
VB Studio offers end-to-end functionality for your development team, from planning releases and managing development backlog, to hosting source code in Git, to designing, building, testing, and deploying cloud-native applications to your Oracle Cloud Applications and Oracle Cloud instances.
For Former Developer Cloud Service Users
If you were a Developer Cloud Service user, the following table will help you understand the primary differences between Developer Cloud Service and VB Studio:
How Developer Cloud Service and VB Studio Differ? | Find out more: |
---|---|
You don’t need to migrate your Developer Cloud Service projects. A VB Studio instance replaces your Developer Cloud Service instance, and you can continue to use your existing projects and corresponding DevCS features just as they are, without any impact to you. | Using Oracle Developer Cloud Service has been restructured and rewritten for VB Studio and is now called Managing Your Development Process with Visual Builder Studio. If you’re an administrator, you’ll want to check out Administering Visual Builder Studio as well. |
VB Studio comes equipped with the Designer, a graphical user interface that enables you to develop web and mobile apps using components from the Oracle JavaScript Extension Toolkit (JET). To test these applications, or to release them for production, you must deploy the apps to a separate Visual Builder instance, which serves as the runtime environment.
Of course, you can still use VB Studio to build apps with a third-party IDE or code editor and use VB Studio as the code repository, just as you did with DevCS. You can also use VB Studio to test, deploy, and maintain those apps throughout their lifecycles—nothing’s changed there. |
Building Web and Mobile Applications explains how to use the VB Studio Designer to build web and mobile apps. |
If you purchased Oracle Cloud Applications subscriptions that have front ends built with JET components, you can also use the VB Studio Designer to extend those apps to customize them for your business needs. | See Extending Oracle Cloud Applications. |
Developer Cloud Service used tags to associate service instances with environments. In VB Studio, you’ll need to add service instances again to environments, because the service instances associated with the environments were removed as part of the upgrade. The environments themselves were not removed, just the service instances associated with them. |
For information about how to add a service instance to an environment, see Manage an Environment. |
For Former Visual Builder Users
In VB Studio, you still use the Designer to create your visual applications, but the infrastructure surrounding that process has changed significantly, as described here:
How Visual Builder and VB Studio Differ? | Find out more: |
---|---|
In VB Studio, you and your team belong to an organization. Within that organization are projects, which help to organize the work for a given endeavor. A project contains a Git repository, where your source code is stored, along with build jobs that package up your app’s artifacts and deploy them to the target environment. Each project also contains tools to help you manage your visual application’s lifecycle, like an Agile board, issue tracker, team wikis, and more. | What Is Oracle Visual Builder Studio? |
Whereas Visual Builder used to contain the runtime environment where you could test and deploy your visual applications, VB Studio requires you to have a separate Visual Builder instance to serve as your runtime environment, and to establish communication between the two services.
VB Studio manages the runtime environment instances that serve as your development, test, and production environments in the Environments page. Within the Environments page, you can view the status of the various service instances that have been added to your environment. |
If you’re an administrator, see Set Up VB Studio for Developing Visual Applications to find out how to hook up your runtime to VB Studio. If you’re an app developer, see Share, Publish, and Deploy Visual Applications. |
Your work in the Designer now takes place in a workspace, which is an entirely private area within a project that only you can access. The workspace brings together everything you need to build your visual app: a private branch within the Git repository and a VB Studio environment that points to your Visual Builder runtime instance. | If you’re an app developer, see Create Visual Applications in VB Studio. |
If you want others to collaborate with you in developing your project's apps, your project owner will need to add them to the project and you’ll need to commit your workspace to a branch in a Git repository that is shared with these project members.
To facilitate collaboration, the Designer in VB Studio includes built-in support for Git with a Git menu in the toolbar that accesses the Git commands you’re likely to use most frequently (Pull and Push, for example). There's also a new navigator tab (Git Panel) that provides a view to uncommitted changes in your workspace, and tools to resolve issues when your changes conflict with other changes in the Git repository branch that you want to commit to. |
If you're a project owner, see Add and Manage Project Users. If you're an app developer, see Manage Your Visual Applications With Git. |
In Visual Builder, the Stage and Publish actions were key parts of your development cycle. In VB Studio, however, you use Share to share your application with others for testing purposes, and Publish to push your changes from your local Git repository to the master branch of your remote repository (that is, the project's version) and deploy it to the Visual Builder runtime environment. |
If you’re an app developer, see Share a Visual Application and Manage Deployed Visual Applications. |
For business objects, VB Studio maintains one database schema per workspace. As a best practice, we recommend that you use the same workspace and branch to create and edit business objects in a visual application. | See Work with Business Objects. |
VB Studio provides the following options to manage your visual application’s business object data:
|
See Manage Business Object Data During Development. |
You can use the visual applications you built in Visual Builder within VB Studio by importing them, then performing a few post-import tasks. | See Learn About Migrating to Oracle Visual Builder Studio. |
VB Studio manages connections to backend services differently to Visual Builder, where a Visual Builder administrator added these services to the Tenant Settings page.
In VB Studio, the steps to create a connection depend on the backend service. If your visual applications need to access REST services from an Oracle Cloud Applications catalog, you add the Oracle Cloud Applications instance to the runtime environment. If the Visual Builder instance that you use in your environment is provided by Oracle Integration, visual applications in VB Studio inherit the catalog of Integration and Process backend services. |
See Manage Backend Services in Your Visual Application. |
The grunt-vb-build NPM package includes tasks to build visual applications that you develop in VB Studio and deploy to a Visual Builder runtime instance:
|
If you want to use the Grunt tasks described here to build and deploy a visual application to a Visual Builder runtime instance, see Build and Deploy Your Application. |
Although you’ll now do almost all the administration tasks for your visual applications in VB Studio, someone with administrator privileges for the Visual Builder runtime needs to sign in to the Visual Builder runtime to do certain tasks. Examples include configuration changes to connect your Visual Builder runtime to an Oracle DB instance with more space, or to configure a custom domain if users access an application deployed on the Visual Builder runtime from a custom app URL. | If you’re a Visual Builder runtime administrator, sign in to the Visual Builder runtime to complete the following tasks, that are described in Administering Oracle Visual
Builder.
|
Extending Oracle Cloud Applications
If Oracle built your Oracle Cloud Application using Oracle JET, you can extend that app to customize it for your business needs.
To find out if you have such an app, see if you have an Edit Pages in Visual Builder option in your Oracle Cloud Application’s edit menu. If you do, click it to jump over to VB Studio and start creating your application extension. To help you along the way, have a look at How Can Visual Builder Studio Help Me Extend My Oracle Cloud Application?
Like everything built in VB Studio, the source code for your application extension is stored within a project’s Git repository, and you work on your own branch of that repo in the context of your own private workspace.
Documentation Accessibility
For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc.
Access to Oracle Support
Oracle customers that have purchased support have access to electronic support through My Oracle Support. For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.
Oracle Cloud What's New in Oracle Visual Builder Studio
F35436-06
April 2021
Copyright © 2020, 2021, Oracle and/or its affiliates.
Primary Author: Oracle Corporation
This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.
The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.
If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable:
U.S. GOVERNMENT END USERS: Oracle programs (including any operating system, integrated software, any programs embedded, installed or activated on delivered hardware, and modifications of such programs) and Oracle computer documentation or other Oracle data delivered to or accessed by U.S. Government end users are "commercial computer software" or "commercial computer software documentation" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, the use, reproduction, duplication, release, display, disclosure, modification, preparation of derivative works, and/or adaptation of i) Oracle programs (including any operating system, integrated software, any programs embedded, installed or activated on delivered hardware, and modifications of such programs), ii) Oracle computer documentation and/or iii) other Oracle data, is subject to the rights and limitations specified in the license contained in the applicable contract. The terms governing the U.S. Government’s use of Oracle cloud services are defined by the applicable contract for such services. No other rights are granted to the U.S. Government.
This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.
Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.
Intel and Intel Inside are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Epyc, and the AMD logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.
This software or hardware and documentation may provide access to or information about content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services unless otherwise set forth in an applicable agreement between you and Oracle. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services, except as set forth in an applicable agreement between you and Oracle.