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.

The log messages for Groovy scripts in your application might not appear in the Groovy Logs tab in the Trace pane, though tracing is enabled.

If the Groovy logs are not appearing in the Trace pane, open the Logs pane, and then click Enable Logging. The Groovy logs will now be displayed in the Trace pane when you enable tracing.

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.

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.

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.

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.

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 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.

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.

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.

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.