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.

• Desupported Query Builder
  
• Desupported User Interfaces Removed
  
• Desupported JET Date Picker Item Type Migrated
  
• DOM Object Desupported
  
• Legacy Bulk Utilities Desupported
  
• Desupported Attributes in App Builder
  
• Desupported Properties
  
• Desupported View Columns
  
• FullCalendar 3 Desupported
  
• App Builder Defaults Desupported
  
• Copying Legacy Themes Desupported
  
• CKEditor4 Desupported
  
• Desupported Public Package APIs
  
• Desupported Page Positions
  
• Desupported Region Positions
  
• Custom Page Region Templates with Duplicated Positions Desupported
  
• Legacy Substitution Strings Desupported
  
• Desupported JavaScript Functions
  
• Post Calculation for Page Items Desupported
  
• Show / Hide All Page Items On Same Line Attributes Desupported
  
• apex.server Plug-in and Process Function Async Option Desupported
  
• apex.widget.initPageItem Function Desupported
  
• Popup LOV Template Desupported
  
• Based On - Output of PL/SQL Code attribute Desupported
  
• Syntax {COLUMN_NAME}_LABEL in Interactive Grid Icon and Detail Views Desupported
  
• Removed Content Delivery Network
  
• APEX-Based REST Services Desupported
  

8.1 Desupported Query Builder

SQL Workshop Query Builder is now desupported, and will be removed in a future release.

8.2 Desupported User Interfaces Removed

APEX previously defined multiple users interfaces for each application. This is no longer the case. Desupported user interfaces are cleaned up, which impacts many APEX Dictionary Views:

• Obsolete views:
  • apex_workspace_ui_types
  • apex_appl_user_interfaces
• New view columns:
  • apex_applications.theme_style_by_user_pref
  • apex_applications.built_with_love
  • apex_applications.navigation_list
  • apex_applications.navigation_list_position
  • apex_applications.nav_bar_type
  • apex_applications.nav_bar_list
  • apex_applications.include_legacy_javascript
  • apex_applications.include_jquery_migrate
• Obsolete view columns:
  • apex_applications.ui_detection_css_urls
  • apex_appl_concatenated_files.user_interface_id
  • apex_application_pages.user_interface_id
  • apex_application_pages.page_transition
  • apex_application_pages.popup_transition
  • apex_application_themes.ui_type_id
  • apex_application_themes.ui_type_name
  • apex_application_themes.default_page_transition
  • apex_application_themes.default_popup_transition
  • apex_appl_plugins.supported_ui_types
  • apex_appl_plugin_std_attrs.supported_ui_types
  • apex_appl_plugin_attributes.supported_ui_types
• Removed Page Designer Properties:
  • Page Transition
  • Popup Transition
  • User Interface

Older applications created when APEX could have two User Interfaces now only use the active user interface. Inactive user interfaces are removed from the metadata.

8.3 Desupported JET Date Picker Item Type Migrated

The Date Picker (JET) item type is now removed. Existing page items and interactive grid columns are automatically migrated to the new Date Picker item type introduced in APEX 22.2.

This impacts any JavaScript customizations made for the JET Date Picker component.

8.4 DOM Object Desupported

The DOM Object Dynamic Action selector type is desupported. Any page that uses this type for an action now throws an exception in the browser console, and the action does not execute.

Use the JavaScript Expression type instead of DOM Object.

8.5 Legacy Bulk Utilities Desupported

The Grid Edit tools are now desupported. This includes grid edit tools available in:

• Cross Page Utilities
• Region Utilities
• Button Utilities
• Item Utilities
• Computation Utilities
• Validation Utilities
• Process Utilities
• Dynamic Action Utilities
• Branch Utilities

You can edit items individually through Page Designer, or view them in bulk through the appropriate Utility area.

8.6 Desupported Attributes in App Builder

The following attributes in App Builder are desupported:

• In Edit Application Definition:
  • Progressive Web App - Icon URL
  • Application Icon - Icon File Name
• In Edit User Interface:
  • Favicon

8.7 Desupported Properties

The following properties in the property editor are desupported:

• Region Image
• Image Tag Attributes

8.8 Desupported View Columns

The following view columns are desupported:

• In apex_applications:
  • app_builder_icon_name
  • favicons
  • pwa_manifest_icon_url

8.9 FullCalendar 3 Desupported

FullCalendar v3 is desupported, including:

• deprecated plug-in attributes
• files and folders specific to v3 or jquery-fullcalendar
• v3-specific logic in PL/SQL and JavaScript

The used library version is now FullCalendar 6.1.8. APEX upgrades the library automatically.

8.10 App Builder Defaults Desupported

Developers can no longer define App Builder Defaults from Workspace Utilities, App Builder Defaults. The Create Application Wizard no longer uses the defined attributes.

8.11 Copying Legacy Themes Desupported

The Copy Theme Wizard no longer supports copying legacy themes. This includes Themes 1 - 26, and the jQuery Mobile theme.

8.12 CKEditor4 Desupported

Rich Text Editor items based on CKEditor4, which are marked as deprecated since APEX 20.2, are now desupported and will be automatically converted to CKEditor5. CKEditor4 is removed from APEX completely.

Converted items receive the following configuration:

• Format: HTML
• Toolbar: unchanged
• Toolbar Style: Multiline
• Minimum Height: 180
• Maximum Height: null
• Allow Custom HTML: Enabled

The properties Toolbar Position and Skin do not have a CKEditor5 equivalent, and are removed. Any code included in the JavaScript Initialization Code attribute is automatically commented out.

Oracle recommends manually checking the functioning of each Rich Text Editor item.

Note:

With this update, any code referencing CKEditor4 and the CKEDITOR global object no longer works.

8.13 Desupported Public Package APIs

Desupported public package APIs:

• apex_page.is_desktop_ui function
• apex_page.get_ui_type function

8.14 Desupported Page Positions

The following page positions are desupported and display as Legacy in Page Designer:

• Body 1
• Body 2
• Body 3
• After Header
• Before Footer

8.15 Desupported Region Positions

The following region positions used for button positioning are desupported and display as Legacy in Page Designer:

• Top of Region
• Bottom of Region
• Above Region
• Below Region

8.16 Custom Page Region Templates with Duplicated Positions Desupported

Custom page template and custom region templates with duplicated positions are desupported. For example, a region template referencing position #CHANGE# twice is not recommended because that duplicate position causes duplicate DOM IDs.

8.17 Legacy Substitution Strings Desupported

The following apex.env substitution strings are desupported:

• APP_IMAGES
• IMAGE_PREFIX
• THEME_DB_IMAGES
• THEME_IMAGES
• WORKSPACE_IMAGES

While the legacy substitutions still function, Oracle recommends developers update their environments to use updated substitutions (listed below).

Legacy	New
IMAGE_PREFIX	APEX_FILES
WORKSPACE_IMAGES	WORKSPACE_FILES
APP_IMAGES	APP_FILES
THEME_IMAGES	THEME_FILES
THEME_DB_IMAGES	THEME_DB_FILES

8.18 Desupported JavaScript Functions

The following functions are desupported:

Universal Theme JavaScript API function:

• apex.theme42.util.mq (use apex.theme.mq instead)

8.19 Post Calculation for Page Items Desupported

The Post Calculation functionality of page items is desupported.

This functionality remains for existing page items where it has been used, but you can no longer set it for new page items nor add it to existing page items where it has not been used in the past.

8.20 Show / Hide All Page Items On Same Line Attributes Desupported

In Dynamic Actions, the Show and Hide actions have attributes Show all page items on same line and Hide all page items on same line, respectively. These attributes were designed for forms with a table-based layout. Because Universal Theme no longer uses table-based layout, these attributes are desupported.

This functionality remains for existing Dynamic Actions where it was set to Yes, but developers cannot select it for new Dynamic Actions.

8.21 apex.server Plug-in and Process Function Async Option Desupported

In a future release, the async option will be ignored and all Ajax requests will be asynchronous.

8.22 apex.widget.initPageItem Function Desupported

The function apex.widget.initPageItem is desupported. Item plug-in creators should use apex.item.create instead.

8.23 Popup LOV Template Desupported

The Popup LOV template type is desupported.

8.24 Based On - Output of PL/SQL Code attribute Desupported

The selection Output of PL/SQL Code of the attribute Based On is now desupported.

8.25 Syntax {COLUMN_NAME}_LABEL in Interactive Grid Icon and Detail Views Desupported

The &{COLUMN_NAME}_LABEL. syntax, which is used to reference the column label in Interactive Grid Detail and Icon views, is desupported.

Instead, use &{COLUMN_NAME}%LABEL..

8.26 Removed Content Delivery Network

The attribute Content Delivery Network that could be found under User Interface Attributes, Javascript with options None, Google, Microsoft, and jQuery, has been removed. Enabling this option was only relevant for pulling in a few of the JavaScript libraries that APEX needs.

If you were using this option, it's recommended to instead use the more modern, Oracle-provided CDN approach. For further information, see Announcing Oracle APEX Static Resources on Content Delivery Network.

8.27 APEX-Based REST Services Desupported

APEX-based REST Services are desupported. Prior to release 18.1, definitions of RESTful services created within Oracle APEX were stored within the metadata tables of the core APEX schema, and referred to as APEX-based REST Services. With release 18.1, we introduced support for Oracle REST Data Services (ORDS) -based REST Services, where definitions are stored in the ORDS repository. ORDS-based REST Services continue to be supported for definitions of RESTful Services in Oracle APEX.

The instance parameter APEX_REST_PATH-PREFIX is desupported.

Note:

Oracle REST Data Services (ORDS) release 21.4.2 and newer now ship with migration scripts that enable you to upgrade any remaining APEX-based REST Services to ORDS-based Services. To learn more, see Migration of Oracle APEX Restful Service Modules in Oracle REST Data Services Release Notes.