Kinetic Control Compendium

[hmwillett (Hannah Willett)]

Tab

Allows a user to add a tabstrip where multiple tabs can be added.

**Use a Panel Card Stack for this if in 2023.2+ (See clarification below)

Clarification from @bconner:

@bconner

Bonus thing to know about tabstrip is we did not really intend it to be used on the page body it was for inside-card data organization but we didn’t prohibit the use on the page body therefore folks are using it in a way that doesn’t work as well as we’d like. Epicor has used it also but will be replacing it with our intended solution.

@bconner

Our intended solution for this is in 2023.2 where you can join cards together into a group in studio and we strongly recommend using that instead of placing tabstrips on the page body like you are showing here. This will make more sense in 2024.1 - users will be able to group and ungroup cards in personalization, but not if you have built a custom tabstrip layout.

See Panel Card Stacks for this.

Property Group	Property	Description
Basic	Id	Unique identifier for the control
Comments	Comments	Add some developer notes to the control. These are not customer-facing and are only visible in App Studio (Fig. A)
Data	Key Field	Indicates that a bound component is a key field. If true, the field is enabled if there is no current record, allowing the user to select an existing record or create a new one. Not applicable.
Data	Data	This is where you bind the pages to tabs.
Data > Data	Id	Unique ID for the tab.
Data > Data	Title	Title for the tab. (Fig. B)
Data > Data	EpBinding	EpBinding for the tab in the format of DataView.Column. You can use this to enact row rules on the tab (like hiding or showing by user or something).
Data > Data	Selected	Specifies the tab to be selected by default.
Data > Data	Page	Dropdown of pages available to bind to the tabs.

Figure A: Comments

Figure B: Title