Layouts are custom templates that make it possible for you to render content in a wide variety of ways. These templates are developed internally within your organization and made available for you to add to content items via the Insert menu in the Editor. Contact your main editor or application manager for information about the layouts that are available.
Because layouts can take on so many different forms, their use can only be described generically.
In This Topic
Input Fields
Layouts can contain input fields that an editor can fill in with content. To enter text into an input field, you simply hover the mouse over it and then click the left mouse button. For example:
The focus is now in the field and you can now enter the desired text.
Repeatable Parts
Layouts can have repeatable parts. For example, a layout that renders a tab might allow you to add extra tabs. When more than one repeatable part has been added, you can change the order in which they appear by moving them. Extra repeatable parts that have been added can also be removed.
When a layout contains repeatable parts, the Actions menu becomes available. For example:
You can perform the following tasks using the Layout Actions menu:
| Action | Description |
|---|---|
| Add | Add another instance of the repeatable layout part. |
| Remove | Remove the selected repeatable layout part. |
| Move to Left | Moves the selected repeatable layout part one position to the left. |
| Move to Right | Moves the selected repeatable layout part one position to the right. |
Selecting Layout Variants
When there are one or more variants for a layout, you can select it from the first drop-down list left of the [Actions] button. For example:
Expand the drop-down and select the variant you want to add to the canvas.
Switching Layouts
The following applies to XperienCentral versions R41 and higher.
After selecting a layout, you can switch to another using the drop-down to the left of the Layout Variant drop-down. For example:
Expand the drop-down and select the layout you want to add to the canvas.
Layout Switching Logic
When you switch from one layout to another, XperienCentral maps the fields from the original layout to the one being switched to in the most logical way possible. Because layouts can vary widely, switching from one layout to another can correspondingly have widely varied effects. Depending on the circumstances under which you switch to another layout and what you've already done in the layout you're switching from, there are a number of things to consider. For example, if you have already filled content into one or more fields and/or if there exist prefilled fields at the time you switch to another layout, you could lose content.
- For best results, switch first to the other layout in order to determine whether that leads to undesired results. If it does, switch back immediately to the original layout in order to restore the data in all the filled in/prefilled fields you have modified.
- When switching between layouts, do not save the content item until you are satisfied with the results. A save action makes it impossible to switch back to the original layout while at the same time restoring the data you filled into fields.
The following table explains how XperienCentral handles a layout switch and how fields and loops from one layout are mapped to another (or not). The mapping logic takes into account what is available in the structure of the layout being switched to and then applies the rules described below.
| Field | Available field | Mapped |
| prefilled field | empty field | Determined by the field type mapping rules described below. |
| empty field | prefilled field | Determined by the field type mapping rules described below. |
| prefilled field | prefilled field | Determined by the field type mapping rules described below. |
| rich text | rich text single line | No |
| rich text | single line (flat) | No |
| rich text single line | rich text | Yes |
| rich text single line | single line (flat) | No |
| single line (flat) | rich text | Yes |
| single line (flat) | rich text single line | Yes |
| Field with name A | Field with name A | Determined by the field type mapping rules described above. |
| Field with name A | Field with name B | Determined by the field type mapping rules described above. |
| Prefilled field with name A | Prefilled field with name A | Determined by the field type mapping rules described above. |
| Prefilled field with name A | Prefilled field with name B | Determined by the field type mapping rules described above. |
| Loop | Available loop | Mapped |
| Single loop | Multiple loops | The single loop is mapped to the first of the multiple loops. |
| Multiple loops | Single loop | The first of the multiple loops will be mapped to the single loop. The rest of the loops will be lost. |
| Singe or Multiple loops | No loops | No - all loops will be lost. |