Slots are containers that you can use to display and manage dynamic items on your Web site. In essence a slot acts as a dynamic placeholder that either waits for content (a passive slot) or calls out for it (an active slot). The content is dictated by a scenario that is either using an Add Items to Slot action or a targeter to fill the slot content. Either of these elements of a scenario can reference a specific repository item (content) or point to a repository with a bunch of content in it (content repository). Slots and scenarios work in tandem with each other to deliver content to the page; renderers specify the presentation of the content.
Slots are defined and managed using the ACC. Like renderers, slots are designed for one type of content only. This means that a slot of type Media-image can only contain images. It cannot contain content from the Solutions repository. It is not recommended that you feed content to a slot using more than one scenario for the offer management panels. In general, use one scenario to fill a slot. Using multiple scenarios to fill a slot could give you unpredictable results if they are not configured correctly.
Because you can use offer management with both internal and external users, it is important to configure the slots and scenarios appropriately. Several slot properties are of particular importance when creating slots for use in the Service Center. You can read much more about slots and slot properties in the Using Slots chapter of the ATG Personalization Programming Guide but it is important to understand how to work with the following slot properties for offer management.
