Open Bugs and Known Issues

This section describes bugs and known issues for Oracle APEX release 26.2.

Tip:

This section is current as of the writing of this document. To view the most current listing of changed behavior, go to the Known Issues page:

https://www.oracle.com/tools/downloads/apex-downloads/apex-262-known-issues/

Alternatively, you can view the Accessibility Conformance Report (ACR). The ACR includes details of all known issues with APEX. A single release of APEX uses multiple component ACRs for specific areas of the product (for example, “Development Environment”, “Components”, “Documentation”, etc.) Please go to Accessibility ACRs | Oracle’s Accessibility Program to find the ACRs for Oracle APEX.

Known Issues for Importing APEXlang Applications in App Builder

Post-installation Credentials and Remote Servers

After successful APEXlang app import, in this release, no convenience page appears to configure “Prompt on Install” Web Credentials or Remote Servers. To adjust them if necessary, use the corresponding edit page in Workspace Utilities.

Tip: The preinstallation step is not required when importing through the App Builder UI. The import wizard includes a dedicated step that makes this configuration easy. Manual preinstallation is only required when importing APEXlang applications through other clients, such as SQLcl.

Known Issues for Working Copy Feature

The known issues for the working copy feature are:

Known Issues for ACL Roles

After creating a role, change the automatically-generated lowercase static ID to uppercase. This ensures apex_acl.user_has_role evaluates correctly.

Known Issue with Refreshing a Master Theme

There is a known issue with refreshing a master theme in the following scenario:

  1. The master theme is subscribed to the Universal Theme in the central application.

  2. There is a child theme that subscribes to the master theme.

  3. There is an app that uses the child theme and has template component regions in the app.

An example of the error is:

Theme Switch failed.
Cannot Switch Template Component "Badge". Custom Attribute "Label" is required in Theme 42.

To fix this error, navigate to the template component and modify the attributes so that the required attributes are no longer missing.

Known Issue with Bot Traffic Protection

The new Allow Bot Access attribute will let developers control whether ORDS should block bots/web crawlers from accessing the application. Bot traffic will be blocked by default for new and internal applications. Support for this attribute will be delivered in a future release of ORDS.

Known Issues with Using BOSS REST Services

Total Results Only Works with Search Views

BOSS support for total results currently only works on search views.

Error Defining REST Data Source Against OAuth-Protected BOSS Endpoint in RDBMS 19c

If your APEX is running in an Oracle 19c database, then when initially defining a REST Data Source against an OAuth-secured BOSS endpoint, you may encounter an HTTP 401 Not Authorized error when discovering the service. The error text returned could indicate Anonymous Access is not allowed for OpenApi Service.

The solution is to use the fully-qualified BOSS endpoint URL including both the optional language path segment (for example, $en) and an explicit deployment id after the version path segment. For example, instead of referencing .../v1/exampleobject you would use .../v1:99/$en/exampleobject during discovery. Once the REST Data Source is created, you can edit its service URL to remove the language path segment and the explicit deployment id.

Known Issue for Sublists

Currently, sublist entries are not included in list search results when the list search configuration is defined on the list referencing the sublist. This will be fixed in a future release.

Known Issue with Confirm or Alert Dynamic Action Messages When Upgrading

Issue

When upgrading from APEX 21.2 or earlier, the text in existing Confirm or Alert dynamic action messages may be truncated if it is too long, leading to data loss. This is due to APEX HTML-escaping messages, which may increase their size past the 4000-byte limit.

Resolution

Prior to upgrading, run a query to check whether any messages are affected:

select *
    from apex_application_page_da_acts
where action_name in ('Alert', 'Confirm')
    and ( lengthb( attribute_01 )
        + ( 4 * nvl( regexp_count( attribute_01, '&|"|<|>' ), 0 ) )
        ) > 4000;

If the query does not return any rows, proceed with the upgrade.

If the query does return rows, convert the affected rows into application text messages and reference them with substitution syntax before proceeding with the upgrade.

Known Issue using “Source Display” region type plug-in in previously installed Sample Apps

Issue

The Source Display region type plug-in that is used in a Sample App installed in a previous release of APEX no longer works. This issue is due to the removal of views associated with AnyChart charts and AnyMap map charts.

Resolution

  1. Open the application to edit it.

  2. Navigate to Shared Components, under Other Components select Plug-ins, and Source Display.

  3. Update the PL/SQL Code to remove the following lines of code (lines 35 - 48):

    union all
select reg.source_type, fs.series_seq, fs.series_name, fs.series_query source
from apex_application_page_regions reg,
    apex_application_page_flash5_s fs
where reg.application_id = :APP_ID
    and reg.page_id = :APP_PAGE_ID
    and reg.static_id = d_region_static_id
    and fs.application_id = reg.application_id
    and fs.page_id = reg.page_id
    and fs.region_id = reg.region_id
    and reg.source_type in (
        'Flash Chart',
        'Map'
    )

  4. Click Apply Changes.

Known Issues for jQuery Upgrade

jQuery 3.x breaks compatibility with earlier 2.x versions. For applications that still rely on removed 2.x functionality, you can use the jQuery Migrate plug-in (to include this plug-in, set the Desktop User Interface Details attribute Include jQuery Migrate to Yes).

To migrate from 2.x to 3.5.x see https://jquery.com/upgrade-guide/3.5/

Interactive Grid support for REST Enabled SQL

Issue

Oracle REST Data Services (ORDS) REST Enabled SQL has a limit of 1000 bind variables in a REST Enabled SQL request. As a result, when Interactive Grid DML sends more than 1000 column values, the following error displays: “Internal ORDS OUT Bind limits exceeded.”

Resolution

Reduce the amount of DML rows.

Group By Component Type mode prevents Default View

Issue

Due to the removal of “Sort by Processing Order” and “Group by Component Type” from Page Designer, developers may be stuck in “Group by Component Type” mode without a way to switch back to the default view (“Sort by Processing Order”).

Resolution

  1. In Page Designer, open Developer Console in the browser, and run the following command:

    pageDesigner.saveBoolPref( "GROUP_BY_COMPONENT_TYPE", true );

  2. Refresh the page.

Known Issues for Data Generator

There are known issues with the API for the data generator:

These issues will be fixed in a future release.