Your search did not match any results.
We suggest you try the following to help find what you're looking for:
Application Express 5.1.4 was first released on December 19, 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 January 18, 2018.
Note: Review the Application Express 5.1.4 Known Issues Addendum for important information regarding flash charts.
When importing an application that contains an Interactive Grid, all user saved reports (Public and Private) will be lost.
Workaround: Warn end users that their saved reports will be lost, or do not import applications into production that contain Interactive Grids.
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.
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.
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.
With Oracle Application Express 5.1.4, 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.
Oracle JET requires that each series of a multi-series chart contains a data point for each label that is represented on the x-axis. Otherwise, the multi-series chart may not render correctly by Oracle JET. Prior to release 5.1.4, the user was required to handle the densification of their data in their chart SQL query to ensure that each series had the same number of data points, even if they were null or zero. Oracle Application Express release 5.1.4 now includes support to automatically fill in gaps, injecting missing data points for multi-series charts.
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.
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.