Two tabs for the same page

Question

Hello,
I have been spending the whole morning trying to find a solution for this problem but did not find any either by myself or parsing the forum messages.
I am building an application with a two level tab for the navigation.
Everything is fine as long as the pages referenced by the tabs have a different number.
My problem is that i use the same dynamic page (let say 40) to be accessed through two different tabs.
e.g Parent tab is labelled "Parent"
Two other tabs are created linked to parent tab "Parent" and those are labelled "Action1" and Action2"
Selecting "Action1" will result in rendering the page 40 with a parameter (let say page_type) set to the value 1.
Selecting "Action2" will result in rendering the *same* page 40 with a parameter (let say page_type) set to the value 2.
For the parent tab "Parent" let say that the default is to select "Action1"
Is there any solution to implement that kind of behaviour?
I have tried to create redirecting pages (empty page and a single branch) to achieve this but i always get stucked when trying to have page 40 displaying the proper tabs and parent tab.
Thanks in advance for any help.
Daniel

Answer 1

Hi Andy,
Thanks for your answer!
Whilst it is fairly straightforward to create multiple tabs for the same page (this can be done through Shared Components, Tabs and click Add on the standard >>tabs bar, enter in any page number you like), the functionality of tabs does not provide the means to set item values. Additionally, as both tabs would be >>"current" for your page 40, once you've clicked on one, you can not click on the other.Yes this is exactly what i discover once my page 40 has been built.
There may be ways to do what you need, but as tabs are really there for navigation purposes only, this may become rather complicated. What is the difference >>between Action1 and Action2? Can this be achieved in another way? Have you considered switching to lists for navigation (where you can set item values)?In fact, i can still duplicate this page and have a few changes within each new page. But as a matter of code design as both pages have around half in common, i wanted to share most of the items (build a single page) and then play for a few additional items with conditions encompassing the page type i have set before rendering the page.=> Most items in common, a few others whose display is conditionnal. For the end user, it looks like two different pages because in their business process the "Action1" and "Action2" are clearly different.
I use lists in this application on the home page to reach most of the application pages but while some users prefer to use the links on the home page and go back to home page, other would like to use the tabs and a number of them use both navigation mechanisms.
Sorry if it is not quite clear (english is not my mother tongue).
Regards,
Daniel