Oracle APEX

Known Issues - APEX 19.1

APEX 19.1.0.00.15 was released on March 29, 2019.

Please review the Release Notes for significant issues known at time of release. Any new significant issues will be added here. This page was last updated on May 13, 2019.

Note: Review the APEX 18.1 and above Known Issues Addendum for important information regarding flash charts.

  • N/A - INSTALLATION SCRIPT FOR APPLICATION CONTAINERS
    The PSE bundle for APEX 19.1 contains a new installation script, catpatch_appcon.sql. This script is used to patch APEX installations in an application container, a new installation option in APEX 19.1. The advantage of this installation option is that you only have to run this patch script once against the application container root, and then application PDBs can apply the PSE bundle when they are ready. To use the catpatch_appcon.sql script:
    1. Connect to the application container root as SYSDBA.
    2. Run catpatch_appcon.sql.
    To apply the PSE bundle to an application PDB:
    1. Connect to the application PDB as SYSDBA.
    2. Execute the following commands:
        alter pluggable database application APEX sync;
        begin
          sys.dbms_utility.compile_schema( 'APEX_190100', false );
          sys.dbms_utility.compile_schema( 'FLOWS_FILES', false );
        end;
    Solution: A PSE has been made available for this issue on MyOracleSupport.
    Navigate to Patches & Updates and search for patch number 29369869.
    Note: this PSE also contains other bug fixes, please review the README in the patch for more details.
  • 29765107 - APEX_JSON.WRITE(XMLTYPE): ENQUOTE IF NUMERIC VALUE ENDS WITH NEWLINE
    If you are using APEX_JSON.WRITE with XMLTYPE or nested a SYS_REFCURSOR and the data contains numeric values followed by newline, invalid JSON is generated.
    Solution: A PSE has been made available for this issue on MyOracleSupport.
    Navigate to Patches & Updates and search for patch number 29369869.
    Note: this PSE also contains other bug fixes, please review the README in the patch for more details.
  • 29705177 - WIZARDS DO NOT CREATE FORM REGION CORRECTLY IF "TABLE" IS SPECIFIED AND UI DEFAULTS EXIST
    When a new form region is created on top of a table (not SQL Query) using the Create App or Create Page wizards - and UI Defaults exist for that table, the form region is not created correctly.
    Solution: A PSE has been made available for this issue on MyOracleSupport.
    Navigate to Patches & Updates and search for patch number 29369869.
    Note: this PSE also contains other bug fixes, please review the README in the patch for more details.
  • 29645898 - FORM REGION WITH CONDITIONAL ITEMS CAN THROW CHECKSUM ERROR ON DML UPDATE OR DELETE ACTION
    A Form Region contains Conditional Page Items and the page item condition references another page item from the same form region. Executing form DML can fail with a Checksum Error, although the table row has not been changed.
    Solution: A PSE has been made available for this issue on MyOracleSupport.
    Navigate to Patches & Updates and search for patch number 29369869.
    Note: this PSE also contains other bug fixes, please review the README in the patch for more details. Workaround: Alternatively, Use Dynamic Actions to show or hide the conditional page items instead of using a server-side condition.
  • 29645950 - WEB SRC MODULE DML DOES NOT TAKE MODULE OR OPERATION PARAMETERS INTO ACCOUNT
    If a form is being created on top of a Web Source Module - and the Web Source module (or one of its operations) have parameters defined, then these are correctly take into account.
    Solution: A PSE has been made available for this issue on MyOracleSupport.
    Navigate to Patches & Updates and search for patch number 29369869.
    Note: this PSE also contains other bug fixes, please review the README in the patch for more details.
  • 29633683 - APEX_EXPORT: IN SPLIT MODE, MULTIPLE APPLICATION_PROCESSES.SQL FILES
    When using APEX Export in split mode, there is only one file for application processes, containing just the last one.
    Solution: A PSE has been made available for this issue on MyOracleSupport.
    Navigate to Patches & Updates and search for patch number 29369869.
    Note: this PSE also contains other bug fixes, please review the README in the patch for more details.
  • 29612553 - FORM REGION DML PROCESS THROWS INTERNAL ERROR WHEN INTERACTIVE GRID DML PROCESS IS ON THE SAME PAGE
    If a page contains a Form Region and an Interactive Grid Region; and there is both a Form - Automated Row Processing (DML) as well as an Interactive Grid - Automated Row Processing (DML) process, then the form region process can fail with an APEX "Internal Error" message.
    Solution: A PSE has been made available for this issue on MyOracleSupport.
    Navigate to Patches & Updates and search for patch number 29369869.
    Note: this PSE also contains other bug fixes, please review the README in the patch for more details.
  • 29614358 - ERRORS ON SAMPLE DATABASE APP PAGE 29 ("ORDER DETAILS")
    Page 29 ("Order Details") of the Sample Database Application throws errors when the end user makes changes to the Order Items Interactive Grid.
    Workaround:
    1. Apply Patch Set Bundle - Navigate to Patches & Updates and search for patch number 29369869.
    2. Change Item P29_ORDER_TOTAL by changing the "Query Only" attribute in the "Source" section and set to "Yes"
    3. Change Interactive Grid Region "Order Items" and add P29_ORDER_ID as Page Items To Submit
  • 29601369 - TIME PICKER DOES NOT INITIALIZE SYSDATE HOURS AND MINUTES CORRECTLY WHEN ITEM OR IG COLUMN VALUE IS EMPTY
    When a date picker item uses hour and minute components in the format mask - and the actual item value (or IG column value) is empty (NULL), it is supposed to initialize with the current datetime (sysdate). However, this does not happen correctly for NULL values, when the current datetime hour or minute values are below 10. This is independent from any locale setting.
    Workaround: Provide a default value (e.g. sysdate) for the page item or Interactive Grid column. APEX will then initialize the page item or IG column with the default value - and the date picker will correctly initialize from that value.
  • 29552515 - INTERACTIVE GRID IE11 CELLS EDITED IN POPUP WHEN SHOULD BE INLINE
    Editing a cell in an Interactive Grid when running in an Internet Explorer 11 browser uses a floating popup even when it should fit in the cell. Editing is still functional.
    Workaround: There is currently no workaround.
  • 29539622 - INTERACTIVE REPORT FILTER DIALOG STYLE ISSUES FOR THEME 26
    Apps using theme 26 containing Interactive Reports have style issues in the Filter dialog. Specifically the 'Row' type of filter, where in the dialog the Columns multi-select showing column identifiers and names overlap each other and make the text illegible.
    Workaround: Add the following CSS snippet to your APEX page, in Page Attributes > CSS > Inline:
      table.calculator td.w120 { height: 20px; width:100%; }
      table.calculator td.w20 { height: 20px; width:20px; }
      table.calculator td.w40 { height: 20px ;width:40px; }

Changed Behavior:

  • N/A - FLASH CHARTS AND GANTT CHARTS NO LONGER DISPLAY
    Starting with Oracle Application Express 5.1.4 and continuing with later releases, the AnyChart and AnyGantt flash .swf files have been removed from the /images folder. This will result in your map chart and gantt charts no longer rendering. No error message will be displayed, instead the region will be blank.
    Solution: To install the AnyChart Flash Content in your instance, download the zip file, unzip the contents and follow the instructions outlined in the README.txt file, to update your images folder.
    Workaround: Please see the Addendum for more details.
  • N/A - JQUERY AND JQUERY UI UPGRADE
    Oracle APEX 19.1 includes jQuery 3.3.1, which breaks compatibility with earlier 2.x versions. If your application relies on removed 2.x, or 1.x jQuery functionality, then this functionality will no longer work.
    Workaround: 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 will no longer work, and you must update the JavaScript to only use jQuery 3.1 APIs.
    Review the jQuery migration guides to learn more: For further information including information about the jQuery UI upgrade, please review section 9.1.3 Known Issues for jQuery and jQuery UI in the release notes.
Downloads