Adding a custom Footprint for the Preview tab
In addition to the Footprints that ship with the product, you can create custom Footprints to display in the Preview tab.
- When to create custom Footprints
This topic explain when and why you would create custom Footprint. - Custom Footprint example
This example shows two custom Footprint elements, one with a closed set of values, another with a free text value restricted by a regular expression. - Configuring a custom Footprint text field
Users can enter any string they want in a Footprint text field, but you can use regular expressions or a fixed set of values to restrict which values are valid, and you can set a minimum and/or maximum length. - Configuring a custom Footprint radiobutton field
Users can pick an option from a Footprint radiobutton field. - Configuring a custom Footprint dropdown or select box field
Users can pick an option from a Footprint dropdown field. - Configuring a custom Footprint date field
Users can pick an option from a Footprint date field. - Creating a custom Footprint field with a custom input control
If none of the standard controls offered out of the box are suitable for your Footprint, you may choose to implement a custom input control. Use the GUI extension mechanism of SDL Tridion Sites to define, configure and implement your custom input control. Then configure one or more custom Footprint fields that use the control. - Configuring a custom cookie name for custom Footprint Claims
If you configured Claim forwarding in the Ambient Data Framework for custom Footprints, you may have chosen to configure a different cookie name than the default,TAFContext. If so, you must also configure that custom cookie name in the Experience Manager configuration. - Migrating Footprints to the new publishing framework
If you use Footprints and if you are migrating your implementation from the deprecated publishing framework to the new publishing framework introduced in SDL Web 8, run a migration tool to ensure that the Footprints continue to work.