That’s the last posting about new features in the 1.02 release of the ApexLib Framework.
Ever wanted to set a case restriction (uppercase/lowercase/capitalize) for a field like you can do it in Oracle*Forms with the “Case Restriction” property?
Here you go!
One problem with Tabular Form Column is that they don’t have a “Maximum Width” property as Page Items do. APEX automatically generates a maxlength=2000 for all columns. What is the result? The user gets a
when he enters a too long value. Not really nice, isn’t it? And now he has to start counting so that he knows where to cut of…
Just kidding I was just looking for an eye catcher…
Maybe you have already seen my announcement that I have released v0.17 of the ApexLib Framework, which contains a lot new features.
The previous features in the Framework mostly concentrated on improvements of Oracle APEX on the server, so that’s easier to access Tabular Forms or do automatic validation of date picker or numeric items. The main idea was to make APEX applications more secure without having to do a lot of additional coding. Continue reading
Have you ever wondered why you have to create extra validations for required items (item is NOT NULL), for date picker items (item is a valid date) or for numeric items where you have already specified a numeric format mask?