|
|
Form |
|
|
|
|
|
Form |
|
|
|
|
|
|
Form |
|
|
|
|
|
Form |
|
|
|
|
|
|
||
The Form tab is used for editing the data related to the document (Document name, Publish from/to, etc.) or its structured content. The document fields are fully customizable for every document type.
Any changes made to the document's field values must be confirmed by clicking the 
Save button.
Note that values of system fields edited using the Form tab may be overridden due to the way the fields are being processed.
If you are editing a product (i.e. an SKU and the associated product type document), the 
Remove SKU from this document action in the SKU binding section allows you to remove the bound SKU from the document. Please note that the system does not support the action (and hides the section) for products using a workflow.
If you are editing a product type document only (i.e. no SKU is currently assigned), the 
Create new or assign existing SKU action allows you to assign an SKU (new or existing) to the document.
Other properties available here when editing a product can also be modified in CMS Desk -> E-commerce -> Products -> Edit (
) product on the General tab. For further details about products, please refer to the Products chapter in the Managing your store section of the E-commerce Guide.
If a workflow is defined for the current document, an additional list of actions becomes available in the header of the tab.
In the case of dedicated wireframe documents (CMS.Wireframe document type), the Form tab is used to manage properties related to the wireframe's functionality.
The Comments area at the top of the tab can be used to enter a text description or any other information about the wireframe, e.g. detailed instructions for other developers on how it should be converted to an actual page.
By default, wireframe documents are ignored by all forms of search (both the Smart search module and the SQL search). To enable search for the wireframe, uncheck the Exclude from search box.
In the Inherit content section, you can configure the visual inheritance preferences, which determine what will be displayed when viewing the wireframe in addition to its specific content. It is possible to inherit content from parent documents in the content tree, both from standard pages and other wireframes. If the parent is a standard document that also includes a wireframe definition, the inherited content will be loaded from the wireframe. Please select one of the following options:
Use page template settings |
The content inheritance is determined by the settings of the wireframe's page template.
To manage the template's configuration:
1. Switch to the Wireframe tab, 2. Right-click the green template header above the wireframe grid and select 3. Set the Inherit content property on the General tab of the Page template properties dialog. |
Do not inherit any content |
The wireframe does not inherit any content from parent documents in the content tree. |
Inherit only master page |
The wireframe inherits content from the first master page above the document in the content tree. If there are multiple master pages, the wireframe only inherits from the closest one in the hierarchy. |
Select inherited levels |
You can select exactly from which parent documents the wireframe should inherit via the checkboxes below. |
|
Content inheritance requirements
If you wish to inherit content from a parent wireframe, it should always contain the Next page level wireframe component (web part) in its definition. If this is not the case, the child wireframe will only display the fixed inherited content and will not be editable in any way.
For standard page content, the basic visual inheritance requirements apply. This means that the Page placeholder web part must be placed somewhere on the parent page to ensure that child documents are displayed correctly (including wireframes). |
The 
Convert to another document type button in the tab's header provides a way to transform the wireframe into a different document type. This action can be used when you wish to create an actual page (document) based on the wireframe. The new document will still contain the wireframe definition in addition to its standard content, so you may refer to it at any time and even make further modifications. Please note that this process is irreversible and it is not possible to convert back to a dedicated wireframe‑only document.
Once converted to a different document type, the configuration options described here are longer be available on the Form tab. You can instead access them by switching to Properties -> Wireframe.
Additional resources:
•Developer's Guide -> Development -> Wireframing
•Developer's Guide -> Development -> Wireframing -> Managing wireframes
•Developer's Guide -> Development -> Wireframing -> Configuring content inheritance
