Hi Soujanya.
No problem and I certainly agree with you with regards to the approval process and notifications. However I still don't see the one click structure need myself .. perhaps you can change my mind? Here's my thoughts...
Pretty much any organisation that needs a tool like OrgChart or OrgModeler is at a scale such that anyone looking at the overall chart would be incredibly hard pressed to make immediate sense and deliver supportive action based on it. Rather I believe that they would be focussing on a particular area at any moment - a natural drilling in and focus of attention which is actually the user interface basis for the apps. I think where design and review activities are involved the use of analytics and KPIs best applied as these are succinct in visualisation and translate into direct and accurate comparisons.
For the sake of discussion, let's take a small example organisation. We'll give it 500 positions across 100 org units. That's 600 nodes to view.
How big a screen would you need to view all of those nodes at once (clicking and drilling wouldn't be such an issue if you were focussing on particular areas and search allows you to jump in at a particular node) and who can take in 600 nodes of information in a scan and glance?
Even if such a chart (or probably illegible content) gave you a sense of scale in areas, this would still be available and I might suggest quicker and more accurate to reconcile when presented with actual figures.
I'm not saying that there isn't a scenario where someone could not make use of a full org chart that is opened in one click, but I've yet to be shown a solid reason for needing it and how it would be viewed in practical terms that wasn't already better served by what's already provided. I'm certainly more than happy to switch my point of view if a compelling reason is put forward to do so 
Regards,
Stephen.