Comments on: "Comment out" an Oracle APEX Process, Validation, Branch, …

By: Subramanian Kaushik Gurumoorthy

Subramanian Kaushik Gurumoorthy — Thu, 15 Oct 2009 22:31:58 +0000

Hi Patrick,
Good to see a nice blog on Apex.
Iam a forms guy and I want to work on Oracle apex , So could you give me some directions which would reduce my learning curve.

Thanks in advance for your help.
regards
Subramanian Kaushik Gurumoorthy

By: Scott Wesley

Scott Wesley — Tue, 06 Oct 2009 07:09:23 +0000

G’day Patrick,

I’ve been experimenting with the build option, and I can’t get it to behave as expected. Given the following directions
- create ‘exclude’ build option under shared components
- assign build option to a page (and specific button to be sure)
- export the application
- import as separate id, check the page & button do not exist
- page & button exist!

I’ve also had a play with the build option in the supporting components section, checking the prompt for build checkbox – hoping perhaps I may get prompted somewhere during import.

I’m using Apex3.2.1 on 10gR2

Any tips?

By: Yuri

Yuri — Sun, 22 Feb 2009 15:31:55 +0000

It’s absolutely obvious solution.

Every developer must do this trick automatically and without thinking.

By: Mihaï

Mihaï — Thu, 20 Dec 2007 09:20:00 +0000

thanks Patrick

sorry for missing the first explanation on Condition Type

By: Patrick Wolf

Patrick Wolf — Thu, 20 Dec 2007 08:38:00 +0000

Hi Mihaï,

just noticed that I have made a typo in the above text. Instead of "None" it should have been "Never". I have fixed that.

So see above why I wouldn't use the condition type. About the performance. Should be the same, because both are fixed wired checks in the APEX rendering code and remember, it should always be the exception that objects/code is commented out so you will hardly be able to measure a difference between this two methods.

About "readability": There a pros and cons. When you are going to deploy your application, the "Utilization" tab gives you a quick quality check to verify if there is code which shouldn't be commented out. For the conditions you can't do that. Pro for the condition is that you see it immediately on the page overview that the object/code is not used. BTW, I will add a highlighting for the "Build Option" to the APEX Builder Plugin as I did for the "Comment" field to make it better visible.

Patrick

By: Mihaï (apex newbie)

Mihaï (apex newbie) — Thu, 20 Dec 2007 04:48:00 +0000

thanks for the tip

isn't it that this functionality can be achieved most of the times with conditional display-Never ?

some more questions:
* from the readability point of view which is more developer friendly for you?: the utilization tab or seeing Never on the ( Page definition )
* which would be faster on running?: disabling by build options
or disabling by condition-never
or both

By: Anthony Rayner

Anthony Rayner — Wed, 19 Dec 2007 09:30:00 +0000

Patrick,

Nice trick! Will come in very useful.

Anthony.