Updated Oracle Visual Builder Studio

Here are some key things you can now do to extend your application pages using Visual Builder Studio:

  • Option to bypass CI/CD pipelines for deployment

You now have the option to deploy your extension directly to your development environment without using CI/CD pipelines. CI/CD pipelines provide advanced functionality, for example, you can use CI/CD pipelines to deploy dependent artifacts to the target environment in parallel or delete extensions to clean up the environment. If you don't need this functionality, you can opt to disable pipelines to deploy your extension. For more information, see Enable or Disable the CI/CD Pipeline for Publishing.

  • Option to isolate extension workspace or repository by pillar

    You can now isolate extensions by product family (pillar) into separate workspaces and repositories when you use the Edit Page in Visual Builder Studio option to customize Oracle Fusion Cloud Applications. For example, you can use one workspace or repository to edit HCM pages and another workspace or repository to edit CX pages. You can still edit all your pages in the same workspace or repository if that's what you want.

    With this update, the default workspace name generated when you switch to VB Studio typically uses the pillar of the page you're trying to extend. For example, Workspace HCM. For more information, see Configure an Oracle Cloud Application.

  • Dependencies grouped by pillar

Dependencies are now grouped by pillar in the Dependencies pane, making it much easier to find the one you want to add to your App UI. For more information, see Add a Dependency.

  • Core pack replacement for legacy components

When your extension uses the default Redwood theme, several core pack components now replace their legacy versions. For example, oj-c-input-text has replaced oj-input-text. While this change doesn't impact an existing extension, when you drag and drop one of these components afresh from the Components palette, you use the Core Pack version on your extension pages. For more information, see Work With JET Core Pack Components.

NOTE: This feature requires Oracle Fusion Cloud Applications 24C or later (with JET 16.x).

  • Support for selecting field values from list of values (LOV)

The condition builder now supports selecting values by name from a list for fields controlled by an LOV. For extensions in advanced mode, see Set Conditions for an Extension Rule. For express mode, see Set Conditions for an Extension Rule.

  • Improved support for standard functions and actions in Advanced Expression editor

The list of functions in the Actions palette now includes standard functions provided by Oracle developers. You can drag the functions from the palette into the expression and configure them in the Properties pane.

The Advanced Expression editor now provides better support for defining actions for creating expressions. Creating conditions using the If action has been improved, so you can now select criteria, operators, and values using drop-down lists in the Properties pane of expression builder. For extensions in Advanced mode, see Build Advanced Expressions. For Express mode, see Build Advanced Expressions.

  • Automatic saving of changes to the condition builder

When you change business rules and validations in the condition builder, your changes are now saved automatically.

  • Support for $objectContext parameters

The condition builder for business rules and validation messages now supports parameters defined in the $objectContext parameters.  These parameters can also be used when creating conditions in the Advanced Expression editor and in expressions to set the default values in business rules. In Advanced mode, you can view the list of the Object Context parameters and their definitions in the Context tab. For more information, see Use Context Parameters in Extensions.

  • Default value in business rules support LOVs

The business rules editor now supports setting a default value for fields controlled by a LOV by selecting a name in a list of values. For extensions in Advanced mode, see Set a Default Value for a Field. In Express mode, see Set a Default Value for a Field.

  • Support to create sections in containers

Support for containers has been improved in the Express mode. You can now create sections in the container's rules editor. You can also edit the name, description, and input parameters of new sections in the Properties pane. For more information, see Control the Sections Displayed on the Page.

  • Page title in Properties pane

The Properties pane in Express mode now displays the page title.

  • Enhanced variable and type creation

We've optimized the process of creating multiple variables and types, so each variable or type is generated with a default name. You can then use the Properties pane to update the name and other properties as needed. For visual applications, see Create Variables and Create Types. For extensions, see Create Variables and Create Types.

With this update, the ability to create a custom type that defines a list of enumeration values is deprecated. For more information, see Deprecated Features.

  • Autoselection of a single environment during workspace creation

When your project has only one environment, it's now automatically selected for you when creating a Visual Application or Application Extension workspace. For visual applications, see Create a Workspace. For extensions, see Create an Extension.

  • New dirtyDataStatus property in vbBeforeExit payload

If you track changes in a variable's state to detect unsaved changes, you can now use the vbBeforeExit event listener's dirtyDataStatus payload (instead of the Get Dirty Data Status action) to check whether navigating away from a page will result in the tracked variable losing its data. For visual applications, see Add a Get Dirty Data Status Action. For extensions, see Add a Get Dirty Data Status Action.

  • Duplicate option in JavaScript action chains

You can now duplicate an action, or a code block within an If, Switch, or Run in Parallel action. For visual applications, see Create Action Chains in Design Mode as well as Add an If Action, Add a Switch Action, and Add a Run In Parallel Action. For extensions, see Create Action Chains in Design Mode, Add an If Action, Add a Switch Action, and Add a Run In Parallel Action.

  • New Select Variable icon in the Properties pane

The Select Variable icon in the Properties pane has been changed to better represent the variable picker. You can now click (x) to select a variable.

  • Listener shortcut on the Events editor

You can now use a shortcut to create a listener when you're working with custom events in the Events editor, instead of switching to the Events Listener editor. Simply select the new Create Event Listener option from the right-click menu of an event to create a new event listener in the same scope as the event. For visual applications, see Create Event Listeners for Events. For extensions, see Create Event Listeners for Events.

The new Visual Builder Studio functionality provides you with a platform to extend your Fusion Applications extensively.

Steps to Enable

You don't need to do anything to enable this feature.

Key Resources