Tabs

the tabs element organizes form content into multiple tabbed panels, allowing users to switch between different views or sections of a form without leaving the page it is ideal for forms that contain distinct, non sequential categories of information — such as summary, details, history, and attachments — that users may need to access in any order unlike the stepper (which enforces sequential progression), tabs give users free navigation between panels the activetabindex attribute makes it possible to programmatically switch the active tab from event logic — for example, automatically navigating to an error tab if a validation issue is detected, or switching to a results tab after a process completes each tab's visibility can also be toggled individually key use cases • record detail forms with summary / activity / documents / settings tabs • dashboard style forms that present different data views in separate tabs • programmatically switching to a specific tab after a process runs (e g , 'results' tab) • conditionally hiding tabs that are not relevant to the current user's role • organizing approval forms with separate tabs for request details and review decision runtime api — attributes in procesio forms both the tabs container and each tab have their own api attributes, all accessible at runtime via the data model tabs container api name description type default notes activetabindex index of the currently active tab (0 based) — set programmatically to switch tabs number — — visible show or hide the entire tabs container boolean true — name unique element name string — — id unique element id string — — individual tab api name description type default notes label the tab's header label text string — — tooltip help text shown alongside the tab label string — — visible show or hide this individual tab boolean true — name unique tab name string — — id unique tab id string — — for support, please join our https //discord com/invite/cebukgjefv for further assistance and support