The problem of strings with more than 4000 chars in different regions

When you create an object (item, process, validation, ...) in APEX with the application builder there are properties like messages, conditions and comments. These properties using a string with more than 4000 characters will encounter an error like that:

Even when you use an item Value like


 and the value of this item is longer than 4000 characters, it will result in runtime in this error:

In my case i had to print out a message for the user which could be longer than the 4000 characters.
One solution for my case was to use jQuery and Dynamic Actions to print out the content of an item.
I created the Dynamic Action on the Global Page (Page 0) with these attributes:
The JavaScript Code is:  $('.uMessageText').append($v('P0_TEST'));
Of course there are other ways like described in my oracle-forum thread, but i hope the next apex versions will solve these problems.

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.