Oracle® Cloud

Known Issues for Oracle Integration 3

F45533-31
March 2025
Oracle Cloud Known Issues for Oracle Integration 3,

F45533-31

Copyright © 2022, 2025, Oracle and/or its affiliates.

Primary Author: Oracle Corporation

This software and related documentation are provided under a license agreement containing restrictions on use and
disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or
allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit,
perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation
of this software, unless required by law for interoperability, is prohibited.

The information contained herein is subject to change without notice and is not warranted to be error-free. If you find
any errors, please report them to us in writing.

If this is software, software documentation, data (as defined in the Federal Acquisition Regulation), or related
documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then
the following notice is applicable:

U.S. GOVERNMENT END USERS: Oracle programs (including any operating system, integrated software, any
programs embedded, installed, or activated on delivered hardware, and modifications of such programs) and Oracle
computer documentation or other Oracle data delivered to or accessed by U.S. Government end users are "commercial
computer software," "commercial computer software documentation," or "limited rights data" pursuant to the applicable
Federal Acquisition Regulation and agency-specific supplemental regulations. As such, the use, reproduction,
duplication, release, display, disclosure, modification, preparation of derivative works, and/or adaptation of i) Oracle
programs (including any operating system, integrated software, any programs embedded, installed, or activated on
delivered hardware, and modifications of such programs), ii) Oracle computer documentation and/or iii) other Oracle
data, is subject to the rights and limitations specified in the license contained in the applicable contract. The terms
governing the U.S. Government's use of Oracle cloud services are defined by the applicable contract for such services.
No other rights are granted to the U.S. Government.

This software or hardware is developed for general use in a variety of information management applications. It is not
developed or intended for use in any inherently dangerous applications, including applications that may create a risk of
personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all
appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its
affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.

Oracle®, Java, MySQL, and NetSuite are registered trademarks of Oracle and/or its affiliates. Other names may be
trademarks of their respective owners.

Intel and Intel Inside are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used
under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Epyc, and the AMD logo
are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open
Group.

This software or hardware and documentation may provide access to or information about content, products, and
services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all
warranties of any kind with respect to third-party content, products, and services unless otherwise set forth in an
applicable agreement between you and Oracle. Oracle Corporation and its affiliates will not be responsible for any loss,
costs, or damages incurred due to your access to or use of third-party content, products, or services, except as set forth
in an applicable agreement between you and Oracle.
Contents

1 Common Issues
List of Deprecated Native Format Annotations in Oracle Integration 3 1-1
Recipes Documentation Does Not Reflect Oracle Integration 3 User Interface 1-3
Instance unavailable for one minute after creation 1-3

2 Integrations Issues
Adapter Issues 2-1
REST Adapter Multipart/Mixed Option Issue 2-1
Private Endpoints and Oracle Fusion Applications Adapters 2-1
Oracle HCM Cloud Adapter ZIP File Issues 2-1
Oracle E-Business Suite Adapter Issues 2-1
Integration Issues 2-2
Errors in a Tenancy Migrated from Oracle Identity Cloud Service to an Identity Domain 2-2
Windows 10 Design-Time Issues 2-3

3 Oracle Cloud Infrastructure Process Automation Issues

4 File Server Issues

Copying Issue Encountered Using WinSCP 4-1
File Names Limited to 924 Characters 4-1
Data Removed from Files During Simultaneous Updates 4-1
Read-Only Users Can Delete Files Using WinSCP 4-1

5 Visual Builder Issues

Unsupported Features 5-1
Supported Browsers 5-1
Upgrade Policy 5-2
Known Issues 5-2
Known Issues in Service Connections 5-2
Invoking OIC REST API from Service Connection returns 404 error 5-3

iii
 Authentication failing on OIC service connections 5-3
Integration Applications not listed in Service Catalog 5-4
Error testing connection to IDCS REST APIs with OAuth User Assertion
Authentication type 5-4
Create service connection wizards ignore secure header setting 5-5
Integration endpoint not listed in catalog 5-5
Error creating service connection to Integration Applications from catalog 5-6
CORS error when connecting to Oracle Integration 5-6
Service connection using self-signed certificate not working 5-6
Known Issues in Business Objects 5-6
New business objects not selected in Business Object Resource Editor 5-6
Problems when saving business object diagram as image 5-7
Creating new record using REST API results in empty response 5-7
Known Issues in the Page Designer 5-8
Component not loading in page after upgrading application 5-8
Filter field populated with cached data 5-8
Known Issues in Creating and Building Projects 5-8
Staging PWA app fails in government realm 5-9
Update deprecated Oracle SaaS application template theme 5-9
Cannot switch theme in application settings 5-9
Error when creating new version of application 5-9
Camera component no longer offers camera capture option on Chrome browser on
Android 14 5-10
Loading JSON using Text module stops Persistence Toolkit working 5-10
Error 502 Bad Gateway when deploying visual app 5-10
Known Issues for Live/Staged Apps Post-Upgrade to Oracle Integration 3 5-11
Cannot access non-catalog Integration REST APIs in app 5-11
Visual Builder apps on obsolete VB runtime versions 5-12
Unable to access VB business object URLs from service connections in live app 5-12
Custom code accessing pre-upgrade Visual Builder URL failing 5-12
PWA app no longer receives updates automatically after upgrade to Oracle
Integration 3 5-12

iv
Preface
Known Issues for Oracle Integration 3 describes issues you may encounter when using Oracle
Integration and possible workarounds.

Topics:
• Documentation Accessibility
• Diversity and Inclusion
• Related Resources
• Conventions

Documentation Accessibility
For information about Oracle's commitment to accessibility, visit the Oracle Accessibility
Program website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc.

Access to Oracle Support

Oracle customer access to and use of Oracle support services will be pursuant to the terms
and conditions specified in their Oracle order for the applicable services.

Diversity and Inclusion

Oracle is fully committed to diversity and inclusion. Oracle respects and values having a
diverse workforce that increases thought leadership and innovation. As part of our initiative to
build a more inclusive culture that positively impacts our employees, customers, and partners,
we are working to remove insensitive terms from our products and documentation. We are also
mindful of the necessity to maintain compatibility with our customers' existing technologies and
the need to ensure continuity of service as Oracle's offerings and industry standards evolve.
Because of these technical constraints, our effort to remove insensitive terms is ongoing and
will take time and external cooperation.

Related Resources
For more information, see these Oracle resources:
• Oracle Integration documentation on the Oracle Help Center.
• Oracle Cloud at http://cloud.oracle.com.

Conventions
The following text conventions are used in this document.

Convention Meaning
boldface Boldface type indicates graphical user interface elements associated with an
action, or terms defined in text or the glossary.

5
 Conventions

Convention Meaning
italic Italic type indicates book titles, emphasis, or placeholder variables for which
you supply particular values.
monospace Monospace type indicates commands within a paragraph, URLs, code in
examples, text that appears on the screen, or text that you enter.

6
1
Common Issues
Review Oracle Integration common issues.

Topics:
• List of Deprecated Native Format Annotations in Oracle Integration 3
• Recipes Documentation Does Not Reflect Oracle Integration 3 User Interface
• Instance unavailable for one minute after creation

List of Deprecated Native Format Annotations in Oracle

Integration 3
If you plan to upload custom schemas (from Oracle SOA Suite) to Oracle Integration, the
following annotations are deprecated and may be removed in future releases of Oracle
Integration. This section only covers the names of the directives that are deprecated. For a
detailed description of the directives, see the latest Oracle SOA Suite documentation.

Schema-Level Directives
The following directives are provided as attributes under the schema. For example:

<xsd:schema ... xmlns:nxsd="http://xmlns.oracle.com/pcbpel/nxsd"

nxsd:version="NXSD" ...>

nxsd:byteOrder e.g nxsd:byteOrder="bigEndian" or

nxsd:byteOrder="littleEndian"
nxsd:dataLines e.g. nxsd:dataLines="10"
nxsd:detectLoops e.g. nxsd:detectLoops="false"
nxsd:eofEqualsEOL e.g nxsd:eofEqualsEOL="false"
nxsd:outboundHeader e.g. nxsd:outboundHeader="this is the header"
nxsd:prettyPrint e.g nxsd:prettyPrint="true"
nxsd:readerBufferSize e.g. nxsd:readerBufferSize="2048"
nxsd:standalone e.g. nxsd:standalone="true"
nxsd:stream with bytes e.g. nxsd:stream="bytes" (OIC3 only supports
nxsd:stream="chars")
nxsd:useArrayIdentifiers e.g. nxsd:useArrayIdentifiers="true"
nxsd:fieldValidation e.g. nxsd:fieldValidation="true"
nxsd:validation e.g. nxsd:validation="true"
nxsd:validateNxsd e.g. nxsd:validateNxsd="true"
nxsd:xlationMode e.g. nxsd:xlationMode="lax"

1-1
 Chapter 1
List of Deprecated Native Format Annotations in Oracle Integration 3

Field-Level Directives
The following directives are provided either as simpleTypes, complexTypes, or element
definitions in the schema. These directives are deprecated and may be removed in later
versions of Oracle Integration.
Array style constructs:

nxsd:style="array"
nxsd:arrayLength="<<length>>" e.g. nxsd:arrayLength="10"
nxsd:cellSeparatedBy="<<literal>>" e.g. nxsd:cellSeparatedBy="\n"
nxsd:arrayTerminatedBy="<<literal>>" nxsd:arrayTerminatedBy="#"
nxsd:arrayIdentifierLength="<<length>>" e.g. nxsd:arrayIdentifierLength="2"

LookAhead constructs:

nxsd:lookAhead="<<length>>" e.g. nxsd:lookAhead="100"

nxsd:lookTill="<<literal>>" e.g. nxsd:lookTill="order"
nxsd:scan="<<length>>" e.g nxsd:scan="3"
nxsd:lookFor="<<literal>>" e.g. nxsd:lookFor="TRUE"
nxsd:lookForPattern="<<regex pattern>>" e.g. nxsd:lookForPattern=".purchase."
nxsd:scanLength="<<length>>" e.g nxsd:scanLength="3"
nxsd:reportLookAheadError="<<true|false>>" e.g.
nxsd:reportLookAheadError="true"

Skip constructs:

nxsd:skip="<<number of characters>>" e.g. nxsd:skip="10"

nxsd:skipLines="<<number of lines to skip>>" e.g. nxsd:skipLines="10"
nxsd:skipUntil="<<skip until characters>>" e.g. nxsd:skipUntil="\n"

List constructs:

nxsd:style="list"
nxsd:itemsSeparatedBy="<<literal>>" e.g nxsd:itemsSeparatedBy=","
nxsd:listTerminatedBy="<<literal>>" e.g. nxsd:listTerminatedBy="\n"

Surrounded constructs:

nxsd:style="surrounded"
nxsd:surroundedBy="<<literal>>" e.g. nxsd:surroundedBy="^"
nxsd:leftsurroundedBy="<<literal>>" e.g. nxsd:leftsurroundedBy="
{" nxsd:rightsurroundedBy="<<literal>>" e.g. nxsd:rightsurroundedBy="}
"

Write constructs:

nxsd:write="<<literal>>" e.g. nxsd:write="Mr."

nxsd:writeMode="before|after" e.g. nxsd:writeMode="before"

1-2
 Chapter 1
Recipes Documentation Does Not Reflect Oracle Integration 3 User Interface

Timezone and Date formats:

nxsd:useTimeZone="UTC"
nxsd:dateFormat="MM-dd-yyyy"

Conditional constructs:

nxsd:choiceCondition="fixedLength" nxsd:length="2"
nxsd:conditionValue="<<literal>>" e.g. nxsd:conditionValue="PO"

Variable constructs:

<nxsd:variables>
<nxsd:variable name="customerZip"/>
</nxsd:variables>
<nxsd:variable name="someName" value="someValue" />

Recipes Documentation Does Not Reflect Oracle Integration 3

User Interface
The documentation for many recipes has been updated to provide steps using the Oracle
Integration 3 user interface. However, the documentation for some recipes still currently
reflects the Oracle Integration Generation 2 user interface.
For a full list of accelerators and recipes currently available for Oracle Integration, see Recipes.

Instance unavailable for one minute after creation

If you try to open an instance within one minute of creating it, an error occurs.
As a workaround, wait one minute after creating an instance to access it.

1-3
2
Integrations Issues
Review Integrations issues in Oracle Integration.

Topics:
• Adapter Issues
• Integration Issues

Adapter Issues
Review known issues associated with adapters.

Topics:
• REST Adapter Multipart/Mixed Option Issue
• Private Endpoints and Oracle Fusion Applications Adapters
• Oracle HCM Cloud Adapter ZIP File Issues
• Oracle E-Business Suite Adapter Issues

REST Adapter Multipart/Mixed Option Issue

If you are using the multipart/mixed option with XML Schema or XML Sample as your payload
format in the REST Adapter and view the Request/Response pages in the Adapter Endpoint
Configuration Wizard in edit or view mode, JSON Sample is shown as selected. Re-upload
your sample payload. Despite JSON Sample appearing, this doesn't affect runtime and your
XML payload is parsed correctly for mapping.

Private Endpoints and Oracle Fusion Applications Adapters

When a private endpoint is enabled for an Oracle ERP Cloud Adapter, Oracle HCM Cloud
Adapter, or Oracle CX Sales and B2B Service Adapter connection, creation of the endpoint
during design time may fail for certain SOAP business objects.

Oracle HCM Cloud Adapter ZIP File Issues

Note the following issues when using the Oracle HCM Cloud Adapter ZIP file feature:
• A ZIP file that is extracted using the Oracle HCM Cloud Adapter must only contain a single
file. If there are multiple files, only the file with the most recent time stamp is extracted.
• The supported method for using the Oracle HCM Cloud Adapter ZIP file feature is to first
zip your files, and then encrypt them.

Oracle E-Business Suite Adapter Issues

2-1
 Chapter 2
Integration Issues

When using the Oracle E-Business Suite Adapter in an integration, you may encounter the
following issues:
• Trading partner setup form does not accept a password with special characters
The Trading Partner Setup form does not accept a password with special characters.
Therefore, the Oracle Integration password should be a combination of text and numbers.
To resolve this issue, apply the following patches to enable Oracle XML Gateway to accept
passwords with special characters:
– For Oracle E-Business Suite Release 12.2, apply Patch 27752692:R12.ECX.C.
– For Oracle E-Business Suite Release 12.1.3, apply Patch 28310667:R12.ECX.B.
• Service invocation fails for certain PL/SQL APIs with table type input parameters
When invoking certain PL/SQL APIs having table type input parameters, the following
exception may occur:

java.sql.SQLException: ORA-06531: Reference to uninitialized collection

ORA-06512

To resolve the exception, pass an empty element in the request corresponding to the table
type in the API. For example, when invoking the PROCESS_BOM API with table type
parameters P_BOM_REVISION_TBL, P_BOM_REF_DESIGNATOR_TBL, and
P_BOM_SUB_COMPONENT_TBL, pass the empty tags as a workaround:
1. Export the integration with the mappings for the Oracle E-Business Suite request.
2. Locate the corresponding .xsl file to change the mapping entries for
P_BOM_REVISION_TBL, P_BOM_REF_DESIGNATOR_TBL, and P_BOM_SUB_COMPONENT_TBL as
follows:

<P_BOM_REVISION_TBL/>
<P_BOM_REF_DESIGNATOR_TBL/>
<P_BOM_SUB_COMPONENT_TBL/>

3. Import this modified mapping for the request mapping.

4. Activate the integration and the API should be invoked successfully.

Integration Issues
Review known issues associated with integrations.

Topics:
• Errors in a Tenancy Migrated from Oracle Identity Cloud Service to an Identity Domain
• Windows 10 Design-Time Issues

Errors in a Tenancy Migrated from Oracle Identity Cloud Service to an

Identity Domain
If your Oracle Integration instance tenancy was migrated from Oracle Identity Cloud Service to
an identity domain, you can receive errors when using the OCI Object storage and OCI

2-2
 Chapter 2
Integration Issues

Function actions or using a terraform script-generated service instance. These issues don’t
impact tenancies that were always enabled for identity domains.

Using OCI Object Storage or OCI Function Error in a Tenancy Migrated from Oracle
Identity Cloud Service to an Identity Domain
If you attempt to use the OCI Object storage action or OCI Function action in an integration,
you can receive the following errors. Open a service request (SR) against Oracle Cloud
Infrastructure Identity and Access Management (OCI IAM) and request a fix for Jira issue
IDCS-152404.
• OCI Object storage action:

oracle.tip.tools.adapters.cloud.api.CloudAdapterException:
Couldn't authenticate while querying OCI Object Storage. You may need
to enable identity domains for your instance in Oracle Cloud
Infrastructure.

• OCI Function action:

Couldn't authenticate while invoking an OCI Function. You may need

to enable identity domains for your instance in Oracle Cloud
Infrastructure.

Using a Terraform Script-Generated Service Instance in a Tenancy Migrated from Oracle

Identity Cloud Service to an Identity Domain
Terraform script-generated service instances don't work. Open a service request (SR) against
Oracle Cloud Infrastructure Identity and Access Management (OCI IAM) and request a fix for
Jira issue IDCS-152404.

Windows 10 Design-Time Issues

If you attempt to drag a connection into an integration when using the Chrome browser on
Windows 10, the connection is not added. If you use Internet Explorer, a forbidden icon is
displayed.
If you disable support for the touch screen and restart the browser, this issue goes away.

2-3
3
Oracle Cloud Infrastructure Process
Automation Issues
Review Oracle Cloud Infrastructure Process Automation issues in Oracle Integration.
See Known Issues for Oracle Cloud Infrastructure Process Automation.

3-1
4
File Server Issues
Review File Server issues in Oracle Integration.

Topics:
• Copying Issue Encountered Using WinSCP
• File Names Limited to 924 Characters
• Data Removed from Files During Simultaneous Updates
• Read-Only Users Can Delete Files Using WinSCP

Copying Issue Encountered Using WinSCP

An issue was encountered when copying files to File Server when using the WinSCP client,
where a zero byte file with the same file name was created.
The workaround is to use another SFTP client or delete zero byte file.

File Names Limited to 924 Characters

If a file name in File Server exceeds 924 characters, a file system error gets logged in File
Server.

Data Removed from Files During Simultaneous Updates

When one or more integrations attempt to update the same file by appending data to it, all data
in the file is sometimes removed.
The issue occurs when the integrations attempt to update the file in parallel, leading to multiple
integrations changing the file simultaneously. The data removal from the file then can cause
one or more integrations to fail because the integrations expect the file to contain data.
The workaround is to update your integrations so that they do not update the same file by
appending data to it in parallel. As a best practice, Oracle recommends avoiding simultaneous
operations on the same file.

Read-Only Users Can Delete Files Using WinSCP

A person who has read-only permissions for a directory can edit and delete files in that
directory when working with File Server from WinSCP version 5.x.
The workaround is to use a different supported SFTP client or the command line SFTP.

4-1
5
Visual Builder Issues
Visual Builder issues in Oracle Integration.

Topics:
• Unsupported Features
• Supported Browsers
• Upgrade Policy
• Known Issues

Unsupported Features
Some Visual Builder features are not supported in Visual Builder service instances enabled in
Oracle Integration 3.

Feature Description
VB instance as a private endpoint It is not currently possible to provision a Visual
Builder instance as a private endpoint.
Processes in Visual Builder The following Process-related features are not
supported:
• Register deployed processes
• Use of Process Actions in Action Chains
• Support for Process code snippets
• Process-related Quick Starts
Instead, you can leverage service connections to
interact with OCI Process Automation. See
Connect to Oracle Cloud Infrastructure Process
Automation APIs.
Start or stop a Visual Builder instance in the OCI Once enabled in Oracle Integration 3, you cannot
Console stop or start a Visual Builder instance.
Move a Visual Builder instance to another This is not supported for Visual Builder instances.
compartment
Delete a Visual Builder instance This is not supported for Visual Builder instances.
Change the node count This is not supported for Visual Builder instances.

Supported Browsers
Oracle Visual Builder supports the latest version of the Chrome browser running on Mac OS X
and Windows. Other browsers and platforms are not supported.
Applications created using Visual Builder can run on any browser supported by Oracle JET. For
details, see What platforms are supported by Oracle JET?
JavaScript must be enabled for all browsers.

5-1
 Chapter 5
Upgrade Policy

Upgrade Policy
When you create a new visual app, Visual Builder automatically sets your runtime
dependencies to the latest Visual Builder Runtime and JET versions. If you’ve already staged
or published an app, however, it’s up to you to decide when to upgrade, as long as you do so
within a certain time period.
As a general rule, you can run a published Visual Builder application built on the current
runtime version, and continue running it on the three previous versions—but new Visual
Builder runtime libraries are released with new versions of the Visual Builder Studio design
time (around four times a year). The Visual Builder design time is only updated twice a year, so
it gets only two of those four versions (another reason we recommend using Visual Builder
Studio as your design environment). As a result, you need to upgrade every other release in
Visual Builder, while in Visual Builder Studio, you upgrade after four releases, with the design
time supporting the last three versions.
So if you built your app in 24.10 (for example), Visual Builder supports the app not only on the
24.10 runtime version, but also on 25.01, 25.04, and 25.07. Once 25.10 comes out, however,
support for the 24.10 runtime version will drop off, so we'll ask you to upgrade your app before
you can work on it in the Designer. If you choose not to upgrade at that time, you run the risk
that newer browser versions will break your app. You also won’t be able to take advantage of
any important security and performance improvements. For all of these reasons, we encourage
you to build time into your development cycle to keep abreast of current changes, and to make
sure you upgrade your app (you should version it first) before support for your current runtime
version expires.

Known Issues
Known issues associated with this release of Visual Builder.

Known Issues
• Known Issues in Service Connections
• Known Issues in Business Objects
• Known Issues in the Page Designer
• Known Issues in Creating and Building Projects
• Known Issues for Live/Staged Apps Post-Upgrade to Oracle Integration 3

Known Issues in Service Connections

The following issues might affect the behavior of service connections in your applications.

Known Issues
• Invoking OIC REST API from Service Connection returns 404 error
• Authentication failing on OIC service connections
• Integration Applications not listed in Service Catalog
• Error testing connection to IDCS REST APIs with OAuth User Assertion Authentication
type
• Create service connection wizards ignore secure header setting

5-2
 Chapter 5
Known Issues

• Integration endpoint not listed in catalog

• Error creating service connection to Integration Applications from catalog
• CORS error when connecting to Oracle Integration
• Service connection using self-signed certificate not working

Invoking OIC REST API from Service Connection returns 404 error
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.

Authentication failing on OIC service connections

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.

5-3
 Chapter 5
Known Issues

Tip:
To determine whether your Integration is an openAPI-based integration, check the
integration's metadata page (which may look something like https://
OIC_instance/ic/api/integration/v1/flows/rest/ECHO/1.0/metadata/), which
will have swagger and openAPI metadata URLs.

Integration Applications not listed in Service Catalog

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.

Error testing connection to IDCS REST APIs with OAuth User Assertion
Authentication type
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.

5-4
 Chapter 5
Known Issues

Create service connection wizards ignore secure header setting

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.

Integration endpoint not listed in catalog

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.

5-5
 Chapter 5
Known Issues

Error creating service connection to Integration Applications from catalog

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.

CORS error when connecting to Oracle Integration

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.

Service connection using self-signed certificate not working

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.

Known Issues in Business Objects

You might encounter the following issues when working with business objects in your
applications.

Known Issues
• New business objects not selected in Business Object Resource Editor
• Problems when saving business object diagram as image
• Creating new record using REST API results in empty response

New business objects not selected in Business Object Resource Editor

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.

5-6
 Chapter 5
Known Issues

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.

Problems when saving business object diagram as image

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.

Creating new record using REST API results in empty response

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.

5-7
 Chapter 5
Known Issues

Known Issues in the Page Designer

You might encounter the following issues when working with the Page Designer.

Known Issues
• Component not loading in page after upgrading application
• Filter field populated with cached data

Component not loading in page after upgrading application

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.
ADP data in a JSON file needs to be assigned a valid JSON value. ADP data that is assigned
a value from the result of a previous action (for example, a call module action or REST action),
must also be valid JSON. When a non-JSON value (such as JavaScript values like NaN or
Infinity) is provided, you should choose the correct JSON value that should be used and then
replace it.
Visual Builder upgrade tools might not be equipped to correctly upgrade the application when
invalid JSON is present.
The workaround is to ensure that all values in JSON files are valid JSON.

Filter field populated with cached 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.

Known Issues in Creating and Building Projects

You might encounter the following issues when creating and building Visual Builder projects.

Known Issues
• Staging PWA app fails in government realm
• Update deprecated Oracle SaaS application template theme
• Cannot switch theme in application settings
• Error when creating new version of application

5-8
 Chapter 5
Known Issues

• Camera component no longer offers camera capture option on Chrome browser on

Android 14
• Loading JSON using Text module stops Persistence Toolkit working
• Error 502 Bad Gateway when deploying visual app

Staging PWA app fails in government realm

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

Update deprecated Oracle SaaS application template theme

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.

Cannot switch theme in application settings

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.

Error when creating new version of application

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.

5-9
 Chapter 5
Known Issues

Camera component no longer offers camera capture option on Chrome browser on

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

Loading JSON using Text module stops Persistence Toolkit working

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.

Error 502 Bad Gateway when deploying visual app

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.

5-10
 Chapter 5
Known Issues

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.

Known Issues for Live/Staged Apps Post-Upgrade to Oracle Integration 3

The following issues might result in live or staged apps not working correctly after upgrading to
Oracle Integration 3.
For details about the tasks you need to perform before and after upgrading to Oracle
Integration 3, see Upgrade from Oracle Integration Generation 2 to Oracle Integration 3.

Known Issues
• Cannot access non-catalog Integration REST APIs in app
• Visual Builder apps on obsolete VB runtime versions
• Unable to access VB business object URLs from service connections in live app
• Custom code accessing pre-upgrade Visual Builder URL failing
• PWA app no longer receives updates automatically after upgrade to Oracle Integration 3

Cannot access non-catalog Integration REST APIs in app

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:
a. 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).
b. 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

5-11
 Chapter 5
Known Issues

instance). If you use a build pipeline, you would need to modify the parameter in the
packaging jobs.

Visual Builder apps on obsolete VB runtime versions

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.

Unable to access VB business object URLs from service connections in live app
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.

Custom code accessing pre-upgrade Visual Builder URL failing

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 app no longer receives updates automatically after upgrade to Oracle

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

5-12