Using Business Manager, you can import existing content slot configurations to use with a new instance, and export them for transfer between instances. The slots themselves are not imported or exported, but are defined within page templates (in UX Studio). Slot configurations only reference those slots (using the slot ID). This is controlled by the elements in the slot.xsd.
A slot configuration can belong to zero or one site. A slot configuration that doesn't belong to a site is like a reusable part waiting to be used by the site. A slot configuration can be assigned to zero or one campaigns or promotions. The schedule, rank, and qualifier elements are part of the assignments.
| Elements/attributes | Impact |
|---|---|
| <slot-configuration> | When importing a <slot-configuration> element in MERGE mode, the system checks to see if there is an existing slot configuration with the same ID in the current site domain. If so, the import process updates the existing one; if not, one is created. |
| <rank>, <schedule> or <customer-groups> | If the import file includes any of the deprecated elements <rank>, <schedule>, or <customer-groups>, the system can only update them if there is an explicit SlotConfigurationAssignment between the slot configuration and the site. If there is one, the import process updates those attributes of the assignment; if there is none, the import logic logs a warning. |
| <slot-configuration-assignment> | When importing a <slot-configuration-assignment> element in MERGE mode, the system checks to see if there is an existing assignment between the specified slot configuration (identified by a compound key consisting of slot-id, context, context-id, and configuration-id) and the current site (derived from the import/export context, not specified in the file). If an assignment already exists, it's updated; otherwise one is created. |
| <slot-configuration-campaign-assignment> | When importing a <slot-configuration-campaign-assignment> element in MERGE mode, the system checks to see if there is an existing assignment between the specified slot configuration and the campaign (specified by campaign-id). If an assignment already exists, it's updated; otherwise one is created. If the import is performed in a different import mode, the usual modified semantics apply. |
| <mode> | There is a new mode attribute in the existing <slot-configuration> element. This mode attribute is used for deleting individual objects without doing a full DELETE mode import. The <slot-configuration> element offers special wildcard behavior for deletion. The context, context-id and configuration-id can be omitted in delete mode. You can use this to delete multiple slot configurations simultaneously. |
| <slot-configuration-assignment> and <slot-configuration-campaign-assignment> | The new elements <slot-configuration-assignment> and <slot-configuration-campaign-assignment> support a delete mode, but not a wildcard deletion, such as described previously. With this method, you can only delete one assignment at a time. As a result, the attributes context, context-id, and configuration-id are required for these elements. |