Error when updating Static File Comment in APEX 4.2.1

Today i played around with updating static files in APEX. Using apex.oracle.com with version 4.2.1 i got an error when updating a static file comment. I simply uploaded a file and afterwards i tried to change the comment. The comment which was initially submitted was saved, but any change results in:
Error updating file.
ORA-06502: PL/SQL: numeric or value error: invalid LOB locator specified: ORA-22275 ORA-06512: at "SYS.DBMS_LOB", line 884 ORA-06512: at "APEX_040200.WWV_FLOW_HTML_API_PRIVATE", line 144 ORA-06502: PL/SQL: numeric or value error

APEX Expertenseminar in Berlin

Vom 09.04.-10.04.2013 findet in Berlin ein Expertenseminar mit Niels de Bruijn und Mir statt. Inhaltlich ist es für fortgeschrittene bzw. Profis im Bereich APEX Entwicklung. Es beschäftigt sich schwerpunktmäßig mit der aktuellen Version 4.2 und der mobilen Webentwicklung.
Neben den APEX eigenen Werkzeugen werden auch die Integration von Hudson, FOEX für komplexe Dialoge, sowie automatisierte QS-Unterstützung vorgestellt. Das Seminar besteht sowohl aus Workshopkomponenten als auch Vorträgen.
Alles weitere findet man auf den Seiten der DOAG "Berliner Expertenseminar: APEX für Experten mit Niels de Bruijn und Oliver Lemm".

APP_PAGE_ID=0 in OnDemandProcess

In APEX we have many Substitution Strings. One of these is :APP_PAGE_ID. Be careful with this String in an OnDemandProcess. I have called an OnDemandProcess by using JavaScript/AJAX and the result was, that :APP_PAGE_ID was always 0.
To solve this problem i have created an Application Item (AI_APP_PAGE_ID). This item will be filled every time a page is rendered in APEX.

*Update*
Due some good tips the problem can be solved by calling the OnDemandProcess with the correct full syntax from JavaScript.
var ajaxCall = new htmldb_Get(null,$v('pFlowId'),'APPLICATION_PROCESS=IS_HANDLE_VALID', $v('pFlowStepId'));
With this call especially the last parameter $v('pFlowStepId') the pageId will be the actual ApexPageId where the Javascript is used.
Thanks to Peter and Roel for your tips.

Highlighting in full-text search works case sensitiv

If you search for something in APEX you can use in version 4.x or later the full-text search.
It's a great feature, but the the word is only highlighted, if you write it completly the same way, even if you don't check "case sensitive".

Keep in mind that the result always finds all the correct words and only misses the red highlighted string.

Result when searching for P1600_AEU_WHRG_KEY

Result when searching for P1600_aeu_whrg_key

Wishing new features in APEX future Releases

Wishing new features in the next APEX releases can be affected by everyone in this official Feature Request Application. Now is the right time, because the last APEX Patch 4.2.1 is not far away and the next release will be a bigger one.
Here are some of my most desired features (beside the State of direction for APEX 5.0)

• Authorisation accepts parameter (Feature ABPY)
  At the moment it's not possible in an APEX Authorisation Scheme to forward any information from the calling element. Further more it would be nice to have some variables, which could be referenced in the authorisation. Now you have to use the condition area to use specific parameters. If there is already some kind of condition (often already functional conditions are existing), the technical authorisation and the functional condition is mixed up.
• Read Only condition - read only type option (AA4A)In the last projects, often we got the questions, why the read only text area or select-lists are displayed differently in standard read only mode. With this feature it would be possible to display the input element like the original one with only shown greyed out.
• Defining one named Dynamic Action for different use (AD1B)Often the same effect (Dynamic Action) should be used on different objects and even different pages to effect like the same way. In this case it would be nice to define named Dynamic Actions and only call these actions which are predefined in the shared objects.
• Tabs using URL Targets => Tabs can be opened with right click (AD1A)
  It's only a small feature, but often when i use application in nower days, i'm disapointed, when i can't open a link in a new browser tab. In standard APEX at the moment it's not possible.
• Able to lock whole application (ADVQ)
  In many cases we have different people who are starting new APEX projects or customers who want to look into the development areas. These people should not be able to change anything but should be able to reach every attribute in the application builder.
• Integrate with Subversion (ABAF)
  Working with big APEX Applications, it would be nice to have an easy access to every APEX component by using subversion.

 I wish a merry christmas and some days to relax.

Advisor misses column mapping for Tabular Form

If you create a tabular form based on a view or table you have to take care that the column mapping have to be updated.
In a short test where i created a view on a table i changed the name of the view after creating the tabular form.I got an error "ORA-00942" that table or view were missing.
I went through all processes and changed the view name, but i missed one column. Checking the Page with the APEX Advisor the failure in my column mapping was not found.
The problem can be found with this query:

select c.application_id
      ,c.page_id
      ,c.column_alias
      ,c.reference_table_name
      ,c.reference_column_name
from apex_application_page_rpt_cols c
left join user_tab_cols u on u.table_name = c.reference_table_name and
                             u.column_name = c.reference_column_name
where c.reference_table_name is not null and
      c.reference_column_name <> 'ROWID' and
      u.table_name is null

It would be nice to add this check to the advisor  @ APEX Team

APEX 4.2.1 released

On the 14. of december the APEX version 4.2.1.00.08 was released.
The Patchnotes are available under APEX 4.2.1 Patchnotes. The fixed bugs are listed up here. A short look over all fixed bugs sumerizes that the most fixes are belonging to the mobile theme and components of APEX.

These Know Iusses are still open bugs:

• Developer Toolbar Not Available for Mobile Applications
• Page Submit Actions Not Working for Some Longer Mobile Select Lists
• Issues with Editing Items After Upgrade
• Theme 25 Alert Region Does Not Support Multiple Page Items in the Same Row

Here are changes in the behaviour of APEX

• Maximum Width for Textareas
• Textarea can use less then maximum width
• Enhanced Security for Report Links
• JavaScript/jQuery can be mixed up with column name syntax
  javascript:alert( 'Delete #NAME#' );
• jQuery Mobile
• updated to 1.2.0
• AnyChart 6
• AnyChart 6.0.11 is included
• Resizing of Charts on Mobile Page
• Now its possible to resize charts in the mobile theme with jQueryMobile

Keep in mind if you update a 4.2 release you have to go to support.oracle.com and download the patch number 14732511.