It's not really a big deal, but a hindrance.
If I manually create an Automated Row Fetch process for a page, in the "Source: Automatic Row Processing" area, the table name and other fields allow lowercase data to be entered, but the process won't run and simply returns an error unless I go back in and switch my values to uppercase.
If you could add in a couple UPPER() functions to the process, it would eleiminate this potential headache.
I am running Apex version 4.2.1.00.08 on a Win 2008 server.
Edited by: wbfergus-1 on Feb 12, 2013 12:23 PM
Since by default Oracle database identifiers are case insensitive what is obviously required is for the APEX team to fix this bug (by making the process work with the identifiers as entered, not by adding <tt>upper</tt>), and for the deluded few requiring case sensitivity to use quoted identifiers.
A similar unfortunate situation exists in declarative BLOB support, where contrary to all Oracle norms, case sensitive identifiers are documented as being required. Since double quotes don't/can't play any role in the APEX process there, it's difficult to see why this unconventional convention is imposed, rather than requiring a very small minority to use the double quotes they must be using everywhere else.