8 Desupported in Previous Releases

The following section lists features that were desupported in a previous release.

If a desupported feature has to do with application metadata or APIs, then existing applications may not work as they did previously. Oracle recommends modifying the application to replace the feature.

8.1 Desupported APIs

As of APEX 24.2, the following APIs are desupported:
  • apex_javascript.add_3rd_party_library_file
  • apex_css.add_3rd_party_library_file

8.2 Public Dictionary View Changes

As of APEX 24.2, columns attribute_01 through attribute_25 now return null in the following views:
  • apex_application_page_items
  • apex_appl_page_ig_columns
  • apex_appl_plugin_settings
  • apex_appl_page_filters
You can query this attributes by reading the attribute's JSON column.

8.3 TinyMCE-based Rich Text Editor Desupported

In APEX 24.1, the Rich Text Editor page item based on the TinyMCE library was deprecated.

As of APEX 24.2, TinyMCE is desupported and the Rich Text Editor page item no longer supports the TinyMCE library. The underlying library is now Oracle Rich Text Library (ORTL). Any Rich Text Editor page items still using TinyMCE are auto-migrated to ORTL. Any custom Initialization JavaScript Function code is commented out.

8.4 CSSO Desupported

As of APEX 24.2, the CSSO 3rd party JavaScript library is removed and replaced with a basic minification logic. This may impact existing CSS static files.

8.5 Removed JSON Application Export

As of APEX 24.1, the JSON application export option is removed. The Export Readable Format option is now a switch. If off, the application exports in SQL form. If on, the export file contains a human-readable YAML version of the application metadata.

8.6 CKEditor Desupported

As of APEX 23.2.9, CKEditor 4 and CKEditor5 are desupported. Any custom code using CKEditor5 APIs must be re-worked. Any code referencing CKEditor4 and the CKEDITOR global object no longer works. Any existing CKEditor regions default to using Oracle Rich Text Library.

8.7 Desupported Utilities

As of APEX 23.2, the APEXExport utility is desupported and is no longer included with Oracle APEX. Oracle recommends using SQLcl to perform export operations.

8.8 Querying Template Component Metadata

As of APEX 23.2, for template components only, the ATTRIBUTE_01...ATTRIBUTE_25 columns of APEX_APPLICATION_PAGE_REGIONS and APEX_APPLICATION_PAGE_IR_COL public views now return null.

Instead, use the new ATTRIBUTES column that stores a JSON object of all attribute values. Use the attribute's Static ID as the object key. Note that a table alias is always needed when using the JSON dot notation. For example:
select r.attributes.COLOR
  from apex_application_page_regions r
 where r.application_id = 100
   and r.page_id        = 1
   and r.static_id      = 'user_badge';