Deploy Oracle Visual Builder Applications.

Either FDOVB_CLOUD_ACCOUNT_CODE environment instance property value or FDOVB_INP_CLOUD_ACCOUNT_CODE plugin input value should exist. When both exists, plugin input value will take precedence. See Creating/Editing a Cloud Account and Provider for details on how to setup Cloud Account for OVB.

If a team.json file is found in the artifacts directory, it will be imported into the instance after being deployed. To get a team.json file, look at the export team input in the export application operation.

In order to deploy an application it must have both the rootURL and version set in the visual-application.json file. The rootURL is used as the application ID and version as the version. If you use the export application operation this will be set automatically.

Environment/Instance Properties

Property Name	Property Code	Required	Description
Oracle Visual Builder Account	`FDOVB_CLOUD_ACCOUNT_CODE`	No	The OVB account with all the required properties like Base URI, Username and Password for running OVB Instance.

Project Properties

Property Name	Property Code	Required	Description
Application Profile ID	`FDOVB_APPLICATION_PROFILE_ID`	No	Oracle Visual Builder Application Profile ID. Default is generally base_configuration.

Inputs

Input Name	Input Code	Required	Description
Oracle Visual Builder Account	`FDOVB_INP_CLOUD_ACCOUNT_CODE`	No	The OVB account with all the required properties like Base URI, Username and Password for running OVB Instance.
Publish Application	`FDOVB_INP_PUBLISH`	No	Publish the app, or just stage it.
Delete if Already Live	`FDOVB_INP_DELETE_IF_ALREADY_LIVE`	No	Delete the app if it is already live. If this option is checked, basic auth is not supported. This is due to the REST API being used to determine if an app is already live.
Schema	FDOVB_INP_SCHEMA	No	Specifies data schema processing during application stage or publish. Value of 'new' creates a new data schema. Value of 'dev' uses the data schema from development. Value of 'stage' uses the data schema from the previous staged version of the application. Value of 'live' uses the data schema from the previous live version of the application. Defaults to 'new'

Artifacts

This operation consumes artifacts from the artifacts repository.

Endpoint Selection

This operation delegates the selection to the workflow developer to determine.

Endpoint Execution

This operations delegates the execution to the workflow developer to decide.

Special Considerations

The visual-application.json file within the application must have "rootURL" and "version" key-value pairs set for deployment. This mainly applies to cases where Visual Builder Studio GIT repository is not used.

@since 5.7.0.11 If exportApplication operation is used, "rootURL" and "version" key-value pairs will automatically be created in visual-application.json

Browser not supported