It just hit me – with the proper db table and a where clause in the SQL, you can actually create a personalized tab system, based on user name, security etc. Really powerful stuff." It actually much more powerful than the built in tabs …"
select tab_label as "TAB_LABEL",'doSubmit("'||tab_name||'");' as "TAB_LINK" from apex_application_tabs where application_id = :APP_ID order by display_sequence
apex_application.g_unrecoverable_error := true;Assuming you put TAB_LINK in your doSubmit, of course. Adjust as necessary depending on whether TAB_LINK is just a page id or the entire URL.
select tab_label,tab_link from (Thanks
select tab_label as "TAB_LABEL",'doSubmit("'||tab_name||'");' as "TAB_LINK",
case when <some condition> then 'Y' else 'N' show_tab
where application_id = :APP_ID
order by display_sequence
) where show_tab='Y'
I've played in the past with #TAB_LINK# and if you'll check the source code you'll see it is only being substitute with doSubmit('T_....'); . I suspect the processing engine "knows" it is a tab just by the tab naming convention – prefix T_. So I believe that if you are using the TAB_LINK from the apex_application_tabs view, you don't need to worry about the branching. If you're creating your own link repository, your suggestion seems like a good solution." If you use doSubmit as the TAB_LINK (as Arie showed), the page will be submitted and form inputs will be saved but you need to do something special to branch to the next page (This is not an issue when using regular tabs because the accept processing engine "knows" that a tab has been pressed and branches to the target page)"
Sometimes I prefer it this way (as you said, the opposite of the default tab behavior). I'm trying to educate my users to take an explicit action – pressing a button – whenever they want to save something on page. It seems that for some of the users, the intuitive behavior of a tab is like pressing "esc" or "cancel". All they want is to leave the current page in favor of another. Usually I encourage this behavior, as it is consistent with the behavior of pagination in tabular forms. Users learned that in order to save their work they need to press "submit" and any other action can result in them losing their work." Standard tabs submit the page so form inputs are saved into session state. If you code the TAB_LINK as a regular link (not a submit), form inputs will be discarded"
Is there a way to make the tab-report appearing on all this pages without adding it physically to the page.Put the tab replacement report in the appropriate region on Page Zero.