After that beyond closing the tab your control of the tab is limited. (Unless there are undocumented features to tabs, in which case please share).
Ideally I would like to be able to control Tabs from the process as I typically use the Tab to display layouts where a form is too simple (eg a layout with a BO's form, a grid that is not directly related and a form for that grid in a Master/Detail layout).
- Process control of when a Tab is opened would open a tab give it a Title, Prevent User from Closing, Place a layout into that new Tab and use a specific BO as context.
Code: Select all
IF BO.Attribute=X THEN TAB_OPEN(TabName, NotCloseable, LayoutFromVP,BO) ELSE...
- Control of the ability for the user to close that tab - to prevent the user from being able to press the little close cross on the tab where that might leave an orphaned BO
- Ideally the tab would be able to hold a BO in context without the need to run other processes
- Be able to uniquely identify the tab - ideally linked to the BO that was placed into context
- Be able to navigate to that uniquely identified tabcheck for the existence of a uniquely identified Tab and if it is open then bring that tab into focus, otherwise open that tab.
Code: Select all
IF TAB_EXISTS(TabName, BO) THEN TAB_NAVIGATE(TabName, BO) ELSE TAB_OPEN(...)
- Open a tab from Contact will flip to the correct tab that contains a Contact
- Open a tab using Order.psContact when the Contact tab is already open will open duplicates because psContact is not considered the same as Contact even though psContact is a reference to Contact
Is there other missing tab functionality?