I don't believe so, however I have not done lots with the hierarchy of parent/child regions. You might look into it. Create a parent region and all your other regions a child of that region. If the condition on the parent prevents it from rendering, I am not sure if that will prevent the child regions from display. I would have to check. If works that way then that could be your answer.
Message was edited by: DLittle I did a quick check I think you can create an empty html region and make all your other regions as sub-regions to that new html region and then apply your condition to the parent only. http://docs.oracle.com/cd/E23903_01/doc/doc.41/e21674/ui_region.htm
This is same suggestion as in David's initial reply.
The problems with this approach is that there are no page level conditions. So the conditions have to be applied/configured for each region which is not ideal.
Though David's second suggestion also not ideal, it is better than setting conditions per region it is a limitation imposed by the APEX environment?
A totally different way to go about it is taking use of the different templates for the login page and the standard pages.
Region set to templates that are not in the page template are not rendered.
Check which region position substitution strings (#REGION_POSITION_05#) are used by your default page template and not in your login page template.
Set the regions on your global page to use the region positions that are not in login page template.
A benefit off this approach is that the region positions not used in the template are not evaluated to render. Meaning those condition aren't checked saving rendering time.
Depending or your theme and the position you need for your global regions you may have to shuffle the region position around in your templates.