I found bug in tabular forms created over tables that have columns with timestamp datatype (datepicker fields).
If you try to update any column value you'll get error message like this one:
Current version of data in database has changed since user initiated update process. current row version identifier = "CB89E9B0740B64051B6CA00FD81E58166C2288FA" application row version identifier = "3641B87EB52532E016A0D8377AA8F181A6E2FBCA" (Row 1)
I'm getting same error on APEX 4.2.5.00.08 and 5.0.0.00.31 (apex.oracle.com).
The bug was reported to APEX team and it will be fixed in future releases (5.1).
Quick fix for this is applying explicit format mask for timestamp datepicker columns.
Thanks to Robert and Valentino Orehoci for pointing this out and Marc Sewtz for quick fix.
If you're getting this alert window when going to your APEX 5 login screen:
after upgrading from older versions of APEX you're probably missed this paragraph in installation documentation: When using Oracle REST Data Services as your web listener, static files are served using RESTful service module built into Oracle Application Express. Therefore, you must configure RESTful Services in new installations and in upgrade installations when RESTful Services were not configured in a previous release.
To fix it don't forget to configure Oracle REST Data Services by executing this script @apex_rest_config.sql.
Deprecated column types in Classic Report. Oracle recommends to use Tabular Forms or APEX_ITEM API for creating editable reports.
File Browse Item should use APEX_APPLICATION_TEMP_FILES table for select, update or delete operations instead of WWV_FLOW_FILES. Deletes are no longer necessary, as the file will automatically be purged after the request or when the session is purged.
If you used WWV_FLOW_FILES as a permanent store, the files should be copied into their own BLOB column(s) within a table within your schema.
In APEX 5.0 there is only one button type which can be positioned in a region or next to items. Finally, no more Item Buttons! :)
Page computations and validations based on SQL expressions have been deprecated. You should use PL/SQL expressions or PL/SQL Function returning VARCHAR2 types
#PLUGIN_PREFIX# substitution string is not supported any more in plug-in files. You should use relative URLs instead.
Also, there's a nice chapter about Changed Behavior. Here are some nice bullets to remember:
Static files will be stored in central repository that is available for a specific application (Static Application Files) or for all applications within a workspace (Workspace Application Files)
Static application files uploaded to Shared Components are automatically included in an application export. No more recreating supporting object scripts. :)
In a future version of Oracle Application Express, the dictionary view APEX_WORKSPACE_FILES will no longer include CSS, image or static files uploaded in Shared Components. You should use the new views APEX_WORKSPACE_STATIC_FILES and APEX_APPLICATION_STATIC_FILES instead.
Because of internal changes to the views APEX_APPLICATION_FILES and WWV_FLOW_FILES, it is not possible anymore to lock rows with SELECT FOR UPDATE
Please check the whole documentation for details. Remember, for now this is only BETA documentation.
Don't forget to check those chapters in full documentation before moving to APEX 5.
If you like to write custom JS code
in your APEX applications or to use lots of 3rd party plugins you
should be aware of changes in jQuery and JS libraries in APEX 5.
APEX 5 (at least current version
5.0.0.00.28) uses jQuery 2.1.3 and if you plan to migrate from APEX 4.2 you
should check for changes from jQuery version 1.7.1 which is included in APEX
4.2. There are some things that are deprecated and removed like .die() or
.live() event handlers.
But APEX development team was one step ahead and they provided us with quick solution to include jQuery Migrate plugin that restores deprecated features and behaviors of jQuery.
Note that, as you can read in jQuery documentation, jQuery 2.x has the same API as jQuery 1.x, but does not support Internet Explorer 6, 7, or 8. APEX development team also thought of that and they put conditional comment to handle this:
Also be aware that by default when you create new application in APEX 5 there is no more old