You can use the Tabs UI Pattern to display large sets of information, which can be split into different areas, while always remaining a click away.
How to use the Tabs UI Pattern
In Service Studio, in the Toolbox, search for
The Tabs widget is displayed.
From the Toolbox, drag the Tabs widget into the Main Content area of your application's screen.
By default, the Tabs widget contains 3 Header Items (tab titles) and 3 Content Items (tab content). You can add or delete as many as required.
Add the relevant content to each of the Header Item and Content Item placeholders. In this example, we add text. You can add forms, images, labels, etc.
On the Properties tab, you can customize the Tabs look and feel by setting any of the optional properties, for example, which tab is displayed as the active tab when the page loads and whether the tabs are displayed vertically or horizontally.
After following these steps and publishing the module, you can test the pattern in your app.
|ActiveTab (Text): Optional||Defines which tab is active when the page loads.
|Orientation (Orientation Identifier): Optional||If Vertical, the tabs are displayed vertically. If Horizontal, the tabs are displayed horizontally. This is the default.|
|IsJustified (Boolean): Optional||If True, the Tabs are evenly distributed in the space available. If False, the Tabs are left aligned. This is the default.|
|IsRight (Boolean): Optional||If True, the Tabs are displayed to the right of the Tab content. If False, the Tabs are displayed to the left of the Tab content. This is the default. Note: This setting is only applicable if the Orientation property is set to Vertical.|
|ExtendedClass (Text): Optional||Add custom style classes to the Tabs UI Pattern. You define your custom style classes in your application using CSS.
Tabs Header Item
|DataTab (Text): Mandatory||Sets the name to connect to the Tabs Content Item. Should be the same as the paired Header Item and unique.|
Tabs Content Item
|DataTab (Text): Mandatory||Value that connects with the Tabs Header Item. Should be the same as the paired Content Item and unique.|