When a user opens a project, the first page displayed is the default report navigation tab. The default tab can be customized using the special "Params" project. In this project is a data set called Tabs. The data set includes instructions for modification, which are included here for convenience.
Description
This dataset specifies what cross-project tabs exist, and what project they navigate to.
Important Notes
This dataset does not control all visibility. All that it does is adverties a tab as being cross project. IF a tab exists in a local project, it will override and cross project tabs. This dataset also cannot hide a tab that comes from the current project (This can be done by opening the tab you wish to eliminate, and choosing 'delete report').
The standard application tabs typically look up the project that they navigate to from the projects dataset. Other tabs will not do this.
A user account may override the standard destination for a tab. It this is happening, there will be a user with that userid in the tabUser column. This row is created if the user opens an application tab in any project other than the default for that tab. If this row exists, the user will navigate back to that project, instead of the default. This matters for whatifs and BF, where a tab may correspond to multiple projects. The user will be taken back to the last project they were in in that tab.
Cross project tabs only support 'true tabs' not default project tabs. You can tell that a report is in a true tab because when you are viewing that report, its url will contain '.View:tab:the name of the tab'
Do not make any structural changed to this dataset.
Default Table Transform Columns
Column | Description | Required | Type | Formatting Expectations |
| TabName | The name of the tab for which this row controls the destination. | Yes | label | The name of an apptio tab. This does not include the tab: or .View: part of the report, just the report name. |
| ProjectColumn | The name of the column in the Projects dataset that the project name should look up from. The Standard apps tabs use this, custom tabs should leave this blank. There is an if in the table transform that codes in the logic for handling projectColumn. | No | Label | a column name in the projects dataset, or null. |
| TabProject | The name of the project that the tab should navigate to. If projectColumn is nonnull, and the tab project in the raw table is null, this will read in the tab from the projects dataset. | Yes (Unless the tab is disabled). | Label | A valid Apptio Project Name |
| TabDisabled | allows a tab to be disabled, at which point it will not show. IT is possible for a user to get a per user tab override, even if the default tab destination is disabled. If the value in the raw table is null, and so is tab project, the table transform will disable it. | No | Label | enabled, disabled, null. |
| TabRoleList | This entry allows you to state that for a particular role this tab goes to a particular project. It will override the default project for a tab, and is ofverriden by a row with tabUser set. | No | Label | null, or a valid Apptio Role |
| TabUser | This entry allows you to have a user go to a project when clicking into a tab the overrides the default, or the per role setting. | No | Label | null, or an apptio userId. |
Default Raw Table Columns
Same as table transform.
Considerations when adding a new Raw Column
Do not modify the structure of this dataset.
Related Tables
Dataset Name | Description of Relationship |
| Projects | Apptio's OOTB Applications read the name of their project for default tabs from this dataset. |
Reports Affected
Report Name | Description of Dependency |
| All | Every single report in an application tab is affected by this dataset. |