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.

When on an upgraded APEX 24.1 instance using ORDS version 24.1.0, if you click the link from APEX App Builder to SQL Developer Web, an error message ("Method Not Allowed") appears.

This bug is fixed in ORDS version 24.1.2.

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.

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

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.

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.

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

If your application relies on removed 1.x jQuery APIs, that functionality no longer works as of Application Express release 18.1. You must update the JavaScript to only use jQuery 3.5 or later APIs. See the jQuery migration guides to learn more:

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

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

Solution

Reduce the amount of DML rows.

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.