As of APEX 24.1, the APEX Dynamic Action event "Page Unload" is deprecated because the underlying browser event unload is deprecated. For more information, see Window: unload event.

As of APEX 24.1, when editing a region plug-in, the Substitute Attribute Values switch is now deprecated. When you move to the Procedure interface, this switch disappears. To perform substitutions on the attribute value, use apex_plugin_util.replace_substitutions.

As of APEX 24.1, dynamic substitutions for Min/Max Value attributes for the Number field page item, including &P1_MIN., are deprecated. This will be fixed in a future release by allowing developers to declaratively pick an item to use for Min/Max Value attributes.

Deprecated Settings

Deprecated Directives

As of APEX 23.1, APEX prevents double escaping of LOV display values.

By default, APEX automatically HTML-escapes Lists of Values (LOV) display values as necessary. To ensure backward compatibility with legacy apps, APEX checks whether the LOV query already includes a utility function to escape the display value. If it does, APEX avoids double-escaping the value when displaying it in a Select List, Popup LOV, Shuttle, Display Only item, or similar components.

Oracle recommends removing redundant inline escaping calls from your LOVs. In a future version of APEX, this prevention mechanism may be removed, which could cause some display values to appear double-escaped.

select *
  from apex_application_lovs
 where lov_type = 'Dynamic'
   and (   upper(list_of_values_query) like '%HTF.ESCAPE_SC%'
        or upper(list_of_values_query) like '%APEX_ESCAPE.HTML%'
        or upper(list_of_values_query) like '%WWV_FLOW_ESCAPE.HTML%' );

select *
  from apex_application_page_items
 where lov_named_lov is null
   and (   upper(lov_definition) like '%HTF.ESCAPE_SC%'
       or upper(lov_definition) like '%APEX_ESCAPE.HTML%'
       or upper(lov_definition) like '%WWV_FLOW_ESCAPE.HTML%' );

If the queries returns no rows, then no action is required. Otherwise, check the LOV definition and/or page items, remove any manual escaping, and test your applications to ensure that the values still appear as intended.

As of APEX 23.1, Format HTML sanitizes the HTML content on the client before displaying it. This simplifies the display of user-provided HTML, including the content of HTML-based rich text editors.

To maintain backward compatibility with existing applications, all current Display Only page items using the Format HTML option will be migrated to HTML (Unsafe) to preserve their current behavior. However, going forward, this option is deprecated, and displaying "unsafe" HTML, such as script tags or javascript: expressions, onclick attributes, and others, is no longer possible, as this content is stripped away.

Although it is not recommended to display unsafe HTML content, you can still choose to display it.

Future releases of APEX may include fixes and improvements to the accessibility, usability, and functionality of various items that require changing the markup or using custom elements (web components). These changes may create more dynamic behaviors for items, and will be done in a way that minimizes impact to items and forms in existing apps.

As of APEX 22.2, the apex.item namespace and item interface are the only supported APIs for customizing and programmatically working with items. APEX discourages customizations that rely on undocumented item markup or CSS classes, as these may not work as expected in future releases.

Assumptions about the HTML markup used by each of the native APEX items may not hold in the future. Item customization through Advanced attributes (CSS Classes), Custom Attributes, JavaScript code, and CSS rules that assumes particular markup could break.

.important-text.apex-item-textarea + .apex-item-textarea-counter { 
    font-weight: bold;
}

Future releases may document new custom element markup, classes, and CSS variables to allow more supportable customization.

As of APEX 22.2, jQuery Date Picker is now deprecated and cannot be used for new pages or applications. The old jQuery Date Picker JavaScript APIs are not supported.

Oracle recommends replacing all old Date Pickers with the new Date Picker.

As of APEX 22.1, the APEX_IR.GET_REPORT API is deprecated. Instead, use APEX_REGION.OPEN_QUERY_CONTEXT to get interactive report data.

As of APEX 22.1, SOAP style Web Service references and legacy support for REST style Web Services references are deprecated.

As of APEX 20.1, jQuery UI is deprecated. Oracle recommends that customers update third-party APEX plug-ins and custom JavaScript code to remove any jQuery UI references. Native APEX components that use jQuery UI will continue to function, but support will be removed in a future release.

Oracle ships a custom bundle of JQuery UI 1.13.2 that includes only the modules that APEX needs. Oracle no longer ships individual widgets or any jQuery UI CSS files.