No results found

Your search did not match any results.

We suggest you try the following to help find what you’re looking for:

  • Check the spelling of your keyword search.
  • Use synonyms for the keyword you typed, for example, try “application” instead of “software.”
  • Try one of the popular searches shown below.
  • Start a new search.
Trending Questions
apex

Oracle Application Express Known Issues - Application Express 5.1.2

Application Express 5.1.2 was released on June 28, 2017.

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 July 13, 2017.

  • 26337459 - APEX_UTIL.FIND_SECURITY_GROUP_ID RETURNS NULL IN SCHEDULER JOB CREATED VIA APEX

    When creating a scheduler job from within APEX, e.g. SQL Commands, the job creator is APEX_PUBLIC_USER. This can cause various procedures, e.g. APEX_UTIL.FIND_SECURITY_GROUP_ID or APEX_UTIL.SET_WORKSPACE to fail.

    Solution: There is a patchset exception for this available on My Oracle Support - search by bug number.

  • 26326761 - SURVEY BUILDER: CAN'T EDIT QUESTIONNAIRE PAGE 30, WITH ORDS 3.0.10 INSTANCE

    ORDS 3.0.10 is stricter with URL references than previous versions of ORDS.

    Workaround: Edit Page 30 and change "#JQUERYUI_DIRECTORY#/ui/minified/jquery.ui.sortable.min.js" which is included in the page attribute 'File URLs' to "#JQUERYUI_DIRECTORY#ui/minified/jquery.ui.sortable.min.js" i.e. without the slash after #JQUERY_DIRECTORY#.

  • 26352194 - SAMPLE PROJECTS: ADMINISTRATION PAGE THROWS ORA-00942: MISSING TABLE DEMO_STATES

    Sample Projects application is reporting an ORA-00942 error on the Administration page, pg 24: Error computing item source value for page item P24_STATE_COUNT. ORA-00942: table or view does not exist

    Workaround: Install the Sample Database Application.

  • 22090477 - NOT ABLE TO PERFORM A SINGLE COMPONENT EXPORT/IMPORT FOR NAV MENU LIST

    If the navigation menu list is exported and imported with a component export, the reference in the User Interface Details will get lost.

    Solution: There is a patchset exception for this available on My Oracle Support - search by bug number.

  • 25303970 - INLINE ITEM ERRORS FOR OLDER THEMES ARE NOT ALWAYS CLEARED WHEN A PAGE HAS ‘RELOAD ON SUBMIT’ SET TO ‘ONLY FOR SUCCESS’

    If an application uses an older theme (not the Universal Theme) and has a page that uses the ‘Reload on Submit’ attribute setting of ‘Only for Success’, then Application Express will use the new client-side messaging to display error messages without a full page reload. However, the label templates in older themes are not compliant with the new client-side messaging logic, which in turn results in some fallback logic being used to display the inline item errors, causing issues with clearing the message. The issue occurs if a page has more than one item error displayed, and then subsequently if only one of those errors is rectified before the next attempt to save, the inline item error message for the rectified error will not be removed as it should be. It is removed from the page error notification, but not from the inline item notification.

    Note: Applications using older themes, generally have the page attribute ‘Reload on Submit' set to ‘Always’ so will not face this issue. However, new pages added to existing applications will have the page attribute set to 'Reload on Submit' by default.

    Workaround: You can set the page attribute ‘Reload on Submit’ back to ‘Always’, however, this will preclude you from being able to use an Interactive Grid on that page.

  • 25305292 - CLIENT SIDE INLINE ERROR MESSAGE FOR RICH TEXT ITEM GIVES JAVASCRIPT ERROR

    If you have a Rich Text Editor item that has validations on a page with page attribute Reload on Submit = 'Only for Success' then if there are validation errors to report there will be a JavaScript error that keeps the inline validation message from displaying. This may also affect reporting other errors on the page, and will keep the page from being submitted again.

    Workaround: You can set the page attribute ‘Reload on Submit’ back to ‘Always’, however, this will preclude you from being able to use an Interactive Grid on that page.

  • N/A - THE TIMEZONE APIS AND CONSTANTS AVAILABLE IN APEX_JSON SHOULD NOT BE USED

    APEX_JSON contains new, undocumented APIs and constants for reading and writing TIMESTAMP, TIMESTAMP WITH TIME ZONE and TIMESTAMP WITH LOCAL TIME ZONE values. These APIs and constants are subject to change in later releases, which will likely break any code that utilizes them at this point in time.

    Workaround: Do not use the undocumented timezone APIs and constants until they have been documented.

Changed Behavior:

  • N/A - CLIENT-SIDE MESSAGING ISSUES IN APPS USING OLD, OR CUSTOM THEMES

    If you create a new application using an old, or custom theme, or add new pages to an existing application which is not using the Universal Theme, then you may encounter minor differences in how inline errors are displayed. This can affect you if either:

    1. The page attribute 'Reload on Submit' is set to 'Only for Success' (the default for new pages) and an item validation occurs.

    2. The application 'Compatibility Mode' is set to '5.1' and the submit button is set to 'Execute Validations' = 'Yes', and any items have client-side validation such as 'Value Required' = 'Yes', which fail

    An inline error is shown but it may not look exactly the same as on other existing pages because it isn't using the templates from the theme.

    Workaround: These differences can be a avoided by setting 'Reload on Submit' to 'Always', (Note: Interactive Grid requires this to be set to 'Only for Success') and not using client-side validation by either setting application compatibility mode < '5.1' or Setting Execute Validations = No. The differences can also be avoided by updating the old theme to use the new style of error templates, or by updating the application to use Universal Theme.

  • 25247070 - TIE SWITCH TO ASYNCHRONOUS DYNAMIC ACTIONS TO COMPATIBILITY MODE 5.1

    In Application Express 5.1 the compatibility mode controls how Ajax-based Dynamic Actions operate, specifically a setting of '5.1' will make all Ajax calls asynchronous. Prior to 5.1, Ajax-based Dynamic Actions that also had the ‘Wait for Result’ attribute set to 'Yes' would issue synchronous Ajax calls. Synchronous calls can have a negative impact by blocking all page interactions until the call has been completed. Dynamic Actions with 'Wait for Result' set to 'No' previously performed asynchronous Ajax calls, therefore, there is no change in behavior for these actions.

    This change has been tied to compatibility mode to protect against possible regressions in existing applications, where applications may have relied upon the synchronous Dynamic Actions nature for certain functionality.

    Workaround: Remove the reliance on synchronous-based Ajax calls before upgrading the compatibility mode for the application.