Template¶
Introduction¶
The Template control is a special Toolbox control available exclusively inside Partial View form models and Master Pages. It defines a named content slot — a region within the Partial View or Master Page that the consuming form (the parent form or Normal Form respectively) can populate with its own controls.
This mechanism allows a Partial View or Master Page to define its overall structure while delegating specific regions of its UI to the consumer, without the Partial View or Master Page needing to know anything about what will be placed there.
How It Works¶
In a Partial View¶
When a Template control is dropped onto a Partial View's canvas, it marks a named slot in that Partial View's layout. On the parent form, inside the Partial View control that references this Partial View, a corresponding container appears for each Template slot. The parent form can then drag and drop any controls it needs into those containers.
At runtime, the controls placed by the parent form are rendered inside the Partial View at the position where the Template control was placed.
In a Master Page¶
When a Template control is dropped onto a Master Page's canvas, it marks a named slot in the Master Page layout. Inside every Normal Form that uses this Master Page, a corresponding container appears for each Template slot. Each Normal Form can independently populate those slots with its own controls.
At runtime, the controls placed by each Normal Form are rendered inside the Master Page at the position where the Template control was placed.
Properties¶
| Property | Description |
|---|---|
| Name | A unique identifier for the slot within the Partial View or Master Page. Used to match the slot to its container in the consuming form. |
Use Cases¶
Partial View Templates¶
Variable content region within a shared layout A "Card" Partial View defines a standard card shell (border, shadow, header bar) and places a Template slot in its body. Each parent form that uses this card appends different content into the body slot — one form puts a data list, another puts a form with input fields — while the card's visual frame remains consistent.
Configurable footer actions A "Detail Panel" Partial View places a Template slot in its footer area. Parent forms append their own action buttons (e.g. "Save", "Cancel", "Delete") into that slot, keeping the panel's layout uniform while allowing each usage to define its own set of actions.
Optional sidebar A layout Partial View defines a two-column structure with a main area and a Template slot for the sidebar. Forms that need a sidebar populate it; forms that do not leave it empty and the layout collapses gracefully.
Reusable wizard shell A "Wizard" Partial View defines the step indicator, navigation buttons (Back / Next), and overall chrome, and places a Template slot in the content area. Each step of the wizard is a different set of controls appended into that slot by the parent form, one step at a time.
Master Page Templates¶
Page-specific action toolbar The Master Page places a Template slot in the header next to the page title. Each Normal Form appends its own contextual action buttons (e.g. "Save", "Export", "Delete") into that slot, keeping the header layout consistent across all pages without the Master Page needing to know about each form's actions.
Per-page breadcrumb trail The Master Page places a Template slot in the breadcrumb bar area. Each Normal Form appends its own breadcrumb items reflecting its position in the application hierarchy. Breadcrumb styling is owned by the Master Page; content is owned by each form.
Contextual sidebar panel The Master Page places a Template slot in a collapsible sidebar. Most forms leave it empty, but certain forms (e.g. a document editor or a settings page) append a context-sensitive panel with additional options or metadata.
Relationship with the Partial View and Master Page Controls¶
The Template control is the counterpart to the container that appears in the consuming form. The relationship is:
- Template control (inside Partial View / Master Page) → defines where the slot is and gives it a name.
- Slot container (inside the Partial View control on the parent form, or inside the Normal Form on the Master Page) → is where the parent/child form places its controls for that slot.
Each named Template produces exactly one corresponding container in the consumer. If a Partial View defines two Templates (e.g. "Header" and "Footer"), the Partial View control on the parent form will expose two separate containers, one for each slot.