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.

The Logs and Trace tools for business objects are not supported in Visual Builder Studio. The Logs tab in Visual Builder Studio does not display logs related to business objects. The Trace tab has been hidden.

If you want to use the Logs and Trace tools for business objects, open the associated Oracle Visual Builder or Oracle Integration environment and then open the app.

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.

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.

In the Organization page's VM Build Executors tab, the name of the free VM executor template is displayed as "System Default OL7 for Visual Builder" in the table. The name of the template is incorrect, and the template is actually the updated System Default OL8 for Visual Builder.

Publishing your app extension might cause your Oracle Cloud Application to stop working if your extension uses Oracle JET packs or web components that are not hosted on CDN, which means the pack or web component resources are included in your extension when you build it. Your Cloud Application might stop working if any of these resources were already optimized prior to you building the extension.

Trying to run a build in Visual Builder Studio might fail with the error Error: Failed to start the VM Agent. This can happen if you are trying to run builds using a free micro Compute VM provided with an Oracle Cloud Free Tier account. The micro VM is not sufficient to run the System Default OL7 for Visual Builder build executor template that includes the necessary software for running VB Studio builds.

If you encounter this issue, you should remove the Oracle Cloud Free Tier account details from the OCI Account tab in the Organization page, and switch to using VB Studio's free VM build executor. The free VM build executor is sufficient to run VB Studio executor system templates. The free VM build executor is available in the VB Studio's built-in free account.

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.

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.

After the Maven update to version 3.9.9 in build VMs, when you run a Maven build job where Vulnerability Analysis is enabled, the Vulnerability Analysis might cause the error Failed to execute goal com.oracle.oscs.plugin:oscs-dcs-mplugin:5.1.0:oscs_scanowaspall (default-cli), causing the build to fail. There is currently no workaround to successfully run the Vulnerability Analysis in a build job.

To get the build to complete successfully, disable the Vulnerability dependency analysis from the build job configuration.

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 the VB Service Connection 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 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.

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.

If you are trying to connect to service endpoints on OIC Gen 3 using the Basic Auth authentication type, the connection will fail because OIC Gen 3 does not accept Basic Auth. You will need to switch the service connection to use a supported authentication type, such as OAuth 2.0 Resource Owner Password.

For more details on how to switch from Basic Auth to OAuth 2.0 Resource Owner Password, see How Do I Resolve Connection Issues to OIC Gen 3 Services?

Starting with Visual Builder 23.07, the size of Oracle Integration Generation 2 Process-related payloads is limited to one million characters. If your Process-related payload is near or greater than the size limit, you should use the Process Cloud Service REST API directly to avoid the size limitation.

Support for Process is not available in Visual Builder instances enabled in Oracle Integration 3.

If your app has service connections to an OIC Gen 2 instance that you created from the catalog, the connections might stop working after the OIC Gen 2 instance is migrated to OIC Gen 3. This is because the design time API URL for the OIC Gen 3 service is different from the API URL for the OIC Gen 2 service.

The workaround:

1. Create a backend based on the design time URL of the API on OIC Gen 3. (For example, https://design.integration..../ic/api/integration/v1/integrations)
2. Update your service connection to use the backend.

   In your service connection, add a static query parameter to model the correct URL for your OIC instance. For example, for an OIC instance myinstance (https://myinstance.integration...), add the query parameter integrationInstance=myinstance to generate the instance's design time URL https://design.integration..../ic/api/integration/v1/integrations?integrationInstance=myinstance

Process related tasks are not supported with anonymous access. If you try to access any process related tasks (for example, Start Process/Perform Task) from a web or mobile app having anonymous access, you might run into this error.

{ "type": "vbcs://process_service_problem", "title": "Process Service Error", "detail": "Authorization failed.", "status": 500, "o:errorCode": "authorizationFailed" }

This will happen even if you manually allow anonymous access and give anonymous access credentials to the Process Applications backend.

When creating or updating a service connection based on a business object URL, you might find that the service connection URL is automatically updated to vb-catalog://backends/ics or vb-catalog://backends/process if you have an OIC or Process instance configured as backends.

Backends are now mandatory for service connections, so Visual Builder tries to match the URL with any existing backend, and uses that backend if found. As a result, if OIC, Process, and business object URLs all point to the same instance, Visual Builder might try to use the same backend. To avoid this, you can do the following:

1. Create a backend called BOBackend with the base URL of the business objects (for example, https://someinstance...oraclecloud.com) and the proper authentication and connection type. (To avoid problems, you might want to consult the service connection you are connecting to, and provide the same details in the backend).
2. Then do the following:
   • For existing service connections based on business objects, replace the URL segment that is based on the BOBackend. An example is shown below, but your URL might be different and have more or fewer segments:

     "servers": [ 
        { "url": "https://someinstance...oraclecloud.com/ic/builder/rt/someapp/1.0.4/resources", 
     "description" : "something""x-vb": { 
             "authentication": { 
                 "authenticated": { "type": "basic", "credentials": "vb_xxx" } 
               } 
          } 
        } 
     ],

     Change it to this:

     "servers": [
        { "url": "vb-catalog://backends/BOBackend/ic/builder/rt/someapp/1.0.4/resources"
        }
     ],

     Test the service connection in the Test tab to confirm it works as expected.

   • For creating new service connections based on business objects, first select the BOBackend in the URL, and then add the remaining part comprising the URL.

Digital Customer Service customers who created visual applications with VB Studio from 20C through 23A will need to take action after migrating to VB Studio 24.10 (24D).

When you create a backend in the Create Service Connection wizard, the backend might not be able to connect to the service because the authentication details are missing. When you use the Define by Endpoint option in the wizard, the authentication details for the new backend in the wizard might not be saved if you also add authentication details for the service in the Server tab.

The workaround is to set the authentication details for the new backend in the wizard, and then create the service without specifying the authentication in the Server tab. After the service is created, edit the backend to set the additional authentication details.

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.

When developing an Oracle Cloud Application extension, the tab for editing JavaScript might not be visible when you open a layout in the Designer.

To open the JavaScript editor, locate the JavaScript file (for example, layout-x.js) in the Source view of the navigator, and then click the file to open it in the Designer. If the JavaScript editor is still not visible in the Designer, click the file again in the navigator.

When working on an app extension, you might see a "Page cannot be previewed" message in the Designer if your browser is blocking access to your Oracle Cloud Application instance. To configure your browser to allow access:

1. Configure the browser's cookies options in chrome://settings/cookies and disable Block third-party cookies, if it's not already disabled.
2. Click Add next to the "Sites allowed to use third-party cookies" option, then type your Oracle Cloud Application host domain in the Add a site dialog box. Click Add.
3. Disable the browser's "SameSite by default cookies" flag by adding --disable-features=SameSiteByDefaultCookies to the browser's startup parameters.

   If you're using Chrome 90 or older, you can disable the "SameSite by default cookies" flag in the browser's Flag options page (chrome://flags).

For more details on setting the browser options, see Resolving the error “Page cannot be previewed” in Extending Oracle Cloud Applications with Visual Builder Studio.

When you are adding a display logic rule in a dynamic form rule set, rules containing $fields.<fieldName>.value() are not applicable if the form is using a GET Many endpoint. You'll need to change the field identifier to something like $value.<fieldName>.

If you are using Markdown for your project's wiki pages, lists and paragraphs on some pages might look different if they use syntax incompatible with the updated wiki support in Visual Builder Studio 24.07. As a result of the update, some lists that contain embedded constructs (such as code) might be displayed differently, and pages might contain unexpected line breaks.

The workaround is to manually edit the wiki pages that are not displaying correctly. To add a line break in a page using the Markdown markup:

• type two spaces, followed by a return, or
• type a backslash (\), followed by a return.

When you use the Edit Page in Visual Builder Studio option to customize Oracle Cloud Applications, if your Oracle Cloud Applications instance is connected to your VB Studio instance in the same identity domain via Basic Auth or three-legged OAuth, VB Studio won't create a workspace or open an existing workspace associated with that environment. This is by design.

Instead, a new environment with the Oracle Cloud Applications instance added as an IDCS resource is created for you and associated with either a new or existing workspace. For more information, see Configure an Oracle Cloud Application.