If you are using version 119 or later of the Chrome browser, you might see the following error when trying to create a Service Connection to OIC integrations (using the "Select from Catalog") option:

"Error: "Network Error Unable to read the integrations from [vb-catalog://backends/ics/ic/api/integration/v1/integrations]. Please check the settings for Integration Applications and verify that Integration Applications server is working."

The reason for the error is that starting with version 119, the Chrome browser treats cross-domain redirects and CORS differently than earlier versions.

If you encounter the error, navigate to the "Integration Applications" backend and change the Connection Type to "Always use proxy, irrespective of CORS support" to eliminate the CORS issue.

When creating a service connection to an OIC Integration REST API, connecting to the service might fail if you select an authentication mechanism that is not permitted by the OIC Integration REST service's settings.

If the connection to the service fails with a 401 HTTP error code, check if the authentication settings for the VB Service Connection match the OIC Rest Trigger's Security settings.

If using the catalog for Integration applications, and the Integration Applications backend is configured with Basic Auth, retrieving the catalog will fail. In Oracle Integration 3, all OIC factory endpoints, including the one that retrieves the catalog endpoints, require OAuth authentication. To update the authentication type, navigate to the Integration Applications backend and set the authentication type to "Oracle Cloud Account", or any of the relevant OAuth types. The nearest replacement for Basic Auth is "OAuth 2.0 Resource Owner Password".

If you create the same service connection from an endpoint or specification, updating the authentication type is not needed, provided that:

• If the VB Service Connection to an openAPI based Integration uses "Oracle Cloud Account" or any of the OAuth 2.0 methods for authentication, then the corresponding OIC REST Trigger needs to be configured with either the "OAuth 2.0" or "OAuth 2.0 OR Basic" options.
• If the VB Service Connection to an openAPI-based Integration uses "Basic" for authentication, then the corresponding OIC REST Trigger needs to be configured with either the "Basic" or "OAuth 2.0 OR Basic" options.

If you are creating a Service Connection to an OIC REST endpoint that is not an openAPI-based Integration, then most likely only OAuth will be allowed. For details, see When is Basic Authentication Supported in Oracle Integration 3? and the relevant OIC documentation.

When creating a service connection to an Oracle Integration service, Integration Applications created within an Oracle Integration 3 project are not included in the list of available services in the Service Catalog.

To create a service connection to integrations within a project, the workaround is to either define the specification or define the service endpoint in the Create Service Connection wizard:

1. Open the Create Service Connection wizard.
2. Do either of the following:
   • Select "Define by Specification" and specify the URL of the Oracle Integration 3 OpenAPI/Swagger.
   • Select "Define by Endpoint" and enter the Oracle Integration 3 endpoint URL.

Testing a service connection representing an IDCS REST API with OAuth 2 User Assertion Authentication type in the Test tab will not work. In doing so, you will face an error like:

{
"type": "abcs://proxy_problem/oauth/design_allowed_scope",
"title": "Invalid URI",
"detail": "Cannot process \"https://<idcs>.identity.oraclecloud.com/admin/v1/Me\"",
"status": 400,
"o:errorDetails": [
{ "type": "abcs://proxy_problem/auth/scope/update", "title": "Invalid service scope",
      "detail": "Cannot process service scope \"urn:opc:idm:t.user.me\" in IDCS, for URI \"
{1}
\"",
"status": 400
}
]
}

This limitation only exists in the Service Tester (Test tab). Creating a web app and calling the same REST API from the web app works without any issues.

If you are using a backend that is configured with a secure header, and you create a service connection on the backend, you might receive an error when testing the connection. The wizards for creating a service connection from an endpoint and from a specification ignore the security header, which can result in the connection failing.

The workaround is to create and save an example response in the Create Service Connection from Endpoint wizard:

• Open the Create Service Connection from Endpoint wizard.
• Enter the endpoint and other connection details.
• Open the Response tab.
• In the Example text area, enter an example response (for example, {"test" : "abc"}), and then click Save Example. This creates a schema for the example.
• Click Create to create the service connection.

If you now test the connection to the endpoint, the connection is successful, and you can save the response. You can now save the actual response, which will correctly update the response schema of the service connection.

When creating a service connection from the catalog for Oracle Integrations, the endpoint you want to use might not be listed if you have more than 100 active integrations. Visual Builder currently fetches the first 100 integrations in the catalog, and then extracts the integrations that have a valid swagger endpoint to be displayed in the catalog.

If your integration isn't listed, the workaround for creating the service connection is to create it from a specification:

1. Locate the metadata URL for the OIC integration, and open the metadata URL in the browser. The metadata page will provide you with the swagger URL (the metadata URL will be similar to https://<OIC base URL>/ic/api/integration/v1/flows/rest/ECHO/1.0/metadata, and the swagger URL will be similar to https://<OIC base URL>/ic/api/integration/v1/flows/rest/ECHO/1.0/metadata/swagger). Note that Visual Builder can only consume swagger-based integrations directly via the catalog or the specification flow.
2. In Visual Builder, open the Create Service Connection wizard, and then select Define by Specification.
3. Enter a service name, and then select OpenAPI/Swagger as the API Type.
4. In the URL field, select the "Integration Applications" backend (backends/ics), and then enter the rest of the URL after the backend (for example, ic/api/integration/v1/flows/rest/ECHO/1.0/metadata/swagger). You can click the info icon to see the full form of the URL.
5. In the Metadata Retrieval Option field, select Copy full OpenAPI to the application. Click Create.

   If you see a dialog "Compute missing operation ids", this means Visual Builder has detected operation ids missing from the swagger or openapi from OIC. Select "Compute missing operation ids", and then proceed.

You can check if the created service connection works in the Test tab.

When creating a service connection to Integration Applications from the catalog, creating the connection might fail with the following error:

Error "Type 'Operation' can't map property 'X-OIC-CONSUMPTION-WARNING-CASDK-0063' to a valid type. Verify that the property name is valid in this context.

The error is caused by an invalid swagger coming from OIC. The invalid swagger prevents Visual Builder from creating the service connection.

If you are using version 119 or later of the Chrome browser, you might see the following error when trying to configure a connection to services in Oracle Integration:

"Error: Cross-origin resource sharing error: Missing Allow origin header"

The reason for the error is that starting with version 119, the Chrome browser treats cross-domain redirects and CORS differently than earlier versions.

If you encounter the error, navigate to the "Integration Applications" backend and change the Connection Type to "Always use proxy, irrespective of CORS support" to eliminate the CORS issue.

Your staged or published apps might stop working if they use service connections with self-signed certificates and the certificates have expired. Any certificates issued after 2020-09-01T00:00:00.00Z will automatically expire 398 days after they have been issued. If your apps use certificates issued before 2020-09-01T00:00:00.00Z, the certificates will not expire, but you should update them with a newer certificate.

To avoid disruptions, you should plan regular updates to refresh the self-signed certificates before they expire (for example, every 6 months). It's not recommended to use self-signed certificates in production apps.

When you create new business objects from a file (CSV, zip, xls) using the Import Business Object wizard, the business objects might not be selected when you open the Business Object Resource Editor in the Endpoints tab, but the available new business objects should be selected by default when you open the editor.

If the business objects are not selected by default:

1. Reload your browser. After reloading the browser, the business objects should be selected in the Business Object Resource Editor.
2. Choose the business objects you want to expose.
3. Click Apply Defaults, then click Save.

When trying to save a business object diagram as an image, you might see the following issues:

• It's not possible to save the diagram as a PNG image.
• When saving the diagram as a SVG file, the icons representing the business object field types are not displayed correctly in the saved image. All the icons are rendered as "broken" images.

The workaround to save a diagram where the field icons are intact is to use the zoom in/out tools to make the entire diagram visible, and then to take a screen shot of the diagram using a screen capture application.

If your Visual Builder instance is configured to use another Oracle DB, when you use the REST API to insert a new record in a table you might see a response that contains no data, even though the insert is successful and the call returns the expected status (HTTP 201).

This can happen when a business object has a primary key field defined as <column name> NUMBER GENERATED BY DEFAULT ON NULL AS IDENTITY ....

The workaround is to perform the following steps to modify the business object's primary key field:

1. Open the application in Visual Builder.
2. Open the business object you want to modify.
3. Open the Fields tab.
4. Select the primary key field.
5. In the Sequence Name dropdown list, select the appropriate internal sequence used by the database to create new records in the table.

   If the database schema has only one table with an identity column, it should be clear which sequence to select (the sequence will have an internal looking name). If there is more than one table with an identity column, you can use the following query to locate the sequence the database created for the column:

   select data_default from SYS.user_tab_columns where table_name = <table name used by the BO> and column_name = <primary key field>;

After the Sequence Name property is set to the the correct sequence, Visual Builder will select nextval from that sequence before inserting the record into the table, and will use that value in the primary key column.

After upgrading your application, some components might not load data correctly when bound to an ADP variable, if the application/page's JSON / JavaScript files contain configurations or code that returns invalid JSON data.

When using the Filter field in the Designer, Chrome's Autofill form data feature might populate the field in some panels and dialogs with cached data. For example, when using the Filter field in the Navigator, the field might display your cached email address. If cached data is appearing in the field, clear Chrome's cached Autofill form data:

1. Click the three dots at the top right of the Chrome browser window to open the Chrome options menu.
2. Select More tools > Clear browsing data in the menu.
3. Open the Advanced tab in the Clear browsing data dialog box.
4. Select All Time in the Time range dropdown list.
5. Select Autofill form data in the list. Click Clear Data.

Staging a PWA app might fail on instances in government realms.

The sample SaaS R13 LightBlue theme (ApplicationsCloudUITheme) is deprecated as it relies on the deprecated Alta theme. If any of your existing apps use this theme, you are strongly encouraged to convert them to use the Redwood or Stable themes, and then customize the theme using CSS variables.

The sample SaaS R13 LightBlue theme update for Oracle Visual Builder 22.10 is the final planned update.

For existing apps that still use the SaaS R13 LightBlue theme, you'll need to apply the update before running the app with Oracle Visual Builder 22.10. To upgrade the theme, download the updated version of the Oracle SaaS R13 theme files (ApplicationsCloudUI-n.n.n.zip) from the vbcs-samples repository on GitHub, import the updated theme resources into your application, and select the updated theme in your web app's Settings editor. For details on the upgrade steps, see Upgrading the Sample R13 SaaS LightBlue Theme for Visual Builder.

You might not be able to upgrade an application's theme because the theme dropdown list is not available or is not working properly.

If you run into this situation, the workaround is to upgrade the application:

1. Upgrade the app version to the next higher version (for example, from version 21.07 to 21.10).
2. Upgrade the application's theme.

You might see errors or have problems when creating new versions of an app if the app has too many obsolete versions. Visual Builder limits the total number of versions of an app to 100, which includes development, staged and obsolete versions. You cannot create a new version if it will result in the limit being exceeded.

Each time you publish a new version of an app, the previous version becomes obsolete. On the Visual Builder Home page, you can see the total number of app versions in the Versions column, next to the number of the current version.

To remove obsolete app versions, you must first move them to the Trash, and then permanently delete them. For details, see Delete a Visual Application.

When running an app in the Chrome browser on devices running Android 14, invoking the camera component from the app to capture a photo might not work correctly.

The workaround is to edit the File Picker's Accept property in the app to add "text/plain", and then republish the app.

If you add JSON resources to your app, as shown in these code snippets, the Oracle Offline Persistence Toolkit stops working.

// Add resource
define([
  'text!resources2/js/test.json'
], function(

// Where resources2 is defined as:
  "requirejs": {
        "paths": {
            "resources2": "{{ location.pathname + (window.vbInitConfig.BASE_URL_TOKEN ? 
                          window.vbInitConfig.BASE_URL_TOKEN + '/' : '') + 'resources'}}"
        }
    },

The following error occurs when the app tries to load the Oracle Offline Persistence Toolkit.

Failed to load offline handler from /ic/builder/rt/otf/2.0/webApps/foo/
version_279023731935549663/app-flow.js: Error: importScripts failed for /ic/builder/rt/otf/2.0/
webApps/foo/version_279023731935549663/app-flow.js at /ic/builder/rt/otf/2.0/webApps/foo/versio
n_279023731935549663/app-flow.js
https://requirejs.org/docs/errors.html#importscripts

Two possible workarounds exist to address this issue:

1. Wrap the JSON file in a JavaScript file and load the JavaScript file.
2. Use the Fetch API to load the JSON file in the offline handler.

When deploying an application to a Visual Builder instance, you might see the error message 502 Bad Gateway, and the build log might state that deployment failed.

If you see this error when deploying the app using the grunt vb-deploy task, the workaround is to update package.json so that the grunt build uses the grunt-vb-build-2504.0.28.tar.gz version of the grunt-vb-build library.

If you see this error when deploying the app through the pipeline, verify if the app was deployed correctly to the target instance. In some cases, the error message is displayed though the app was deployed successfully, in which case you can disregard the error message. There is no current workaround if the app was not deployed.

Service connections to the Oracle Integration design-time (or factory) APIs, created using the endpoint flow in Visual Builder, that are not listed in the catalog, will not work after the migration, and you need to update them.

An example of such an endpoint is a lookup endpoint (see Lookups REST Endpoints in REST API for Oracle Integration 3). When you test them in the service connection's Test tab, these endpoints will typically give error code HTTP 403, with the error "Unable to verify URL against allowed list". See SendRequest in REST API for Oracle Integration 3 for more on the design-time URL and factory APIs.

When updating backends and service connections, bear in mind that Oracle Integration 3 does not accept Basic Auth, and recommends OAuth. For more details, see When is Basic Authentication Supported in Oracle Integration 3?

To rework these service connections using a custom backend:

1. Create a custom backend called icsFactoryApi (for example). For the URL, use the design-time URL (for example, https://design.integration.region.ocp.oraclecloud.com), and use OAuth authentication (generally OAuth 2.0 Resource Owner Password). Set the connection type to "Always Use Proxy" (recommended).
2. For existing service connections based on design-time APIs:
   1. Change the URL from vb-catalog://backends/ics to point to vb-catalog://backends/icsFactoryAPI. (If the URL is https://<integration_base_url>, then replace <integration_base_url> with vb-catalog://backends/icsFactoryAPI).
   2. Navigate to the Request tab, and then add the static query parameter of "integrationInstance", and add the appropriate value.
3. The static query parameter introduced this way becomes part of the visual application code. This parameter will be different for different Integration instances, so you would need to update the parameter if you import the app to another instance (for example, a PROD instance). If you use a build pipeline, you would need to modify the parameter in the packaging jobs.

Applications that have very old VB runtime versions might break when upgraded to Oracle Integration 3 if artifacts in the app contain old static references. To avoid this, Oracle recommends that you upgrade the applications to the supported VB runtime and JET versions prior to upgrading to Oracle Integration 3. To understand which VB runtime versions are supported and how to upgrade your app, see Upgrade Policy and Upgrade your app. If you cannot do this prior to upgrading to Oracle Integration 3, you will need to restage or republish the application after upgrading to Oracle Integration 3.

After upgrading a Visual Builder instance on Oracle Integration Gen 2 to Oracle Integration 3, your live app might stop working if the app is still trying to access business objects on the Oracle Integration Gen 2 instance.

The workaround is to update the service definition to the new host name, and then re-deploy the app:

1. In the Services pane, open the service connection that is representing the Business Objects using the older Visual Builder URL.
2. In the Servers tab, click Default Server to open the service definition used by the connection.
3. In the Servers tab for the service definition, click Edit to open the Edit Server dialog.
4. In the Instance URL field, update the host name to the host name of your Visual Builder instance on Oracle Integration 3. Click Save.
5. Re-deploy your app.

To facilitate exporting and importing Visual Builder applications between different VB instances, the applications typically don’t contain any references to the URL of the Visual Builder instance. However, if you have written custom code in your application that references a Visual Builder instance URL, accessing this URL might fail when your instance is upgraded to Oracle Integration 3. In this case, you will need to update the references to the old, pre-upgrade Visual Builder URL with the new Visual Builder URL.

PWA apps installed on user devices no longer receive automatic updates after your Visual Builder instance is migrated from Oracle Integration Gen 2 to Oracle Integration 3.

When users install PWA apps, the URL for your Visual Builder instance is embedded in the app. If the embedded URL points to a Visual Builder instance in Oracle Integration Gen 2, the app will no longer receive updates because redirecting to the URL for the Visual Builder instance in Oracle Inetegration 3 is not possible.

To receive updates to the app, the user needs to re-install the PWA app from the new Visual Builder location in Oracle Integration 3.