Oracle Application Express 4.2.1

Known Issues

Application Express 4.2.1 was released on December 14, 2012.

This page was last updated on 10-January-2013.

  • 16030411 - APPLICATION LANGUAGE DERIVED FROM USING BROWSER LANGUAGE PREFERENCE ALWAYS 'EN'
    When the Globalization attribute "Application Language Derived From" is set to "Browser (user browser language preference)", the language preference determined by Application Express at runtime is always 'en'.
    Solution: There is a patchset exception for this available on My Oracle Support - search by bug number. {Note - This patch can only be applied to APEX 4.2.1.00.08}.
  • N/A - APEX LISTENER PDF PRINTING ISSUES WITH STANDALONE GLASSFISH
    When using the APEX Listener stand-alone Oracle Glassfish Server errors have been reported with the APEX Listener PDF Printing capabilities. If APEX Listener is installed into the Oracle WebLogic Server or "full" Oracle Glassfish Server then no issues have been reported.
    Solution: Upgrade to APEX Listener 2.0.1 by downloading from OTN.
  • 15997109 - MISSING CHANGED BEHAVIOR FOR CHANGE IN EXECUTION OF PAGE LOAD DYNAMIC ACTIONS
    {Documentation Bug}
    Within Dynamic Actions, there are two methods of getting Actions to fire after the page has loaded, either by defining a Dynamic Action's 'When > Event' as 'Page Load', or by setting an Action to 'Fire on Page Load'.
    Prior to Application Express 4.2, these two methods were executed slightly differently, which resulted in an inconsistency in how the 'this.browserEvent' attribute of Dynamic Actions was set. For Actions firing from the 'Page Load' When > Event, this would be set to the full jQuery event object for the 'ready' event. For Actions firing where the 'Fire on Page Load' attribute was set, 'this.browserEvent' would be set to just 'load'. This made it difficult for a plug-in developer to easily and consistently isolate behavior that was specific to page load.
    In Application Express 4.2 and later, this is now handled consistently such that 'this.browserEvent' is always set to 'load'. For
    plug-in developers, it is now only necessary to test 'this.browserEvent' for 'load', to consistently isolate page load behavior for your plug-ins.
  • 15966134 - THEME 25 ALERT REGION DOESN'T SUPPORT MULTIPLE PAGE ITEMS IN THE SAME ROW
    Theme 25 "Alert Region" region template is missing Display Points causing layout problems when laying items in same row.
    Solution: Create a Display Point for this region template by going to the Edit Template screen, and in Display Points, add a new Row with the following information:
    Name: Region Body
    Template Substitution: BODY
    Grid Support: Checked
    Maximum Fixed Grid Columns: -1

    Alternative Workaround: Manually set the Column Span field for your items so that the combined number of columns spanned is one less than the container region's column span.
  • 14749955 - MAKE DEVELOPER TOOLBAR AVAILABLE FOR MOBILE APPS
    The Developer Toolbar is not included on jQuery Smartphone pages. After clicking the 'Run Application' from the Application Builder then the only way to get back to the Application Builder is to user the browser back button. You will need to go back once for each mobile page visited.
    Solution: Right click on the 'Run Application' button and launch the application using 'Open Link in New Tab' or 'Open Link in New Window' or similar. The exact command varies by browser.
    Note: For applications with both desktop and mobile user interfaces you can access the Session State for a mobile page by navigating to a desktop page and using the developer toolbar and then changing the page number.
  • 14680379 - PAGE SUBMIT ACTIONS DO NOT WORK FOR LONGER MOBILE SELECT LISTS, WHEN DEFINED TO FIRE WHEN THE SELECT LIST VALUE CHANGES
    In an application that uses a jQuery Mobile user interface, some form elements use native items when running on actual smartphone or tablet devices. Select lists are rendered using a native control as long as the LOV includes up to 10 items. When there are more than 10 items, select lists are rendered as jQuery Mobile dialogs, making it easier to find and pick a value in long lists.
    When using the "Page Action when Value Changed" attribute to make the page submit when the value is changed, will only work when the native control is rendered. Once the select list gets rendered as the dialog with more than 10 items, the page no longer gets submitted. The same is also true when a Dynamic Action that is defined to fire on 'Change' of one of these select lists, where the action is set to 'Submit Page'.
    Solution: No workaround currently available.