title | description | author | ms.author | ms.topic | ms.date | ms.reviewer | audience | ms.search.region | ms.search.validFrom | ms.dyn365.ops.version | ms.assetid |
---|---|---|---|---|---|---|---|---|---|---|---|
Section Tabbed List subpattern |
Learn about the Section Tabbed List subpattern, including overviews on usage, wireframes, pattern changes, models, and UX guidelines. |
jasongre |
jasongre |
article |
06/20/2017 |
johnmichalak |
Developer |
Global |
2016-02-28 |
AX 7.0.0 |
3f8b00ff-54f0-4e32-bd7f-b94a74785537 |
[!include banner]
This article provides information about the Section Tabbed List subpattern. This subpattern is used as part of the Operational Workspace pattern, specifically for a panorama section that contains a set of vertical tabs, each of which contains a filtered list of data.
The Section Tabbed List subpattern is used as part of the Operational Workspace pattern, specifically for a panorama section that contains a set of vertical tabs, each of which contains a filtered list of data.
This pattern didn't exist for Microsoft Dynamics AX 2012.
-
TabPage
-
TabbedList (Tab) (Style=VerticalTabs)
-
TabbedListPage (TabPage) [0..N]
- TargetForm (FormPart)
-
Each Form Part points to a form that contains the content for the section. Each of these forms should use one of the Form Part Section List form patterns.
Apply Section Tabbed List to the appropriate tab page in the workspace.
The verification checklist shows the steps for manually verifying that the form complies with UX guidelines. This checklist doesn't include any guidelines that will be enforced automatically through the development environment. Open the form in the browser, and walk through these steps.
- At least one list should be present in the tabbed list section.
- Each Form Part Control should point to a form that uses one of the Form Part Section List patterns.
Form: PurchOrderMaintainWorkspace (All workspaces > Purchase order preparation)
This section will have answers to frequently asked questions that are related to this guideline/pattern.
None
[!INCLUDEfooter-include]