Atg Merchandising User Guide

atg
Version 2007.1
Merchandising User Guide
ATG
One Main Street
Cambridge, MA 02142
www.atg.com
ATG Merchandising User Guide

Document Version
MERCH2007.1 USERGUIDEv2 8/31/07
Copyright
Copyright 1998-2007 Art Technology Group, Inc. All rights reserved.
This publication may not, in whole or in part, be copied, photocopied, translated, or reduced to any electronic medium or machine-readable
form for commercial use without prior consent, in writing, from Art Technology Group, Inc. (ATG) ATG does authorize you to copy
documents published by ATG on the World Wide Web for non-commercial uses within your organization only. In consideration of this
authorization, you agree that any copy of these documents which you make shall retain all copyright and other proprietary notices
contained herein.
Trademarks
ATG, Art Technology Group, and DYNAMO are registered trademarks of Art Technology Group, Inc.
ATG Wisdom, ATG Dynamo Application Server, ATG Adaptive Scenario Engine, ATG Scenario Personalization, ATG Portal, ATG Commerce,
ATG Content Administration, ATG Data Anywhere Architecture, ATG Search, ATG Response Management, ATG Merchandising, ATG
Knowledge, ATG Self Service, ATG Commerce Assist, ATG Advisor, ATG Forum and ATG Business Control Center are trademarks of Art
Technology Group, Inc.
Microsoft, Windows and Word are the trademarks or registered trademarks of Microsoft Corporation in the United States and other countries.
IBM, AIX, and MQ-Series are the trademarks or registered trademarks of IBM Corporation in the United States and other countries. Oracle is a
registered trademark, and other Oracle product names, service names; slogans or logos referenced in this document are trademarks or
registered trademarks of Oracle Corporation. Adobe Acrobat Reader is a registered trademark of Adobe. CORBA is a trademark of the OMG
(Object Management Group). Java and all Java-based trademarks and logos are trademarks or registered trademarks of Sun Microsystems,
Inc. in the United States and other countries. Primus, and its respective logo, and Primus Knowledge Solutions, are trademarks, registered
trademarks, or service marks of Primus.
This product includes software developed by the Apache Software Foundation (http://www.apache.org/).
EditLive Authoring Software Copyright 2004 Ephox Corporation. All rights reserved. Includes code licensed from RSA Security, Inc.. Some
portions licensed from IBM are available at http://oss.software.ibm.com/icu4j/. Includes software developed by the Apache Software
Foundation (http://www.apache.org/). Contains spell checking software from Wintertree Software Inc.. The Sentry Spell Checker Engine
2000 Wintertree Software Inc..
All other product names, service marks, and trademarks mentioned herein are trademarks of their respective owners.
No Warranty
This documentation is provided as is without warranty of any kind, either expressed or implied, including, but not limited to, the implied
warranties of merchantability, fitness for a particular purpose, or non-infringement.
The contents of this publication could include technical inaccuracies or typographical errors. Changes are periodically added to the
information herein; these changes will be incorporated in the new editions of the publication. ATG may make improvements and/or changes
in the publication and/or product(s) described in the publication at any time without notice.
Limitation of Liability
In no event will ATG be liable for direct, indirect, special, incidental, economic, cover, or consequential damages arising out of the use of or
inability to use this documentation even if advised of the possibility of such damages. Some states do not allow the exclusion or limitation of
implied warranties or limitation of liability for incidental or consequential damages, so the above limitation or exclusion may not apply to
you.
ATG One Main Street Cambridge MA 02142
617.386.1000 phone 617.386.1111 fax www.atg.com
Contents
Introduction
Users of this Guide

Finding What You Need
9
9
Overview of ATG Merchandising

ATG Merchandising Terminology
Search Terminology
Using Standard or Custom Catalogs
Using Projects
Creating Projects That Access ATG Merchandising
Working on Tasks
Adding Assets to the Project Tab
Reverting Changes Made to an Asset in the Current Project
Advancing from One Task to Another
Deploying Assets in a Project
Using Dynamic Search and Navigation
Using Search Merchandising
Where You Perform Merchandising Activities
Getting Started
Installing ATG Merchandising
Configuring an Evaluation Content Administration Database
Creating Versioned Core Commerce Tables
Creating Versioned Business Commerce Tables
Creating Versioned Search Tables
Creating Versioned Custom Catalog Tables with Search Support
Importing Required Content
Configuring a Purchased Content Administration Database
Running ATG Merchandising
Assembling and Deploying Applications
ATG Merchandising Modules
Removing ATG Merchandising
Destroying ATG Merchandising Database Tables
Configuring ATG Merchandising

Configuring Deployment Resources
13
13
16
17
17
18
18
19
19
19
20
21
22
22
25
25
26
27
28
29
29
30
31
32
32
33
35
35
39
40
iii
Contents
Configuring Workflows
Deployment Options
Setting Up User Accounts and Roles
Configuring AccessControlServlet
Configuring Custom Catalogs
Working with Secured Repositories
Using Secured Repositories
Using Unsecured Repositories
Modifying Views
Working with Prices
Structuring the Search Configuration Tree
Where to Begin
Sample Types of Trees
The Order of Assets in the Tree
Implicit Language Inheritance
Administering Search Merchandising
Managing the Properties in the Property Prioritization Tab
Configuring Language Support
Configuring the Segment Dimension
Managing Search Configuration Folders
41
42
43
44
44
45
46
47
47
48
48
49
49
52
54
55
55
56
58
59
Using the ATG Merchandising User Interface
61
Setting Up Internet Explorer

Accessing the ATG Merchandising UI
Browsing ATG Merchandising in Read-Only Mode
Working in ATG Merchandising
ATG Merchandising UI Basics
Types of Assets and Buttons
61
61
63
64
65
67
Locating Assets
Using Catalog View
Using Catalog Orphans View
Using Promotions View
Using Coupons View
Using Media View
Using Views for Price Lists
Using Facet View
Using Search Configurations Tree View
Using Base Search Configurations View
Using Search Merchandising Administrative Views
Searching for Assets in the Search Tab
Accessing Assets in the Project Tab
Modifying Assets in the Multi Edit Tab
Accessing Assets in the Details Pane Using the Breadcrumb Dropdown List
71
71
72
73
74
75
76
78
79
80
80
82
84
85
86
iv
Contents
Creating and Organizing Assets
89
Creating Original Assets

Creating Catalog Folders
Creating Catalogs
Creating Categories
Creating Products
Creating Media Assets and Folders
Creating Promotions
Creating Coupons
Creating Price Lists and Price List Folders
Creating Search Configurations and Base Search Configurations
Creating Facets
Creating SKUs and Configurable SKUs
Creating SKU Links
Creating Configurable Properties
Creating Configuration Options
Creating Assets Based on Existing Assets
Linking Assets
Unlinking Assets
Moving Assets
Moving Catalog Folders or Price List Folders to the Top Level
Moving Search Configurations and Search Configuration Folders
90
90
91
92
93
94
96
98
99
101
103
105
106
106
107
108
109
110
111
112
112
Modifying and Previewing the Properties of Assets in a Catalog115

Modifying Assets Individually
Modifying Assets in Bulk
Adding Assets to the Multi Edit Tab
Modifying Assets Sequentially
Modifying All Assets in a List at Once
Applying One Set of Property Values to Several Assets at Once
Previewing Assets
Undoing Property Value Changes
Defining Promotions
Building Discount Rules
Defining a Promotion for a Particular Asset
Specifying When a Promotion is Active
Updating Other Promotions Properties
Updating Closeness Qualifier Properties
Updating Upsell Actions
Updating Coupon Properties
10 Using and Defining Price Lists

Modifying Price List Properties
Providing Prices to Products or SKUs
Defining Volume Pricing
115
116
117
117
119
121
124
124
127
127
128
128
129
133
134
135
137
137
138
140
v
Contents
Providing Price Lists to Users

Assigning Price Lists to Users
Assigning Price Lists to Organizations
11 Defining Facets
Designing A Site With Multiple Facets
Common Collaborative Facets
Facets: Independent or Nested?
Products Included in Facets
Setting General Facet Properties
Setting the Defining Selections Property
Using One Selection for Each Faceting Property Value
Using Dynamic Selections
Using Guided Selection Ranges
Using Specified Selections
Specifying a Selection Sort Order
Managing Nested Facets
12 Defining Search Configurations

Inheriting Settings From Base Search Configurations
Defining Rules
Creating a New Rule
Specifying the Condition
Specifying the Action
Disabling and Deleting Rules
Applying Inherited Rules
Specifying the Priority of Properties
Specifying the Ranking of Property Values
Copying Prioritization Settings from Another Search Configuration
Applying Inherited Prioritization Settings
13 Removing Assets
How Asset Deletions Work
Deleting Parents From the Catalog
Deleting Media Folders With Children
Deleting Base Price Lists
Deleting Search Merchandising Assets
Deleting Facets with Nested Facets
Deleting Assets
Deactivating Promotions
14 Customizing the ATG Merchandising User Interface

Creating Workflows
Customizing Views
Modifying Tree Views
Modifying List Views
140
141
141
143
143
144
145
147
149
149
150
151
153
153
154
154
155
156
156
157
158
162
164
164
165
166
168
169
171
171
172
172
173
174
174
174
175
177
177
178
178
179
vi
Contents
Working with Resource Bundles

Defining the UI for Tasks and Activities
Merchandising-Specific Task Configuration Manager
The Merchandising Task Configuration File
Appendix: Asset Properties

Base Properties
Properties Unique to Standard Catalogs
Properties Unique to Custom Catalogs
Properties Unique to Business Commerce
Base Properties Unique to ATG Search
Properties Unique to ATG Search and Business Commerce
Index
180
180
181
181
193
193
204
206
216
217
218
220
vii
Contents
1 Introduction
Business users create and refine commerce catalogs using ATG Merchandising. When you use ATG
Merchandising, you set up catalogs and populate them with categories, products and SKUs. Your
products and SKUs may also have images and copy that need to be created, refined, and ultimately
deployed to your live Web site.
Each task performed in a catalog is tracked in a project. There are several benefits to this approach. For
one, the changes you make to your products, for example, are saved as discrete versions. You can view
old versions as well as merge two versions to create a new one. Also, since each project has a defined set
of tasks, when you finish your task, your project advances to the next task. For example, after you update
a product description, the project advances to the copy review task, which is a task that might be
performed by another user. In this way, ATG Merchandising automates the catalog development process
relying on the features of ATG Content Administration.
This guide covers the following topics:
Overview of ATG Merchandising
Describes ATG Merchandising key concepts and resources.
Getting Started
Provides instruction to administrators for installing an evaluation and a purchased
copy of ATG Merchandising.
Configuring ATG Merchandising
Explains how to set up a purchased copy of ATG Merchandising.
Using the ATG Merchandising User Interface
Describes the features of the main ATG Merchandising UI and how to access it.
Locating Assets
Details the places where you can find the assets you want modify.
Creating and Organizing Assets
Explains how to create individual, duplicate, link, unlink, and move assets.
Modifying and Previewing the Properties of Assets in a Catalog
Describes how to update individual property values as well as values on several assets
at once. Also, describes how to overwrite values provided in the current project with
those from the last.
Defining Promotions
Supplies set up instructions for promotions.
Using and Defining Price Lists
Provides the information you need to set up price lists and assign them to users.
8
1 - Introduction
Defining Facets
Describes how facets work and the configuration options available to them.
Defining Search Configurations
Explains the rules and settings on a search configuration used to control the list of
products or SKUs that display as search results to customers.
Removing Assets
Explains how to delete assets and de-activate promotions as well as provides
background information on deletions.
Customizing the ATG Merchandising User Interface
Explains how to customize workflows, views, UI labels, and asset types as well as
describes how to control the inclusion of existing screen elements and asset
properties.
Describes the properties on an asset in a catalog and how to update them.
Users of this Guide

This guide is written for merchandisers, that is, the set of business users tasked with creating and
maintaining a product catalog visible on a Web site. All of the information they need to know to work
with ATG Merchandising is documented in this guide. Before they begin using ATG Merchandising, its a
good idea for them to familiarize themselves with the features of this product by reading through the
introductory chapters of this guide.
That said, there are a few chapters written for a more technical audience. Site administrators, who are
responsible for installing and configuring ATG Merchandising, can refer to the Getting Started and
Configuring ATG Merchandising chapters for instructions on startup processes. The Customizing the ATG
Merchandising User Interface chapter is designed for programmers who want the tailor the UI to the
specific needs of the internal users they support.
Finding What You Need

The ATG Merchandising application relies on features in ATG Commerce and ATG Content Administration.
You can find instructions for working with these products in a variety of places. Heres a key to finding the
information you need:
9
1 - Introduction
Task
Audience
Guide
Developing catalogs and their

categories, products, and SKUs
(also called commerce assets) in
a content management
environment that uses projects
to manage the tasks you
perform and maintains versions
of the assets you edit.
Business Users
Covered in several chapters

in this guide
Accessing ATG Merchandising
Business Users
See the Using the ATG

Merchandising User Interface
chapter of this guide
Conceptual information about

projects, workflows, noncommerce assets and other
content management terms.
All
See the ATG Content

Administration Guide for
Business Users
Description of the ATG Business

Control Center user interface
and the content management
features it provides.
Business Users
See the ATG Content

Business Users
Accessing ATG Business Control

Center
Business Users, Site

Administrators
See the Accessing the ATG

Business Control Center
section in the ATG Content
Business Users
Creating a catalog and

populating it with categories,
products and SKUs in a noncontent management
environment.
Business Users
See the ATG Commerce

Catalog Administration
chapter of the ATG Commerce
Guide to Setting Up a Store
Working with all out-of the-box

commerce features, such as
promotions, price lists, and
coupons.
Business Users

in this guide
Tailoring the search results that

display to site visitors based on
their characteristics by building
a tree of search configurations.
Business Users, Site

Administrators

in this guide
Creating facets and defining

selections.
Business Users

in this guide
10
1 - Introduction
Developing JSPs that implement

facets in site pages.
Page Developers
See the Dynamic Search and

Navigation chapter of the
ATG Commerce Search Guide
Technical description of
catalogs, categories, products,
SKUs and other Repository
Items.
Page Developers, Programmers

Catalog Administration
Guide to Setting Up a Store
Accessing ATG Control Center
Page Developers, Programmers
In the Windows Start menu,

select Programs > ATG
2007.1 > Tools > ATG
Control Center
Building JSPs that use

Commerce servlet beans.
Page Developers
See the ATG Commerce Guide

to Setting Up a Store
Starting up ATG Merchandising
Site Administrators
See the Running ATG

Merchandising section of this
guide
Installing database tables in

support of ATG Merchandising,
ATG Commerce, and ATG
Content Administration
Site Administrators
The process is outlined in the

Getting Started chapter of this
guide and includes a cross
reference to the ATG Content
Administration Programming
Guide
Understanding and configuring

site services for generating
search configurations and
associating them with search
queries.
Site Administrators,
Programmers
See the Search Merchandising

Search Guide
Customizing the ATG Business

Control Center
Programmers
See the ATG Content

Administration Programming
Guide
Extending ATG Commerce

programmatically by creating
subclasses and modifying
repositories. Integrating with
CyberCash, CyberSource, and
TAXWARE. Communicating with
ATG Commerce through Web
Services
Programmers

Programming Guide
11
1 - Introduction
12
1 - Introduction
2 Overview of ATG Merchandising
ATG Merchandising is designed for ATG Commerce users who want to use ATG Content Administration
tools for building catalogs and deploying them to a live site. Using ATG Merchandising, business users can
develop subcatalogs, categories, products, and SKUs and organize them in catalogs that exist in a content
management environment.
There are two main advantages provided by an environment such as this one. First, the activities you
perform in your catalogs are identified as tasks in a project that is managed by ATG Merchandising. Once
you finish a task, which might involve editing copy for a product, you advance the project so that the
person who is responsible for the next task in the workflow, for example -approving your copy change - is
made aware of the pending project. In this way, the process of developing merchandising assets is
automated.
The second advantage of a content management system is that you can save versions of each asset in a
catalog or of the catalog itself. For example, you may not know which image is best for a given product
image. You can create multiple images so that your manager can select her preference. And if you need to
make minor modifications to an image, you save your changed file as a new version of an existing asset.
Its possible to maintain versions of media assets, such as the image described earlier, as well as versions
of the set of properties describing an asset.
Before using ATG Merchandising, review the following topics:
Using Projects

ATG Merchandising introduces several terms that are new even to customers familiar with ATG Content
Administration and ATG Commerce. Before reading this section, review the terminology defined for those
products so that you have the foundation you need to understand the terminology defined here:
See the ATG Commerce Catalog Administration chapter of the ATG Commerce Guide to
Setting Up a Store
13
2 - Overview of ATG Merchandising
See the ATG Content Administration Overview chapter of the ATG Content Administration
Guide for Business Users
The following concepts are unique to ATG Merchandising or have a definition that is unique to ATG
Merchandising:
Commerce Asset
A commerce asset is an asset you use to build a commerce Web site and whose lifecycle is managed by
projects. Some commerce assets, such as catalogs, categories, products, SKUs, configurable SKUs,
promotions and media assets, will display on your live Web site, while others, such as catalog folders,
media folders, and media-external assets, are used to organize assets in your development environment.
In technical terms, commerce assets are the RepositoryItems provided by ATG Commerce used in the
versioning environment provided by ATG Content Administration. Unlike assets in ATG Content
Administration, all commerce assets are repository assets, meaning they reside in a versioned database,
even though some assets, such as categories, products, and SKUs, live in a SQL repository while other
assets (media assets) live in a content repository.
Catalog
A catalog organizes your commerce assets in a hierarchy that reflects the way users will navigate to them
on your live site. If your site uses standard catalogs, meaning the site presents one catalog to all users, the
catalog itself is not a commerce asset, but a conceptual principle. If your site uses custom catalogs and
employs several catalogs, each of which is tailored to the needs of a unique user segment, a catalog is a
commerce asset that you can create, modify, and delete in ATG Merchandising. A catalog existing in
another catalog may be called a subcatalog, although it is technically identical to a catalog.
Media Asset
A media asset is a type of commerce asset that either includes an external file, content from an external
file, or a pointer to an external file. There are three types of media assets:
Media-internal-binary assets include a binary file, such as an image.
Media-internal-text assets include a block of text, such as text from a JSP.
Media-external assets include a link to an image or a text file, such as a JSP.
Although media assets are organized into media folders outside of the product catalog context, media
assets are typically associated with assets in a catalog; for example, the image of a SKU on the Web site is a
media internal asset associated with the SKU. Unlike other commerce assets, media assets must always
have one and only one parent. Media assets must exist in folders called media folders.
Catalog Folder and Media Folder
A folder is a type of commerce asset used to organize other commerce assets in ATG Merchandising.
Folders arent published to your Web site. Unlike other commerce assets, folders can exist anywhere in
the hierarchy, including at the top level (also called the root level) of the hierarchy. Folders that contain
media assets are called media folders. Customers who use custom catalogs must keep catalogs in catalog
folders.
Parent
A parent is any commerce asset that contains nested assets. Catalog folders, catalogs, categories,
products, and media folders can be parents to other assets. You can think of an assets parent as the place
in the catalog structure where that asset lives. For example, a blender product resides in the Kitchen
14
Electronics category so Kitchen Electronics is a parent to the blender. That same blender may have
another parent, such as the Wedding gifts category, demonstrating that a commerce asset can have
multiple parents. An asset without parents is an orphan, visible in the Catalog Orphans view, rather than
Catalog view.
Orphan
An orphan asset is a commerce asset that can exist in a catalog, but hasnt been added to the hierarchy.
Assets turn into orphans when you remove them from the catalog hierarchy or create them without
specifying a location for them to reside in. Such assets are considered to be orphans, visible in the Catalog
Orphans view, because they have no parents. Any asset can be an orphan except those that require a
parent at all times (media assets) or those that never require a parent (catalog folders and media folders).
You must incorporate orphaned assets into your catalog before you deploy them if you want them to be
visible to site users in your catalog hierarchy.
Price List
A price list is an asset that refers to a set of prices assigned to products or SKUs that are visible to a set of
users. Price lists support three pricing options:
a single price applied to all items,
a group of prices and quantities, so the price used for all items is based on the quantity
purchased, and
a group of prices and quantity range so that one price is used for some items and
another is used for others.
One price list can inherit prices from another price list, so when you create a pricelist, you will often select
a base list, then override inherited prices as needed.
Linking and Unlinking
One of the main tasks performed by a merchandiser is organizing a catalog into a structure thats
appropriate for the Web site. When you add a commerce asset to a catalog, you create a link between the
asset you are moving and another asset, called a parent, that will contain it. Its possible for a single
commerce asset to appear in multiple parts of the catalog so that a change to the asset in one location is
reflected everywhere that asset is used. You add an asset to a new location by creating a link, and you can
remove an asset from a location by unlinking it. Removing all of an assets links or parents turns it into an
orphan and removes it from the catalog structure. The link and unlink operations do not apply to media
assets because they always require a parent.
Workflow
A workflow defines a list of tasks and task actions, and organizes them into a sequence. When you create a
project, you select a workflow for it. ATG Merchandising comes with one commerce workflow that refers
to other workflows for deployment instructions, which is one difference between how workflows work in
ATG Merchandising and ATG Content Administration. For more information on ATG Merchandising
workflows, see Configuring Workflows.
Content Administration Database
The content administration database, also called the versioned database, is the database that stores
merchandising content in a development environment. This database can contain asset versions, which is
different from the production database that supports the live site and contains only the deployed version
of an asset. The difference between the content administration database configured for ATG Content
Administration and ATG Merchandising is the ATG Merchandising version contains additional tables in
15
support of commerce assets. ATG Merchandising comes with a SOLID database that you can set up as a
content administration database and use when you are evaluating the product.
Search Terminology
The following concepts are unique to Dynamic Search and Navigation and Search Merchandising, which
are features in ATG Merchandising that are available only to those users who also have ATG Search:
Search Configuration
A search configuration contains rules and settings that affect how site search results display to a group of
site visitors. Each search configuration has a particular language or user segment called a dimension that
acts as a filtering device. A search configuration applies to only those visitors who meet the language and
segment restrictions.
Base Search Configuration
A base search configuration is a search configuration that acts as a template by providing settings that are
inherited or overridden in the search configurations that use it.
Search Configuration Folder
A search configuration folder is a folder that organizes search configurations into a tree structure.
Different from other folders, a search configuration folder has a dimension that restricts the site visitors
who access the search configurations it contains. In order for a search configuration to be applied to a
visitors search results, that visitor must be part of the language or segment groupings defined by the
search configuration and its parent search configuration folders.
Dimension
A dimension is a characteristic that governs the visitors whose search results are affected by a given
search configuration. Two types of dimensions are possible:
Language dimensions limit access based on a visitors language
User segments group users based on profile characteristics
Search configuration folders always specify a dimension, and the assets they contain - regardless of
whether they are search configurations or search configuration folders - must specify a value for that
dimension.
Facet
A facet is an asset available to users who have ATG Search and ATG Merchandising. Use facets to design
virtual groupings (selections) of products based on a product property. Site pages that use facets show a
range of selections named for product property values or letters in the alphabet that represent them. By
clicking an A-C selection, you view products, for example, that have a manufacturer name that begins
with those letters. A facet may organize all products on your site or a subset of products, for example,
those contained within a given category: the products available to a facet depends on whether your facet
is global (associated with the Global Facets folder) or local (associated with a specific catalog or category).
16

When you design your commerce Web site, you decide whether you want your site to have one catalog
viewed by all users (standard) or multiple catalogs, each of which is designed for a particular audience
(custom). For example, a site might use multiple catalogs to accommodate the following situations:
Provide a unique selection of products in each catalog.
Organize the same products in categories that are unique to each catalog.
Vary the image and copy for products in each catalog.
For more information on standard and custom catalogs, see the ATG Commerce Programming Guide.
All features provided in standard catalogs are available in both models. Additional features are provided
in custom catalogs.
In the standard catalog model, a catalog is a general concept that represents the container for your
categories, products, and SKUs. Customers who use custom catalogs see additional asset types in ATG
Merchandising called catalog and catalog folder that they can use to define and organize separate
catalogs tailored to the needs of specific site users. In the custom catalog model, you can move the assets
from one catalog to another or link most assets across catalogs, the only limitation being that categories
and catalogs must be unique to a catalog. Also, customers using custom catalogs have properties used to
display catalog-specific information for categories, products, and SKUs.
Pricing is handled differently in the two types of catalogs. Each SKU in a standard catalog can have several
prices a sale price, a wholesale price, for example. In general one price is active at a time for all
customers. In custom catalogs, prices for various products of SKUs are organized into price lists that are
visible to visitors who are part of a given organization. Price lists can use a complex pricing scheme that
alters the price of a SKU based on the number of items being purchased. For more information, see
Working with Prices.
Know that standard and custom catalogs are available to the ATG Commerce products that you use in
conjunction with ATG Merchandising: ATG Consumer Commerce and ATG Business Commerce. By
default, ATG Consumer Commerce uses standard catalogs and ATG Business Commerce uses custom
catalogs, but you can alter the default configurations.
Using Projects
When you work with assets, you do so in the context of a project. Your projects dictate what you see in
ATG Merchandising and the tasks, such as content creation, review, and deployment, you are permitted
to perform in it. Projects ensure that tasks are performed in the appropriate order.
All merchandising activities are conducted as part of a project. Making a change to an asset automatically
adds it to a project and, consequently, the Project tab, which holds all assets that are being modified in
the current project. Deploying a project replaces the live assets on your Web site with the version of them
in the project. Although you can modify assets in the Browse tab, Search tab, Project tab or the Multi Edit
tab, and your modifications will be reflected in all four, only in the Project tab can you revert your
modifications so that an asset will not be deployed with the project.
17
You interact with projects in the following ways:

Working on Tasks
Reverting Changes Made to An Asset in the Current Project
Advancing From One Task to Another
If you want to view ATG Merchandising, you can do so outside of the context of a project. See Browsing
ATG Merchandising in Read-Only Mode for instructions.
For general information about projects, see the Creating and Managing Projects chapter of the ATG
Content Administration Guide for Business Users.

When you want to access ATG Merchandising, you select a task in an ATG Merchandising project. If an
appropriate project doesnt exist already, you can create a new one by selecting a workflow. A workflow is
a template for a project that determines the tasks available in the project, the order in which they are
executed, and the actions used to advance from one task to the next.
In order to work with commerce assets, you must create projects based on one of two workflows in the
ATG Business Control Center Operations list beneath the Merchandising menu selection. The Manage
Commerce Assets workflow provides access to all parts of ATG Merchandising used for creating,
modifying, organizing, and deleting commerce assets. The tasks in this workflow are identical to those in
Administer Commerce Search, the second workflow provided out-of-the-box, the difference being the
assets and views visible in each. Administer Commerce Search provides tools used by administrators who
are tasked with configuring ATG Search with ATG Merchandising. To learn more about administrative
tasks, see Administering Search Merchandising.
For instructions on creating projects, see the Creating and Managing Projects chapter of the ATG Content
Administration Guide for Business Users.
You can learn more about workflows by reading Configuring Workflows.
Working on Tasks
Each project contains a preset list of tasks, each of which can be assigned to a user. The tasks represent
activities you perform in ATG Merchandising. The user assigned to a task or, if no user is specified,
administrators are the only users permitted to perform a given task in a particular project.
The first task in an ATG Merchandising project is Author. The Author task permits you to access ATG
Merchandising and create, modify, and delete commerce assets. In order to perform the Author task, you
select a project in the ATG Business Control Center and click the Author task, which automatically opens
ATG Merchandising. In ATG Merchandising, you can see your project and task on the top portion of the
screen.
18
What you see in the ATG Merchandising UI depends on the task and project you are working in. By
default, the Author task provides unrestricted access to all functions in ATG Merchandising. The Review
Content task and the Deploy Now or Later task, however, let users view assets, but prevents users from
modifying them by hiding buttons and making textboxes read-only.

When you make changes to assets, those assets appear in your current project and are visible from the
Project tab. The Project tab holds all assets you have modified or intend to modify in a given project. You
can think about the Project tab as a workspace for all the assets you want to work with in the project and
later, will deploy to your live site. If there are assets you intend to modify, you can add them to the Project
manually:
1.
Locate assets you want to add. See the Locating Assets section for ways to find assets.
2.
Click the checkbox beside each asset.
3.
Click the Add to Project button.
Any asset thats in the Project tab when you deploy the project will appear on the Web site. For more
information on the Project tab, see the Accessing Assets in the Project Tab section.
Reverting Changes Made to an Asset in the Current Project

If you make changes to assets in a project, then decide you want to eliminate those changes, you can do
so using the Remove button in the Project tab. If you delete an asset created in a previous project and
revert your deletion, the asset returns to its pre-project location and state.
Keep in mind that you can revert changes only to assets created in other projects: attempting to undo
changes made to an asset in the project it was created causes all actions associated with that asset to be
reverted, including its creation. Such assets will be permanently deleted.
To revert assets to their pre-project state:
1.
In the Project tab, find the assets that have changes you want to remove.
2.
3.
Click the Remove button.

The assets are removed from the Project tab.
Advancing from One Task to Another

Once youve finished performing your task in ATG Merchandising, you advance the project to the next
task by selecting a task action. Task actions are the possible next steps defined for a task. For example, the
Author task has task actions Ready for Review and Delete Project. By specifying the Ready for Review
action, the Review Content task becomes active and, when the person assigned to the review task views
Projects with My Tasks, this project displays.
Keep in mind that advancing to a new task indicates that all previous tasks are completed. For example,
once you complete your Author task, you will not be able to revise assets in the project before they are
19
deployed, unless the reviewer finds errors and sets the Review Content task action to Reject. You forfeit
control over a project when your task is finished so be certain about your tasks completion before
selecting a task action.
The best way to advance a project from one task to another is by using the Task Action dropdown list
located on the top right portion of the ATG Merchandising UI:
Note that the dropdown list and Go button are visible when you access ATG Merchandising using a task
thats unassigned or assigned to you. You wont see these elements if you use a task assigned to someone
else because you shouldnt be able to advance a project that isnt yours.
To advance to the next task, follow these steps:
1.
From this dropdown list, select a task action.
2.
Click Go.
3.
If necessary, enter a note in the Task Action dialog box.
4.
Click OK.
You are returned to the ATG Business Control Center, which displays information
about your project and its tasks. Notice that the previous task name is no longer a blue
link. The next task now displays as a blue link to users who have permission to perform
it. When clicked, you open ATG Merchandising in that task.
Its also possible to specify task actions from the ATG Business Control Center. See the Managing Tasks
chapter of the ATG Content Administration Guide for Business Users for instructions.

Once the reviewer sets the Review Content task to the Accept task action, your project is ready for
deployment. Deployment is a task like any other and the task actions available to your project are
specified in your workflow. See Configuring Workflows for deployment options.
The deployment task corresponds with the deployment resources you configure ahead of time so that
once you deploy your assets, the following occurs automatically:
The project is checked in.
New versions are generated for the assets in the project, representing the assets
current state. Each new version is represented by a version number.
The new asset versions replace the old ones on the Web site.
If you deploy a project at the same time as another user, changes made in your project may conflict with
those in the other project. For instructions on resolving such conflicts, see the Resolving Asset Conflicts
section of the Creating and Managing Assets chapter in the ATG Content Administration Guide for Business
20
Users. Once a project is deployed, its visible in the ATG Business Control Center, but cant be changed. In a
new project, you can access and alter assets that were created, modified, or deleted in deployed projects.

Users who have ATG Merchandising and ATG Search also have a feature called Dynamic Search and
Navigation that provides tools for designing dynamic navigational elements on your web site. If your site
is an electronics store, for example, you can use this feature to organize TVs by screen size and price. A
user who visits your site sees the following links: 5 - 20 TVs, 21 29 TVs, and 30 39 TVs. Clicking one
link leads a user to a list of pricing links, each of which represents a list of products with a particular screen
size and price.
Screen size and price are both properties of products. You use this feature to create a facet asset that
represents a product property, so your site displays the values of the property as links. You may prefer
separate selections for each property value, for example, one link for 5TVs, another for 13 TVs and so on.
Or, you may prefer to organize a range of selections as demonstrated above.
In ATG Merchandising, you create facets, and decide how facets will organize products into selections and
what products a facet will include in its selections. Some facets are available to all products (global),
where as others are available to a subset of products (local), such as the products in a given category.
Facets can work in tandem with other facets as they do in our example, or may work independently.
You provide all of these guidelines in ATG Merchandising, which are then used in building selections that
contain the appropriate products dynamically. How does that happen? ATG Search interprets the facets
you define as search criteria and produces selections containing products as search results. To site users,
these results appear as links to products.
When you use Search Merchandising and Dynamic Search and Navigation together, ATG Search
incorporates the search configuration settings (created with Search Merchandising) in the search query
text used to produce a list of products. Once that list is produced, ATG uses your facet settings to create
selections and populate them with the appropriate products.
In order to use this feature, an administrative user needs to configure ATG Search to process your facets
and a page developer needs to implement them on site pages, both of which are described in the
Dynamic Search and Navigation chapter of the ATG Commerce Search Guide. The tasks performed by a
merchandising user are explained in the following sections:
Designing a Site with Multiple Facets
Creating Facets
Defining Facets
Removing Assets
21
Users who have ATG Merchandising and ATG Search can also use a feature called Search Merchandising,
which enables Commerce sites to customize search results based on site initiatives and customer
purchasing patterns. For example, Search Merchandising makes it possible for a certain brands products
to appear in search results ahead of other brands, either for all visitors (e.g., if your site is trying to
promote the brand) or for a specific group of visitors who favor that brand. It also enables you to exclude
certain results entirely, such as out of stock or discontinued items.
In ATG Merchandising, you create search configurations, which are sets of rules that control the display of
search results. Depending on how ATG Merchandising is configured for you by your system administrator,
you can create a single search configuration for all visitors at your site, or create different search
configurations for different groups of site visitors. Visitors can be grouped by language (useful if your site
is in multiple languages or has visitors from multiple countries), by user segment (useful for targeting
specific search results to specific visitors), or both.
After you define and deploy search configurations, ATG Search prepares searchable content by indexing
the products, SKUs, and other catalog assets and processes your search configurations. When a visitor
enters a query in a search form on your Commerce site, the software considers the current language and
the user segments the visitor is a member of, and determines which search configuration to apply. The
search results that display and the order they display in reflect the search configuration thats used.
In order to use Search Merchandising, an administrative user needs to configure your Commerce site and
ATG Search to generate the search configurations you define and to apply them to search queries entered
by site visitors. These tasks are described in the Search Merchandising chapter of the ATG Commerce Search
Guide.
This guide covers Search Merchandising in the following sections:
Guidance on architecting a tree of search configuration folders and search

configurations that incorporate base configurations is provided in Structuring the
Search Configuration Tree.
The views you use to access search configurations, search configuration folders, and
base search configurations as well as setup tasks are described in Locating Assets.
All administrative tasks, including creating search configuration folders, are explained
in the Administering Search Merchandising.
Learn how to create search configurations and base search configurations in Creating
Search Configurations and Base Search Configurations.
Specify settings to search configurations and base search configurations from Defining
Search Configurations.

Most tasks performed by commerce business users, such as managing and populating catalogs, are
accomplished in the ATG Merchandising UI. The ATG Merchandising UI is part of the ATG Business Control
Center, which is a Web-based interface that governs all content management activities. Although its
22
possible to create assets in the main portion of the ATG Business Control Center, all commerce assets
should be created, modified, and deleted in the ATG Merchandising UI.
ATG Merchandising users perform some tasks in other user interfaces. Heres a summary of
merchandising tasks and user interfaces you use to perform them:
Merchandising
Activity
Performed in this User

Interface
User Interface
Description
User Interface
Included with
this Product
Work with commerce

projects that involve
developing catalogs
and commerce assets,
such as categories,
products, and SKUs as
well as product images
and copy. Also, creating
and defining
promotions, coupons,
and price lists.
ATG Merchandising UI
A Web-based interface
that lets business users
work with projects to
build and populate
product catalogs in a
content management
environment. This user
interface is accessible
from the ATG Business
Control Center
ATG
Merchandising
Create commerce
projects and deploy
catalogs and assets to a
live site. Also resolving
any version conflicts.
ATG Business Control

Center
A Web-based interface
that lets business users
develop and manage
non-commerce assets in
a content management
environment. Also
provides tools for
managing commerce
and non-commerce
projects and deploying
assets.
ATG Content
Administration
ATG Control Center, also

called the ACC
A client interface
designed for technical
users who create JSPs,
manage users and roles,
and perform other
administrative and
development tasks. Also
used by business users
to design
merchandising
incentives and
implement other
business strategies.
ATG Adaptive
Scenario Engine
See ATG Content

Business Users for more
information.
Create and configure:

- workflows
- gift certificates
- gift lists
- wish lists
See ATG Commerce
Guide to Setting Up a
Store
Note: To use this

product, you must
have ATG
Commerce and
ATG Content
Administration
Note: This
interface provides
support to all ATG
products.
23
24
3 Getting Started
ATG Merchandising is an application that runs on top of the ATG platform. Once you have downloaded
and installed ATG Merchandising, to use the product, you need to start it up and access it through your
browser. ATG provides evaluation copies of its products so you can sample them before making a
purchase. Evaluation products are designed to be easy to start up so they run in a different environment
and use a different database than production products do. If you decide to purchase ATG Merchandising,
you need to configure your product so that you can use it in concert with your live Web site.
The tasks described in this chapter should be performed by a site administrator skilled in installing,
configuring and running technical software. Refer to the following topics for instructions:
Configuring an Evaluation Content Administration Database
Configuring a Purchased Content Administration Database

To use ATG Merchandising 2007.1, you must have the following software installed on your network:
An application server from one of the following vendors: JBoss or WebLogic. For
installation and configuration instructions, see the ATG Installation and Configuration
Guide.
ATG Adaptive Scenario Engine
ATG Commerce
ATG Content Administration
If you want to use the add-on ATG Search features, such as Dynamic Search and
Navigation for creating dynamic groupings of products or Search Merchandising for
controlling which search results display and in what order, you must also install and
ATG Search and Commerce Search. See the ATG Commerce Search Guide for
instructions.
Follow these steps to install ATG Merchandising:

1.
Download one of the following distribution files from the ATG website (www.atg.com):
25
3 - Getting Started
Windows: ATG-Merchandising2007.1.exe
UNIX: ATG-Merchandising2007.1.jar
2.
Run the setup program.
3.
Request the licenses from www.atg.com and, once you receive them, install the
necessary license files into the appropriate local configuration directory. For example:
<ATG2007.1dir>/home/localconfig
Once you have installed ATG Merchandising, you need to configure a database to be used with it. See the
next section for instructions.
Configuring an Evaluation Content Administration

Database
In order to evaluate ATG Merchandising, you need to create the appropriate database tables in SOLID, the
evaluation database provided with your installation. Technically, you can evaluate ATG Merchandising on
any supported database: SOLID is provided as a convenience to you. If you choose to evaluate this
product on a database that already has tables for ATG products, back up your database before running
these scripts because they will overwrite existing tables, removing data and custom code.
There are two main differences between setting up ATG Merchandising for evaluation purposes and for
production use:
The SOLID database provides some configured database tables, so installation and
configuration is easier when you use SOLID.
The evaluation instructions provide the quickest way to access ATG Merchandising by
skipping some steps, such as setting up user accounts and deployment. If you want to
sample these features of ATG Merchandising, see Configuring a Purchased Content
Administration Database.
First of all, make the necessary pre-setup configurations to your database as described in the ATG
Programming Guide. Secondly, create and populate the database tables used by ATG Merchandising, by
following these steps:
1.
Start your database according to the instructions provided by your database vendor.
2.
Create the database tables that support the union of ATG Content Administration and
the ATG Commerce product you are using:
All ATG Merchandising users should see the Creating Versioned Core
Commerce Tables section.
ATG Business Commerce users should also see the Creating Versioned Business
3.
If you have ATG Search and you want to use the Search Merchandising and Dynamic
Search and Navigation add-on features, create the database tables that support the
union of ATG Search, ATG Content Administration, and the ATG Commerce product
you are using:
26
3 - Getting Started
All users should see the Creating Versioned Search Tables.

If you use ATG Business Commerce or ATG Consumer Commerce with custom
catalogs, also see the Creating Versioned Custom Catalog Tables with Search
Support section.
4.
Import ATG Merchandising content into your ATG Content Administration database.
See Importing Required Content.
Creating Versioned Core Commerce Tables

In order to use ATG Merchandising, you need to create database tables. Run the
dcs_versioned_ddl.sql script in the following directory:
<ATG2007.1dir>/DCS/Versioned/sql/install/database-vendor
When installing tables on an evaluation copy of ATG Merchandising, the command takes this format. This
command includes the default arguments used for a SOLID database:
<ATG2007.1dir>DAS\solid\i486-unknown-win32\solsql.exe "tcp 1313"
publishing publishing <ATG2007.1dir>\DCS\Versioned\sql\install\solid\
dcs_versioned_ddl.sql
where <ATG2007.1dir> is the path to your ATG 2007.1 directory, 1313 is the port for your SOLID
database, and publishing is the username and password used for the ATG Merchandising table space
on SOLID.
The tables created by dcs_versioned_ddl.sql have the same names as those created by the script
used to install core Commerce tables called dcs_ddl.sql, the only difference being that some tables
provided by dcs_versioned_ddl.sql have additional columns for storing data on versioned assets.
Those tables are implemented by the individual scripts described in the table below. If necessary, you can
run these subscripts individually from the following directory:
<ATG2007.1dir>/DCS/Versioned/sql/db_components/database-vendor
Script name
Purpose
versioned_claimable_ddl.sql
Creates tables that support the versioning of coupons
versioned_priceLists_ddl.sql
Creates tables that support the versioning of price lists
versioned_product_catalog_ddl.sql
Creates tables that support the versioning of products and

catalogs
versioned_promotion_ddl.sql
Creates tables that support the versioning of promotions
Creating Versioned Custom Catalogs Tables

If you want to run ATG Merchandising and Consumer Commerce with custom as opposed to standard
catalogs or if you want to run the custom catalogs modules on its own, you need to create tables that
27
3 - Getting Started
support versioned custom catalogs in addition to the tables that you create for core commerce. Run the
versioned_custom_catalog_ddl.sql in the following directory:
<ATG2007.1dir>/DCS/CustomCatalogs/Versioned/sql/db_components
/database-vendor
publishing publishing <ATG2007.1dir>\DCS\CustomCatalogs\Versioned\sql\
db_components\solid\versioned_custom_catalog_ddl.sql
on SOLID.
For information on the differences between standard and custom catalogs, see Using Standard or Custom
Catalogs.
Creating Versioned Business Commerce Tables

If you want to use ATG Merchandising with ATG Business Commerce, you need to create database tables
that support the combination of these products, in addition to the tables that you create for core
commerce. Run the b2bcommerce_versioned_ddl.sql in the following directory:
<ATG2007.1dir>/B2BCommerce/Versioned/sql/install/database-vendor
publishing publishing <ATG2007.1dir>\B2BCommerce\Versioned\sql\
install\solid\b2bcommerce_versioned_ddl.sql
on SOLID.
The b2bcommerce_versioned_ddl.sql script executes one subscript,
versioned_b2b_product_catalog_ddl.sql, which creates tables that hold extensions to the Business
Commerce product with support for versioning. If necessary, you can run this subscript from the following
directory:
<ATG2007.1dir>/B2BCommerce/Versioned/sql/install/database-vendor
28
3 - Getting Started
Creating Versioned Search Tables

In order to use the ATG Search add-on features (Search Merchandising and Dynamic Search and
Navigation), you need to create two sets of database tables.
First, create tables that provide versioning support to ATG Search Integration. Run the
versioned_refinement_ddl.sql script in the following directory:
<ATG2007.1dir>/DAF/Search/Versioned/sql/db_components/database-vendor
When installing tables on an evaluation copy of ATG Merchandising on a SOLID database, the command
takes this format. This command includes the default arguments used for a SOLID database:
publishing publishing <ATG2007.1dir>\DAF\Search\Versioned\sql
\db_components\solid\versioned_refinement_ddl.sql
on SOLID.
Second, create database tables that support the union of ATG Merchandising, ATG Commerce and the
add-on ATG Search features. Run the dcs_search_versioned_ddl.sql script in the following directory:
<ATG2007.1dir>/DCS/Search/Versioned/sql/install/database-vendor
publishing publishing <ATG2007.1dir>\DCS\Search\Versioned\sql\install\
solid\dcs_search_versioned_ddl.sql
on SOLID.
Creating Versioned Custom Catalog Tables with Search Support

In order to use ATG Merchandising, ATG Business Commerce and the add-on ATG Search features (Search
Merchandising and Dynamic Search and Navigation), you need to create database tables that support
these products and features. These tables are also required if you use ATG Merchandising, ATG Search,
and ATG Consumer Commerce with custom catalogs. Run the
dcs_search_customcatalogs_versioned_ddl.sql script in the following directory:
<ATG2007.1dir>/DCS/Search/CustomCatalogs/Versioned/sql/
install/database-vendor
29
3 - Getting Started

publishing publishing <ATG2007.1dir>\DCS\Search\CustomCatalogs\
Versioned\sql\install\solid\dcs_search_customcatalogs_versioned_ddl.sql
on SOLID.
The dcs_search_customcatalogs_versioned_ddl.sql script executes one subscript,
versioned_custom_catalog_refinement_ddl.sql, which creates tables that hold extensions to the
Refinement repository with support for versioning catalog assets. If necessary, you can run this subscript
from the following directory:
<ATG2007.1dir>/DCS/Search/CustomCatalogs/Versioned/sql/
db_components/database-vendor
Importing Required Content

In order to use ATG Merchandising, you need to run its import scripts. Note that although you can startup
ATG Merchandising and access it without running these scripts, you wont be able to perform any
activities, such as creating commerce assets. Follow these steps:
1.
Start your database.
2.
Set the DYNAMO_HOME environment variable to <ATG2007.1>/home, if you have not

already done so.
3.
Set the JAVA_HOME environment variable to your Java installation directory, if you
have not already done so.
4.
To import user role and view mapping content used by ATG Merchandising, use:
<ATG2007.1dir>/DCS-UI2007.1/DCS-UI/install/importDCSUIManagement.bat/.sh
5.
To import the information you need to make segments available to ATG

Merchandising, use:
<ATG2007.1dir>/DCS/Versioned/install/importDCSVersioned.bat/.sh
6.
All users who have ATG Merchandising and ATG Search should import the view
mappings used to display search configuration and search configuration folder
information, using:
<ATG2007.1dir>/AssetUI/Search/install/importAssetUISearch.bat/.sh
7.
If you want to use ATG Consumer Commerce in conjunction with ATG Search, import
the necessary view mapping content, using:
<ATG2007.1dir>/DCS-UI2007.1/DCS-UI/Search/install/
importDCSUISearchStandardCatalogs.bat/.sh
30
3 - Getting Started
8.
If you want to use ATG Business Commerce (or ATG Consumer Commerce with custom
catalogs) in conjunction with ATG Search, to import the necessary view mapping
content, using:
<ATG2007.1dir>/DCS-UI2007.1/DCS-UI/Search/install/
importDCSUISearchCustomCatalogs.bat/.sh
Note that you can also import sample property groups, which are groups of properties that you edit at the
same time in the Multi Edit tab. If you dont import property groups, you must create your own property
groups in order to use the Multi Edit tab. Use this command to import property groups:
<ATG2007.1dir>/DCS-UI2007.1/DCS-UI/install/importDCSUIManagement
Examples.sh/.bat
Configuring a Purchased Content Administration

Database
Once you buy ATG Merchandising, you will need to install a production-ready database before you can
begin building your Web application. Follow these steps to set up your database:
1.
Follow the steps provided in the Setting Up a ATG Content Administration Server chapter
of the ATG Content Administration Programming Guide.
2.
Create tables for ATG Content Administration by running the biz_ui_all_ddl.sql

script located in <ATG2007.1dir>/BIZUI/sql/install/database-vendor as
described in the Creating ATG Content Administration Database Tables section of the
Setting Up the ATG Content Administration Database chapter in the ATG Content
Administration Programming Guide.
3.
If you have ATG Search, run the search_ddl.sql script located in

<ATG2007.1>/DAF/Search/Index/sql/db_components/database-vendor to
create tables that support the Search Integration as described in the Creating ATG
Search Database Tables section of the Getting Started chapter in the ATG Commerce
Search Guide.
4.
Create the ATG Merchandising tables necessary for your product suite:
All ATG Merchandising users should see the Creating Versioned Core
ATG Business Commerce users should also see the Creating Versioned Business
5.
If you have ATG Search, create the database tables that support the union of ATG
Search, ATG Content Administration, and the ATG Commerce product you are using:
All users should see the Creating Versioned Search Tables section.
If you use ATG Business Commerce or ATG Consumer Commerce with custom
catalogs, also see the Creating Versioned Custom Catalog Tables with Search
Support section.
31
3 - Getting Started
6.
Import the content required by ATG Content Administration, if you have not already
done so. See the Initialize the Database section of the Setting Up the ATG Content
Administration Database chapter in ATG Content Administration Programming Guide.
7.
Import content into your ATG Content Administration database that configures ATG
Merchandising for use. If you have ATG Search, import an additional script. See
Importing Required Content.
8.
Create tables for other ATG applications you want to use. See the user guides provided
for those applications.

In order to run ATG Merchandising, you need to assemble a J2EE application and deploy it to your
application server. Refer to the following sections:

When you use JBoss or WebLogic as your application server, you need to build a J2EE application that
contains an instance of the modules used by ATG Merchandising. Once youve assembled your
application, deploy the application to the appropriate location and start it up according to the
instructions provided in your application server manuals.
The ATG platform provides an assembly tool that you can use to create your J2EE application. You can
find detailed information about assembling a J2EE application that includes the ATG platform in the ATG
Programming Guide.
To assemble a J2EE application that includes ATG Merchandising, you execute a command in this format:
<ATG2007.1dir>/home/bin runAssembler [options] output-file-name m
module-list
When you build an application that you intend to run with ATG Merchandising, you need to include:
DCS-UI or a submodule of it
PubPortlet
A commerce module that represents a commerce product, such as

B2CCommerce.Versioned or B2BCommerce.Versioned, or a type of catalog (custom
or standard).
The - layer Preview switch, if you want to be able to preview catalog data. For
more information on setting up the preview feature, see the Setting Up Preview
Features chapter in the ATG Business Control Center Administration and Development
Guide.
32
3 - Getting Started
Modules that support the integration of ATG Search, ATG Merchandising, and ATG
Commerce, if you have all three products.
Other modules youve created that contain your custom code
For example, if you want your application to include ATG Merchandising, ATG Content Administration,
and ATG Consumer Commerce using custom catalogs, use this command:
<ATG2007.1dir>/home/bin runAssembler MyApp.ear m DCS_UI.management
PubPortlet B2BCommerce.Versioned
where MyApp.ear is your application packaged as a J2EE archive file. This command assumes that you
have not created any custom modules or use additional ATG modules because if you had, they would
have been specified here. Only the modules mentioned here and those accessed by them are included in
the EAR file. Remember that you can start only the modules that are included in your J2EE application so if
you designate one module during assembly only, you wont be able to start other modules without
assembling a new J2EE application.
Heres an example of the command youd use to run ATG Search with ATG Consumer Commerce, so you
can use Dynamic Search and Navigation as well as Search Merchandising:
<ATG2007.1dir>/home/bin runAssembler MyApp.ear m DCS-UI.Search
PubPortlet B2CCommerce.Versioned DCS.Search.Versioned
The corresponding ATG Business Commerce command is as follows:

<ATG2007.1dir>/home/bin runAssembler MyApp.ear m DCS-UI.Search PubPortlet
B2BCommerce.Versioned DCS.Search.CustomCatalogs.Versioned
Because ATG Merchandising is a development application, you do not need to include it when you are
assembling your production application. The command to create a production ear file for one application
in a cluster that uses ATG Business Commerce and ATG Content Administration is as follows:
<ATG2007.1dir>/home/bin runAssembler MyApp.ear m DCS.PublishingAgent
B2BCommerce
For information on how to deploy your J2EE application, see the documentation from your application
server vendor.

The following are the modules youre most likely to use with ATG Merchandising:
Module
Description
DCS-UI
Contains submodules that contain HTML UIs for ATG

Commerce applications running on ATG Content
Administration. Specifying this module causes DCSUI.management to run.
33
3 - Getting Started
DCS-UI.management
Contains an HTML UI informally called ATG

Merchandising UI, in which merchandising activities are
performed. This module accesses ATG Content
Administration (Publishing.base, BIZUI), UI
elements used to build a UI for a Content
Administration environment (AssetUI), and core ATG
Commerce (DCS).
This module makes ATG Merchandising and ATG
Content Administration available to a single instance.
DCS-UI.Search
Contains an HTML UI used by Search Merchandising

and Dynamic Search and Navigation, which are ATG
Search add-on features of ATG Merchandising. This
module accesses the core Commerce parts of the ATG
Search integration framework (DCS.Search), ATG
Merchandising (DCS-UI.management) as well as
additions to the UI framework in support of these
Search add-on features (AssetUI.Search).
DCS.Search.Versioned
Contains code that supports versioned core Commerce

extensions to the ATG Search integration framework. If
you use ATG Search, ATG Content Administration and
ATG Commerce, you must specify this module.
DCS.Search.CustomCatalogs.Versioned
Contains code that supports versioned custom catalogs

extensions to Commerce Search. If you use ATG Search,
ATG Content Administration and either Business
Commerce or custom catalogs with Consumer
Commerce, you must specify this module.
B2BCommerce.Versioned
Contains ATG Content Administration extensions to the

Business Commerce product.
B2CCommerce.Versioned
Contains ATG Content Administration extensions to the

Consumer Commerce product.
PubPortlet
Contains ATG Business Control Center components.

You must use this module when you want to access the
ATG Business Control Center.
In general, the modules you use for your development environment, which is the environment in which
ATG Merchandising runs are nearly identical to those used in production. If the production environment
uses the B2BCommerce module, the development environment uses the B2BCommerce.Versioned
module, indicating the Business Commerce with support for versioning (Content Administration).
When you build your application, the ATG Commerce module you use indicates the type of Commerce
product (Consumer Commerce or Business Commerce) or the type of catalogs (standard or custom) your
site implements as well as other optional Commerce features. Web applications that use custom catalogs
must specify the DCS.DynamicCustomCatalogs.Versioned module when running ATG Merchandising.
34
3 - Getting Started
Note that non-dynamic custom catalogs are not supported in ATG Merchandising. When you use
B2Bcommerce.Versioned, you use the dynamic custom catalogs automatically.
For a list of modules, see the Appendix A: ATG Modules in the ATG Programming Guide.

To remove ATG Merchandising, complete these steps:
1.
Destroy ATG Merchandising database tables as described in Destroying ATG

Merchandising Database Tables.
2.
Uninstall ATG Merchandising:

On Windows: Use the Add/Remove Programs function in the Windows Control
Panel.
On UNIX: Run the Uninstall_ATG_Merchandising_2007.1 script in the
<ATG2007.1dir>/uninstall/.DCS-UI2007.1_uninstall directory.
The DCS-UI2007.1 directory will be removed.
Destroying ATG Merchandising Database Tables

When you destroy database tables, you need to destroy them in the opposite order you used for creating
them. If you want to remove all tables set up for ATG Merchandising and ATG Business Commerce, for
example, you would destroy first the versioned Business Commerce tables, then the versioned core
Commerce tables, followed by the ATG Content Administration tables and the ATG Adaptive Scenario
Engine tables.
This section includes the following subsections:
Destroying Versioned Custom Catalog Tables with Search Support
Destroying Versioned Core Commerce Tables with Search Support
Destroying Versioned Search Tables
Destroying Versioned Business Commerce Tables
Destroying Custom Catalogs Tables
Destroying Versioned Core Commerce Tables
Destroying Versioned Custom Catalog Tables With Search Support

In order to destroy tables for ATG Merchandising, ATG Search, and ATG Business Commerce (or Consumer
Commerce with custom catalogs), first destroy the tables in this section, then destroy the tables described
in Destroying Versioned Core Commerce Tables with Search Support.
To destroy tables that support the union of ATG Merchandising, ATG Business Commerce, and ATG Search
run the drop_dcs_search_customcatalog_versioned_ddl.sql script in the following directory:
35
3 - Getting Started
<ATG2007.1dir>/DCS/Search/CustomCatalogs/Versioned/sql/install/
database-vendor
The drop_dcs_search_customcatalog_versioned_ddl.sql script executes subscripts in a particular

order to destroy the tables that support the union of ATG Merchandising, ATG Business Commerce, and
ATG Search.
Destroying Versioned Search Tables

In order to destroy tables for ATG Merchandising, ATG Search, and core Commerce, you need to destroy
two sets of tables.
First of all, destroy the tables that support the union of ATG Merchandising, core Commerce, and ATG
Search, run the drop_dcs_search_versioned_ddl.sql script in the following directory:
<ATG2007.1dir>/DCS/Search/Versioned/sql/install/database-vendor
The drop_dcs_search_versioned_ddl.sql script executes subscripts in a particular order to destroy

the tables that support the union of ATG Merchandising, core Commerce, and ATG Search.
Secondly, destroy the tables that support the union of ATG Merchandising and ATG Search, run the
drop_versioned_refinement_ddl.sql script in the following directory:
<ATG2007.1dir>/DAF/Search/Versioned/sql/uninstall/database-vendor
The drop_versioned_refinement_ddl.sql script executes subscripts in a particular order to destroy

the tables that support the union of ATG Merchandising and ATG Search.
Next, remove the versioned Commerce tables, beginning with the Business Commerce tables or Custom
Catalogs tables, if you installed them, then move onto the core Commerce tables, described in the
sections that follow.
Destroying Versioned Business Commerce Tables

When you want to destroy the ATG Merchandising tables and you have both ATG Merchandising and ATG
Business Commerce, first destroy the ATG Merchandising tables that specifically support ATG Business
Commerce and then the core ATG Merchandising tables, as described in Destroying Versioned Core
Commerce Tables.
To destroy ATG Merchandising tables that support ATG Business Commerce, run the
drop_b2bcommerce_versioned_ddl.sql script in the following directory:
<ATG2006.3dir>/B2BCommerce/Versioned/sql/uninstall/database-vendor
The drop_b2bcommerce_versioned_ddl.sql script executes subscripts in a particular order to destroy

the tables used by ATG Merchandising and ATG Business Commerce.
36
3 - Getting Started
Destroying Custom Catalogs Tables

If you created custom catalogs tables by running a script specifically for this purpose because you wanted
to run the custom catalogs without Business Commerce, you can destroy those tables using the
drop_versioned_custom_catalog_ddl.sql script in the following directory:
<ATG2007.1dir>/DCS/CustomCatalogs/Versioned/sql/uninstall/database-vendor
If you use custom catalogs with Business Commerce, following the steps in the prior section will destroy
custom catalog tables along with all other Business Commerce tables.
Next, follow the instructions to remove versioned core commerce tables as described in Destroying
Versioned Core Commerce Tables.
Destroying Versioned Core Commerce Tables

If you created tables for core ATG Merchandising, you can destroy them using the
drop_dcs_versioned_ddl.sql script in the following directory:
<ATG2007.1dir>/DCS/Versioned/sql/uninstall/database-vendor
The drop_dcs_versioned_ddl.sql script executes subscripts in a particular order to destroy the tables
used by core ATG Merchandising as well as ATG Commerce. For a description of the ATG Commerce
tables dropped by this script, see the Configuring a Production Database chapter of the ATG Commerce
Programming Guide.
All versioned subscripts are described in the table below and located in following directory. If necessary,
you can run the subscripts individually:
Script name
Purpose
drop_versioned_claimable_ddl.sql
Destroys tables that have support for versioning

coupons
drop_versioned_priceLists_ddl.sql
Destroys tables for that have support for versioning

price lists
drop_versioned_product_catalog_ddl.sql

products and catalogs
drop_versioned_promotion_ddl.sql

promotions
37
3 - Getting Started
38
3 - Getting Started
4 Configuring ATG Merchandising
When you purchase ATG Merchandising, you need to install it and set it up to use at least two databases: a
Content Administration database that holds versioned data and a production database that holds the
data on your live site. Additionally, you need to configure several parts of your application. Complete the
following administrative tasks:
1.
Install the ATG Merchandising product. See Installing ATG Merchandising.
2.
Set up your Content Administration server. See the Setting Up an ATG Content
Administration Server chapter of the ATG Content Administration Programming Guide.
Note that when you import assets, in order to associate the addition of assets with a
task in a Merchandising project, you need to specify the following as part of the import
command:
workflow /Commerce/editCommerceAssets.wdl
3.
Set up your Content Administration database. See Configuring a Purchased Content

Administration Database.
4.
Set up your production database. See the Configuring a Production Database chapter
of the ATG Commerce Programming Guide.
5.
Run ATG Merchandising. See Running ATG Merchandising.
6.
Set up deployment resources. See Configuring Deployment Resources.
7.
Configure Workflows that will be available to ATG Merchandising projects. See

Configuring Workflows.
8.
Create accounts for the internal users who will be using ATG Merchandising. See
Setting Up User Accounts and Roles.
9.
Depending on how youve implemented AccessControlServlet, you may need to

make some adjustments to it so that it works properly with ATG Merchandising. See
Configuring AccessControlServlet.
10. Configure Custom Catalogs, if you are using custom catalogs instead of standard
catalogs. See Configuring Custom Catalogs.
11. If youd like asset, property, and asset-type level security, implement the resources
required of the secured repositories feature. See Working with Secured Repositories.
12. ATG Merchandising displays price lists to customers using ATG Business Commerce.
For instructions on enabling and disabling price lists, see Working with Prices.
13. Customers who have ATG Merchandising and ATG Search also have the following
features:
39
4 - Configuring ATG Merchandising
Dynamic Search and Navigation lets you define facets used to organize
products into dynamic groupings. See Designing a Site with Multiple Facets for
guidance on how to architect a facet strategy.
Search Merchandising lets you control the display of search results for a
grouping of site visitors, using search configurations and search configuration
folders. See Structuring the Search Configuration Tree to learn how to design a
tree of search configurations and search configuration folders and
Administering Search Merchandising for a description of administrative set up
tasks.
14. Configure the ATG Merchandising UI as needed. The tabs, buttons, and properties you
see in ATG Merchandising can be visible or hidden from users. See Customizing the
ATG Merchandising User Interface and the Configuring the Asset Manager section of
the ATG Business Control Center Administration and Development Guide.
15. Shutdown ATG Merchandising and re-assemble, redeploy, and restart your
application. See Running ATG Merchandising.
Configuring Deployment Resources

The process of copying the assets you created in your ATG Merchandising development environment to a
staging or production environment is called deployment. In order to deploy assets, you need to configure
your deployment resources to recognize the repositories those assets are associated with. The
deployment process requires three copies of each repository that contains deployable assets:
A source repository is a versioned repository you use in ATG Merchandising to edit

assets. This repository runs in the development environment and corresponds with
the ATG Content Administration database.
A destination repository is a nonversioned repository that supports the assets you

want to deploy. This repository runs in the development environment and
corresponds with the production database.
A target repository is a nonversioned repository that supports the deployed assets. It

corresponds with the database in the environment staging or production that you
have deployed assets to.
For assets that use out-of-the-box ATG Merchandising repositories, source and destination repositories
already exist: you need only to register those destination repositories to make them visible in the ATG
deployment UI. You create the target repositories as part of the process for defining your target server
outlined in step 2 below.
To configure your deployment resources, follow these steps:
1.
Familiarize yourself with the deployment process by reading the Understanding

Deployment chapter of the ATG Content Administration Programming Guide.
2.
Set up your target server and database as described in Setting Up Deployment chapter
40
If you customized the out-of-the-box repositories, for example, by adding properties

to an existing item descriptor, you need to make the same customizations to the
corresponding target repository. The out-of-the-box repositories and their locations
are the same on the target server as they are in the Content Administration server, so
see step 4 for this information.
3.
If you have created custom repositories, you need to configure them for deployment
as described in Setting Up Deployment chapter of the ATG Content Administration
Programming Guide.
4.
Add the ATG Merchandising destination repositories to the ATG deployment UI, by
creating an atg/registry/ContentRepositories.properties file located in local
configuration directory (for example, <ATG2007.1>/home/localconfig) on your
Content Administration server with the following content:
initialRepositories+=\
/atg/commerce/catalog/ProductCatalog_production,\
/atg/commerce/pricing/priceLists/PriceLists_production,\
/atg/search/repository/RefinementRepository_production, \
/atg/commerce/claimable/ClaimableRepository_production
Note that you use the repositories listed here to deploy to a production environment
and the similarly named repositories with a _staging suffix for the staging
environment. Also, if you dont have ATG Search, exclude the entry for the Refinement
Repository.
5.
Re-assemble, redeploy and restart your application running with the ATG Content
Administration server, then add a site as described in the Defining the Deployment
Topology section of the Setting Up Deployment chapter of the ATG Content
Configuring Workflows
A workflow defines a set of tasks in an organized sequence that you move through by selecting task
actions. When you create a project, you select a workflow, which acts as a template, providing the
structure and actions available in the project. For general information on workflows, see the Adapting
Workflows to Content Management Projects chapter of the ATG Content Administration Programming Guide.
Workflows behave similarly in ATG Merchandising and ATG Content Administration with one difference.
ATG Content Administration defines one type of workflow that is named for deployment options but
incorporates non-deployment tasks, such as Author and Review Content, as well. There are two kinds of
ATG Merchandising workflows: commerce workflows and deployment workflows. A commerce workflow
defines non-deployment tasks and refers to a deployment workflow for deployment tasks. When users
create ATG Merchandising projects, they select a commerce workflow.
ATG Merchandising includes two commerce workflows. The workflows themselves have identical tasks
Author, Review Content, Deploy - but differ in the parts of the UI to which they provide access.
41
Name in the ATG Business

Control Center
Name in the ATG Control

Center and wdl file
Description
Manage Commerce Assets
editCommerceAssets
Designed for merchandising

users who work with
commerce and search assets.
Administer Commerce Search
adminCommerceSearch
Designed for administrators

tasked with configuring ATG
Search and ATG
Merchandising.
This guide uses the ATG Business Control Center name.

By default, both workflows refer to the Standard workflow for deployment instructions. You can adjust
the default set up as follows:
Learn about your deployment options in Deployment Options.
If you want to change the deployment workflow to Early Staged, follow the
instructions provided in Changing the Deployment Workflow.
For guidance on creating custom workflows, see Creating Workflows.
Deployment Options
Heres a brief description of the deployment workflows available to you:
The Standard workflow lets you deploy assets when the last task is complete, or defer
deployment, for example to a nightly batch operation.
The Early Staged workflow lets you preview assets on a staging server before
deploying them to a production site. The assets are checked in before deployment to
the staging server.
For a detailed explanation of the tasks and task actions provided by ATG Merchandising workflows, see
the descriptions for their Content Administration counterparts in the Project Workflows section in the
Adapting Workflows to Content Management Projects chapter of the ATG Content Administration
Programming Guide. The ATG Content Administration versions of these workflows include Author and
Review Content tasks that are present in commerce workflows, but not in the ATG Merchandising
deployment workflows.
Changing the Deployment Workflow

By default, the commerce workflows use the Standard deployment workflow. To specify a different
workflow, follow these steps:
1.
Start the ACC as described in the ATG Installation and Configuration Guide.
2.
Select Workflow > Publishing.
42
3.
Click the Commerce folder, then click the link for the appropriate commerce workflow
( editCommerceAssets or adminCommerceSearch).
Note: If you expand the Commerce folder, you see a Deployment folder, which holds
all five ATG Merchandising deployment workflows.
4.
Find the following action:

Start workflow processName:
/Commerce/deployment/Standard.wdl
workflowSubjectId:
Process's Process id
5.
Double-click the action to open it in an editor.
6.
Navigate to the /Commerce/deployment/Standard.wdl portion, and click Type a

String.
7.
Replace Standard with the deployment workflow you want to use. Be sure to exclude
spaces between words and keep the .wdl extension.
8.
Click the checkmark on the right side of the element to close the editor.
9.
For instructions on designating a target site, see the Setting Up Workflows section of
the Adapting Workflows to Content Management Projects section in the ATG Content
Setting Up User Accounts and Roles

Users evaluating ATG Merchandising can log in as one of two users:
The publishing user (username and password are publishing) has unrestricted
access to the administrative and merchandising portions of the UI. All administrative
tasks, such as creating search configuration folders and specifying the properties that
affect how search results appear to customers, are applicable and visible only to users
who have ATG Search. See Administering Search Merchandising for information on
administrative tasks.
The merchandising user (username and password are merchandising) can access all
non-administrative parts of the UI.
You can view information about these user accounts in the Internal Users portion of the ATG Business
Control Center. See Setting Up User Accounts and Roles for information.
When you purchase a permanent copy of ATG Merchandising, an administrator needs to set up user
accounts with roles that control the parts of ATG the users can access.
You may decide to assign users to existing roles. All existing roles that provide access to ATG Content
Administration automatically provide access to ATG Merchandising. If you prefer to create new roles, they
will require access to both ATG Merchandising and ATG Business Control Center, because the ATG
Merchandising UI is part of the ATG Business Control Center.
43
For instructions on setting up user accounts and roles, see Managing User Access and Security in the ATG
Content Administration Programming Guide.
Configuring AccessControlServlet
ATG Merchandising uses atg/userprofiling/AccessControlServlet to ensure that only users who
are logged in can access ATG Merchandising features. You can use AccessControlServlet to restrict
access to portions of your site. When you implement this servlet, you use the accessControllers
property to map a partial URL to an access controller component, which defines access limitations.
If you run your application module on the same server as ATG Merchandising as most users do, you will
need to update the properties file for this component so that you wont override access restrictions
provided in other configuration layers. If you dont make this change, users may be permitted to view
pages in the /Merchandising context when they are not logged in and may encounter errors. To ensure
that users are re-routed appropriately to the login page, configure your
AccessControlServlet.properties file.
Users who have configured AccessControlServlet in a properties file previously, follow these steps:
1.
Locate AccessControlServlet.properties in the following directory:

<ATG2007.1dir>\home\localconfig\atg\userprofiling
Note that localconfig is the default configuration directory. If you use a different
configuration directory, locate the AccessControlServlet.properties file in it
and save your changes to the file in that directory.
2.
Change the line that begins

accessControllers=
to
accessControllers+=
3.
Save your changes.
Configuring Custom Catalogs

When you use Business Commerce or Consumer Commerce with custom catalogs, you must configure
one agent server on your target site cluster to run the Catalog Maintenance Service. There are two ways to
do this:
Specify the DCS.PublishingAgent module when you create the application that
corresponds with the agent server that will run the Catalog Maintenance Service. For
all other servers in the cluster, specify the PublishingAgent module instead.
44
Specify the DCS.PublishingAgent module when you create all clustered servers
using . On all servers not running the Catalog Maintenance Service, set the active
property to false in the /atg/epub/CatalogMaintenanceHelper component.
Regardless of which method you choose, the agent server running the Catalog Maintenance Service must
use the /atg/commerce/catalog/custom/CatalogCompletionService component, so make sure
the enabled property remains set to true. This component is responsible for recalculating asset
properties automatically when the properties they depend on change in value. For more information on
custom catalogs, see Using Standard or Custom Catalogs.
Working with Secured Repositories

The secured repository feature permits you to control the access users have to assets, asset properties,
and asset types. For example, you might make all products visible to a given user, but prevent that user
from editing product properties.
ATG Merchandising uses three versioned Commerce repositories: Product Catalog, Price Lists, and
Claimable Repository. Each repository has a different level of support for secured repositories. By default,
Claimable Repository is not secure and requires you to create and configure components in order to be
secured. The Merchandising Product Catalog, which refers to the iteration of the Product Catalog used by
ATG Merchandising, supports secured repositories only when you use the Business Commerce module,
and the Price List repository supports secured repositories by default whenever you use price lists. When
the Price Lists and Merchandising Product Catalog repositories are secured, the following permissions are
enforced by the Repository XML Definition, which you can alter as necessary:
Principal
Access Privileges
ATG Content Administration roles: EPub-Super-Admin, EPubAdmin, EPub-Manager, EPub-User
Read, Write, Create, and

Delete
ACC groups: administrators-group

ACC groups: everyone-group
Read
You can change your configuration to make unsecured repositories secured or the reverse. Use these
instructions when you are working with ATG Merchandising repositories or custom repositories you
created. Refer to the following table for the name and path for the secured and unsecured versioned
Commerce repositories provided to you out-of-the-box:
45
Repository
Unsecured
Repository Path and
Name
Secured Repository Path

and Name (Secure Adapter)
Secured Repository XML

Repository Definition
Merchandising
Product Catalog
/atg/commerce/
catalog/
ProductCatalog
/atg/commerce/catalog/
SecureProductCatalog
atg/commerce/catalog/custom
/secureCustomCatalog.xml
Price List
/atg/commerce/
pricing/price
Lists/PriceLists
/atg/commerce/pricing/
priceLists/SecurePrice
Lists
atg/commerce/pricing/
priceLists/securePrice
Lists.xml
Claimable
Repository
/atg/commerce/
none
none
catalog/Claimable
Repository
Note: Users who have ATG Merchandising and ATG Search have an additional repository called
RefinementRepository. Theres no need to secure the assets (facets) in this repository, so instructions
are not provided for it.
Using Secured Repositories

Note that the Merchandising Product Catalog and Price List repositories are secured by default. If you
modify your installation to use unsecured versions of these repositories, the instructions below describe
how to re-implement the secured versions.
The following steps describe how to secure out-of-the-box as well as custom repositories. All cross
references in the steps below refer to sections in the Secured Repositories chapter of the ATG Repository
Guide:
1.
2.
For all repositories except Merchandising Product Catalog and Price Lists, create and
configure a Secured Repository Adapter component of class
atg.adapter.secure.GenericSecuredMutableRepository as described in the
Configuring the Secured Repository Adapter Component section. Note that each
repository requires a unique component instance.
Replace the entry for the unsecured repository in the
/atg/registry/ContentRepositories.initialRepositories property with the
path and name for the Secured Repository Adapter.

Note: For the Merchandising Product Catalog, skip this step and instead change the
componentPath property of the MerchandisingProductCatalog component to
the unsecured repository. The ContentRepositories.initialRepositories
property should always be set to MerchandisingProductCatalog, whose
componentPath property is then mapped to the exact repository thats used.
3.
For all repositories except Merchandising Product Catalog and Price Lists, create a
secured repository definition file as described in the Writing the Secured Repository
Definition File section. Configure this file according to the needs of your application.
46
4.
Update all views that display assets from the repository you are securing. See
Modifying Views.
Using Unsecured Repositories

To switch from using a secured repository to an unsecured repository, follow these steps:
1.
Replace the entry for the secured repository in the

/atg/registry/ContentRepositories.initialRepositories property with the
path and name for the unsecured iteration of the repository.

2.
Note: For the Merchandising Product Catalog, skip this step and instead change the
componentPath property of the MerchandisingProductCatalog component to the
unsecured repository. The ContentRepositories.initialRepositories property
should always be set to MerchandisingProductCatalog, whose componentPath
property is then mapped to the exact repository thats used.

3.
Update all views that display assets part of the repository. See Modifying Views.
Modifying Views
When you want to change the type of repository secured or unsecured - that you want to use, you need
to update all views that display assets from that repository. Keep in mind that, although its possible for
one repository used by your application to be secured and another to be unsecured, all views associated
with a given repository must use the same security strategy:
For Merchandising Product Catalog, update the Catalog, Catalog Orphans, Media, and
Promotions views.
For Price Lists, update the Price Lists and Price Lists and Folders views
For Claimable Repository, update the Coupons view.
To update a view, follow these steps:

1.
Locate the component that represents the view. Out-of-the-box options include:
Promotions view:
/atg/commerce/web/assetmanager/PromotionsBrowseTab
Configuration
Media view: /atg/commerce/web/browse/MediaTreeDefinition

Price Lists view: /atg/commerce/web/browse/PriceListsTreeDefinition
Price Lists and Folders view:
/atg/commerce/web/browse/PriceListFoldersTreeDefinition
Coupons view:
/atg/commerce/web/assetmanager/CouponBrowseTabConfiguration
Note: No changes are required for Catalog or Orphans view.

2.
Change the value of the repositories property to the repository you want to use.
47
Working with Prices
There are two types of pricing available to you. Basic pricing lets you specify the same prices for a given
SKU to all users. If you require a more sophisticated pricing system, use price lists to create a set of
product and SKU prices that are visible to a set of users, such as all members of a given organization. For
example, a price list called East Coast shows one set of prices to users who live in the appropriate states
and prices from a different list, such as West Coast, are shown to users who live there. Price lists can inherit
prices from base lists, which limits the number of prices you need to enter manually. The other benefit to
price lists is the different types of pricing it provides: you can set an individual price or define different
prices depending on how many items are purchased.
By default, Consumer Commerce customers use basic pricing and Business Commerce customers use
price lists. If you have basic pricing, when you access a SKU, a SKU Pricing tab holds properties for setting
a list price and sale price. For users with price lists enabled, products and SKUs display the prices assigned
for each price list in the Price List Pricing tabs. Also, two price list views are provided for creating,
modifying, and deleting price lists.
If you are a Consumer Commerce customer and you want to switch from basic pricing to price lists, follow
the instructions provided in the Setting Up Price List Functionality in ATG Consumer Commerce subsection of
the Using Price Lists section in the Using and Extending Pricing Services chapter of ATG Commerce
Programming Guide.
Business Commerce customers who wish to use basic pricing need only use the ATG Control Center to
change the value of the preCalculators property in the
/atg/commerce/pricing/ItemPricingEngine to non-price list calculators.
Regardless of the type of pricing you use, you need to configure other pricing resources to implement,
display, and calculate order prices. The pricing services provided by ATG Commerce are flexible and
comprehensive; see the Using and Extending Pricing Services chapter of ATG Commerce Programming Guide
for guidance.
Structuring the Search Configuration Tree

Customers who have ATG Search and ATG Merchandising can control the display of search results by
creating a tree of search configurations and search configuration folders. Before you begin building your
tree, you need to consider the search configurations you want it to contain as well as the order in which
you want them to apply. Its a good idea to develop a tree strategy first, based on a few key principles.
A tree is made up of search configurations organized by search configuration folders. A search
configuration holds the set of rules that affect the ordering and contents of search results for a group of
site visitors. When you create search configurations, its a good idea to create base search configurations
first, which act as templates by providing settings that can be used or overridden in the search
configurations they are associated with. A search configuration can associate any base search
configuration with itself as long as it doesnt support a conflicting language.
Depending on how you configure your tree, you can create a single search configuration for all visitors at
your site, or create different search configurations for different groups of site visitors. Visitors can be
48
grouped by language (useful if your site is in multiple languages or has visitors from multiple countries),
by user segment (useful for targeting specific search results to specific types of visitors), or both. These
groupings are called dimensions; language and user segments are the two types of dimensions provided
by ATG Merchandising.
In addition to holding search configurations, search configuration folders specify dimensions, allowing
you to filter out visitors who dont meet restricted criteria. That way, the specialized visitors who do meet
the criteria are more likely to see products tailored to their tastes.
All users, including merchandisers, can create search configurations and base search configurations, but
its the task of an administrator to architect the search configuration tree by creating the search
configuration folder structure that defines the tree and setting up the languages and user segments that
will be available as dimension values.
Where to Begin
Creating a Search Merchandising strategy involves creating and configuring several assets. There are few
restrictions placed on the order in which you perform tasks, but you may find it easier to approach them
in this order:
1.
An administrator determines the structure for the search configuration tree, which
involves deciding how you want to organize your search configurations and search
configuration folders, the dimensions and dimension values held by each, and the
base search configurations you want to create. This section, Structuring the Search
Configuration Tree, contains the information you need to make those decisions.
2.
An administrator creates the search configuration folders, sets up the dimension

language and segment values, and selects the properties visible in the Property
Prioritization tab. These tasks are described in the Administering Search
Merchandising section. Note that you must create search configuration folders before
creating search configurations.
3.
A merchandising user creates base search configurations as described in Creating Base

Search Configurations.
4.
A merchandiser user specifies the rules and settings used by the base search
configurations as described in Defining Search Configurations.
5.
A merchandising user creates search configurations as described in Creating Search

Configurations.
6.
A merchandiser user specifies the rules and settings used by the search configurations
as described in Defining Search Configurations.
Sample Types of Trees

There are three types of tree hierarchies that you can use:
One Search Configuration for All Site Visitors
One Search Configuration Folder Containing One or More Search Configurations
Multiple Search Configuration Folders and Search Configurations
49
Notice that the top-level of a tree can have one asset only, which can be either a search configuration or a
search configuration folder.
In the examples youll see in the next subsections, the names of the search configurations and search
configuration folders incorporate the dimension type or values they use. You can name items in your tree
anything youd like although names that identify the dimensions will help to distinguish one item from
another.
One Search Configuration for All Site Visitors

You can create a tree in which the only item it contains is a search configuration that sits at the top level.
This search configuration doesnt use a dimension because its settings apply to all site visitors. Use this
approach if you want to control the display of search results in the same way for all visitors.
One Search Configuration Folder Containing One or More Search Configurations

One tree approach places a search configuration folder at the top level of the tree and inside it are one or
more search configurations. If you want to limit the visitors to whom a search configuration applies by
one type of dimension, you design a tree using this strategy. For example:
In this example, My Newspaper - By Segment is a search configuration folder, using segment as its
dimension type. Each configuration it contains specifies the name of a segment.
If you choose to create search configurations that differ by segment as is demonstrated in this example,
the only visitors who see the results produced from those search configurations must, in addition to being
part of the specified segment, use the default language.
Multiple Search Configuration Folders and Search Configurations

One search configuration folder opens to one or two levels of search configurations and search
configuration folders:
50
Use this approach if you want to incorporate both types of dimensions language and user segments. In
this example, My Newspaper By Language is a dimension folder that uses language as its dimension
type. Both of the dimension folders it contains (English, French) specify a particular language as their
dimension value. They must also supply a dimension type, which determines the type of dimension
values their search configurations must provide, not the type of dimension value they provide. For
example, the English search configuration folder has a dimension value of English and a dimension type
of segment.
Using a multi-tiered hierarchy permits a greater degree of specificity. One search configuration is used for
French people who read a variety of newspapers (New Junkie), for example, and another for similar
visitors for whom English is their language. Because there are two types of dimension folders, your tree
can, at most, incorporate 3 levels as demonstrated in this example: one top-level search configuration
folder using one dimension type, a nested search configuration folder using the other dimension type,
and nested search configurations.
When youre planning a multi-tiered tree, you need to decide which dimension type you want to begin
with. Whether you begin with language or segment has no impact on how search configurations are
applied. Theres also no implementation difference if one dimension is applied to search configurations
and the other applied to search configuration folders, so you should organize your dimensions in the way
that creates less setup work for you. For example, consider this tree structure:
This hierarchy requires you to create the fewest assets for two reasons:
51
There are two kinds of languages represented and four kinds of segments. Starting
with the type of dimension that has fewer values ensures that you have fewer to
create.
Of the four segments, one groups visitors of both languages. The other three apply to
one language grouping each.
If you were to organize your tree using segments first, as demonstrated below, youd create 10 assets
instead of 8:
Consider the hierarchy you could use if the News Junkie segment didnt exist. All segments would apply
to either English or French. Because all visitors who are part of Subscribes to Le Monde are also French
speakers, you could create a search configuration to represent French, thereby removing one level in
the hierarchy.
The Order of Assets in the Tree

Its important to note that the ordering of assets at the same level in the tree affects the way in which they
are applied. Consider a tree that organizes search configurations by segment:
52
For site visitors who fall into two segments, such as News Junkie and Subscribes to Wall Street Journal, the
first search configuration that appears in the tree News Junkie is used.
Consider a tree with multiple search configurations and search configuration folders:
Consider an English visitor who is part of the Subscribes to the New York Times segment. ATG Search
locates the correct search configuration by beginning at the top of the tree with the French configuration
folder. Because French is not the visitors language, ATG Search skips immediately to English for which the
visitor is a match. ATG Search then checks the search configurations in that branch, stopping at
Subscribes to the New York Times because the visitor satisfies all of its requirements.
Likewise, if a site organizes search configurations by language, and one dimension value is a superset of
another (en and en_US, for example), placing the search configuration that uses en higher in the tree
prevents the en_US search configuration from being used because all site visitors who use en_US also use
en.
Had the visitor used any language other than the two identified, the All Others search configuration folder
branch would have been traversed. All Others is a dimension value available to both search
configurations and search configuration folders to represent visitors for whom none of the other search
53
configurations apply. For example, a visitor who has never identified newspaper preferences on a user
profile page or has no recorded purchasing history uses the search configuration with the All Others
dimension value.
The ordering principle applies to the All Other dimension as well, so putting a search configuration with
All Others at the top of the tree would cause it to be used for every site visitor, thereby negating the other
search configurations. For that reason, the search configuration or search configuration folder with the All
Others value always appears at the bottom of the tree within a given level.
When Search Configurations and Search Configuration Folders are on the Same Level
Consider a hierarchy that has search configurations and search configuration folders on the same level in
the tree:
In this example, Subscribes to Le Monde, Subscribes to the New York Times, and Subscribes to the Wall
Street Journal are search configurations because the same settings should be applied to all visitors in
these groups regardless of language. Search configurations, when they are on the same level as search
configuration folders, always appear at the top of the list, which causes them to be considered first. A
visitor who is part of both the Subscribes to the New York Times and News Junkie (English) segments sees
search results that coincide with the Subscribes to the New York Times search configuration because it
comes first in the list. The only exception is for a search configuration that has a dimension value of All
Others, which will always be considered last, after all other configurations and configuration folders.
Notice that theres no search configuration on the same level as a folder with dimension value of All
Others. Youre prevented from making this selection because such a search configuration would divert all
visitors away from any search configuration or search configuration folder beneath it on the tree.
In short, the top of a given level begins with a group of search configurations followed by search
configuration folders and if one has a dimension value of All Others, it appears last in the list.
Implicit Language Inheritance

When you specify language as a dimension type for a search configuration folder, the assets in that folder,
regardless of whether they are search configurations or search configuration folders must specify a
language that ensures that only the site visitors for whom that language is appropriate access that
54
resource. See Detecting a Visitors Language to learn how ATG determines the language appropriate for
each visitor.
Every search configuration uses language to restrict the site visitors to whom it applies. This is also true for
those search configurations that arent part of a tree that uses language as a dimension. Heres how ATG
finds the language for each search configuration that it uses as a restriction:
1.
First, ATG checks the search configuration for a language specified as a dimension
value for the search configuration itself or a parent search configuration folder.
2.
If no language is specified in this way, ATG uses the language assigned to its base
search configuration, if one exists. In order to associate a base search configuration
with a search configuration, the configurations need not have identical languages (a
base search configuration might accept any language, for example, or a search
configuration might not have an explicit language), but they must not be conflicting.
3.
If there isnt an associated base search configuration or if the base search

configurations language is set to Any, ATG uses the default language specified by
your site administrator. See Configuring Language Support for more information.
Administering Search Merchandising

There are four setup tasks an administrator needs to perform before your application is ready for
merchandisers. You may also need to make periodic updates to search configuration settings or tree
organization later on.
All administrative tasks but one must be accomplished in ATG Merchandising by a user that has the
EPub-Admin role or EPub-Super-Admin role assigned to his or her user account. Those roles provide
access to views visible only to projects created from the Administer Commerce Search workflow.
Managing languages involves adjusting component property values, so it is the only task that must be
performed in the ATG Control Center or a properties file.
This section covers the following topics, which should be performed initially in this order:

Note: You must specify a default language regardless of whether you use the
language dimension.

The search result order is affected by rankings provided both to properties as well as to property values in
the Property Prioritization tab. A visitor who searches on a clothing brand will see a $300 jacket before a
$10 t-shirt if the search configuration used organizes search results by price (the property) and places
higher priced items (property value) at the top of the list.
55
Administrators select the properties available for ranking in the Property Prioritization tab from the list of
properties indexed by the search engine. If products are indexed, product and SKU properties will be
among those you must select. When SKUs are indexed, you can choose SKU properties only.
Selecting Properties
When you choose properties, keep in mind that both the properties and property values may be ranked.
The properties you select are visible on all current and future search configurations.
1.
From the Project tab or the Property Prioritization view of the Browse tab, click Create
New, and from the dropdown list that displays, click Property Prioritization. To learn
how to access these views, see Locating Assets.
The Details pane displays information about the property.
2.
From the Property Name dropdown list, select the property that will influence the
order of search results.
The Data Type text box displays the data type used by the property.
3.
Click Create.
The property displays in the Navigation pane.
Removing Properties
When you remove a property, it is no longer visible in the Property Prioritization tab, meaning it is
removed from existing search configurations and unavailable to new search configurations. Because you
are able to remove properties that are in use (the property has a weighting and/or its values have
rankings in a search configuration), be certain that a property is not necessary before you remove it. For
removal instructions, see Deleting Assets.

When you organize configurations by language, a search configuration folder uses language as its
dimension type. Assets nested in it, regardless of whether they are search configuration folders or search
configurations, must specify a particular language. That way, the search configuration applied to a given
site visitor depends on the language that user reads.
You need to specify the languages that appear in the General tab as dimension values for search
configurations, base search configurations, and search configuration folders. The languages you see there
can represent general languages (English, for example) or locales (en_US), which are specific versions of a
language used in a given country. You can make search results appear one way for English speakers from
the United States and another for English speakers from the United Kingdom, each represented by a
different search configurations.
It is possible to use more general languages for some resources (English) and more specific (en_US) ones
for others, but note that ordering of resources is significant. Placing a search configuration with a
language of English above a search configuration with a locale of en_US prevents the second from being
used, given that ATG Search always applies the first search configuration thats a match for a site visitor
and English is superset of en_US. Its a good idea to use a consistent value format (all general or all
specific), or, if you blend the two, place resources with more specific values higher in the tree.
56
When you specify the language values, you provide roughly one language (US_english, for example) for
each resource that specifies a language value (search configuration folder). Keep in mind, however, that
theres an All Others dimension value that applies its search configuration settings for users with a
language thats not represented elsewhere.
In addition to defining the languages available as dimensions to search configurations and search
configuration folders, you must also specify the languages available to a base search configuration. If a
search configuration inherits settings from a base configuration, the assets dont need to use the same
language, but must not have conflicting languages. There may be a one-to-one relationship between the
languages supported in each, but thats not frequently true. The best implementations reuse base search
configuration as templates for multiple search configurations. Using general languages on your base
search configurations makes them more likely to be reused.
Consider the following situation: The tree begins with a Language search configuration folder that
contains many search configurations, among them one for French speaking Canadians and another for
French speaking Belgians. By creating a base search configuration with a French language (fr), it can be
used by both search configurations (fr_CA, fr_BE). Again, keep in mind that a base configuration may
use the Any language value, making it available to all search configurations.
To define the languages, you update component properties either by accessing the component in the
ACC or providing a new properties file for the component in your local configuration directory:
1.
Access the resource you want to use to update the

/atg/search/config/LanguageDimensionService component properties.
2.
To specify languages for base configurations, set the locales property to the list of
locales you want to support. For example:
locales=en,fr
3.
To specify languages for search configuration folders and search configurations, set
the languagesMap property to a mapping of resource bundle key to locale. For
example:
languageMap+=\
americanEnglish=en_US,\
canadianEnglish=en_CA,\
britishEnglish=en_GB,\
canadianFrench=fr_ca,\
belgianfrench=fr_be,\
4.
To specify a default language, which will be used when the tree does not use language
as a dimension, specify a language or locale to the defaultLocale property.
ATG Merchandising displays the names of the languages commonly associated to the locales you specify.
For example, en_US and en_BG both display as English by default. If youd like to provide other names for
your locales, you can do so in a resource bundle, following these steps:
1.
Create a resource bundle in /atg/core/i18n/MultiBundleFormatter of your local

configuration directory, if you havent already created a custom resource bundle there.
See Working with Resource Bundles for information on custom resource bundles.
2.
For the base configuration languages, use this format:
57
atg.search.dimension.language.locale.<locale>=<display_name>
For example:
atg.search.dimension.language.locale.en= English (US, CA & GB)
atg.search.dimension.language.locale.fr=French (CA & BE)
3.
For the search configuration and search configuration folder languages, use this
format:
atg.search.dimension.LanguageDimensionService.<locale>=<display_name>
For example:
atg.search.dimension.language.americanEnglish=English (US)
atg.search.dimension.language.canadianEnglish=English (CA)
atg.search.dimension.language.britishEnglish=English (GB)
atg.search.dimension.language.canadianFrench=French (CA)
atg.search.dimension.language.belgianFrench
=French (BE)
The resource bundle keys use a prefix (atg.search.dimension, by default) defined in the
dimensionValueKeyPrefix property of the LanguageDimensionService component. If want to use a
different prefix or no prefix in the resource bundle keys, change the prefix in both places.
Detecting a Visitors Language

A search configuration may be designed for Belgian French speakers, but how does ATG determine which
visitors in fact want to be identified as French-speaking Belgians? The language appropriate for a visitor
depends on the locale ATG detects for him or her.
Each site implements its own mechanism for finding a users locale. One site might select a locale from
the HTTP header of the request. Another site might supply a Profile page in which the user specifies a
locale that ATG saves as a user profile property. A third site might provide a Language Preference
dropdown list on a home page, and when a user makes a selection, its appended to the request as a
query parameter that is processed by a custom pipeline servlet. Most multi-language sites will be
designed to incorporate a combination of these options, giving a priority to each.

Grouping your search configurations by segment ensures that the search results a user sees are tailored to
the buying habits or other characteristics of that user. When a search configuration folder specifies
segment as its dimension type, each asset added to it must specify a given segment or the All Others
option.
To use segments as a dimension, you need to create segments in the ATG Business Control Center as
described in the Creating User Segments chapter of the ATG Business Control Center Administration and
Development Guide. Then you need to make those segments available as options, by adding them to the
Merchandising list, as follows:
1.
From the Segment List view of the Browse tab, click Merchandising.
58
2.
In the Details pane, update the list of segments:

Add a segment by clicking Add. When the Select an Item dialog box opens,
navigate to the segment, click the check box beside it, and click OK. If you dont
see the set of segments you expected, your site administrator should make sure
that the correct modules are running.
Rearrange the position of a segment in the list by changing the number beside
it. To preview the new order, click Reorder. The order you provide here doesnt
affect how segments appear in other Merchandising lists.
Remove a segment from the list by clicking the Delete button beside the
segment.
3.
Click Save.
About Removing Segments

If you remove a segment from a segment list, you make it unavailable for use in ATG Merchandising,
which means that you cant select it to be the dimension for search configurations or search configuration
folders. A segment may already be assigned to a search configuration, for example, when it is removed, in
which case the segment remains usable only for that search configuration. If, however, a segment is
deleted from the ATG Business Control Center, that segment becomes unusable by all applications. Any
search configuration or search configuration folder with a deleted segment can be deployed but will
never be applied because, although the segment may appear in ATG Merchandising, it wont be visible to
ATG Search. Because there wont be any visitor attributes associated with the resource that uses the
deleted segment, that resource will never be applied.

Before you create your tree hierarchy, familiarize yourself with the architectural options available to you
by reading Structuring the Search Configuration Tree. Search configuration folders serve to organize your
search configurations into logical groupings. Like search configurations, search configuration folders have
dimension types and dimension values that control access to the items they contain. Site visitors must be
identified as German speakers in order for their search results to be influenced by a search configuration
nested in a search configuration folder with a language dimension value of German.
Only administrators can move search configuration folders. For instructions, see Moving Search
Configurations and Search Configuration Folders.
Creating Search Configuration Folders

A tree can have only one asset at the root. Unless you find that you need only one search configuration,
that root asset must be a search configuration folder that will hold other search configuration folders
and/or search configurations. To create a search configuration folder:
1.
From the Project tab or the Search Configuration Tree view of the Browse tab, click
Create New, and from the dropdown list that displays, click Search Configuration
Folder. To learn how to access these views, see Locating Assets.
The Details pane displays empty text boxes you fill in with information about the
dimension tree folder.
59
2.
In the Name text box, provide a name to the search configuration folder. Choosing a
name that represents the dimension associated with the folder will distinguish it from
others.
3.
If this is not the top-level search configuration folder (which would also be the first
search configuration folder you create), you can see a dropdown list named for the
type of dimension held by this folder: Segment or Language. Select the appropriate
dimension. The option All Others indicates that the search configurations in the search
configuration folder are used only when a site visitors language isnt represented by
an existing search configuration or search configuration folder.
Note: If you dont see an option in the list, it may be in use by another resource; a
dimension value can be used just once in a given level. Additional languages and
segments may be added by your site administrator.
4.
From the Contents Vary By dropdown list, select a dimension type. All items contained
by this search configuration folder will need to provide unique values for the
dimension type you select. Only one dimension type appears in the list if the folder
you are creating is not the root folder.
5.
Click Create.
The search configuration folder displays in the Navigation pane tree.
Deleting Search Configuration Folders

When you delete a search configuration folder, you delete all search configuration folders and search
configurations it contains. For deletion instructions, see Deleting Assets.
60
5 Using the ATG Merchandising User

Interface
ATG Merchandising provides a Web-based user interface (or UI) called the ATG Merchandising UI. Use the
ATG Merchandising UI to build your commerce catalog. Learn about the ATG Merchandising UI by
reviewing the following topics:

If you use Microsoft Internet Explorer, you need to adjust two browser-related settings to avoid seeing
unnecessary errors. Instructions for changing these settings are provided in the /iefix context root
when ATG Merchandising is running. For example, use:
http://hostname:port/iefix
where hostname is the machine running your application server and port is the port number your
application server uses to listen for HTTP requests. For the default to use, see the ATG Installation and
Configuration Guide.

In order to build catalogs in a Content Administration environment, you need to access the ATG
Merchandising UI in a Web browser.
Before you can access the ATG Merchandising UI, make sure that there is a user account set up for you
that provides access to the application. A publishing user, designed for evaluation purposes, is provided
with the global roles that grant administrative access to ATG Merchandising and ATG Content
Administration, including the ATG Business Control Center.
To access ATG Merchandising through the ATG Business Control Center:
61
5 - Using the ATG Merchandising User Interface
1.
Point your browser to the ATG Business Control Center. Because the URL you use
depends on your application server and context root, it may be helpful to see the URL
format:
http://hostname:port/atg/bcc
where hostname is the name of the server where ATG Merchandising is running and
port is the port that your application server specifies for ATG applications. For
example, if you are running on JBoss and your browser is running on the same
machine as Web server, you would use this URL:
http://localhost:8080/atg/bcc
For the default to use, see the ATG Installation and Configuration Guide.
2.
Log in to the ATG Business Control Center. Users who have an evaluation copy of ATG
Merchandising can choose one of two user accounts:
To access as an administrator who can work in the administrative as well as
merchandising parts of ATG Merchandising, use publishing as the username
and password.
To access as a merchandiser who can work in the merchandising parts only, use
merchandising as the username and password.
For more information on these user accounts, see Setting Up User Accounts and Roles.
Notice that the ATG Business Control Center is divided into two vertical areas. On the left is the Operations
list that displays the applications you are running and tools for accessing them. The right side features a
To Do List that you can use to view the projects you want to work with.
In the Operations list, you can see Content Administration, Personalization, and Merchandising in the list
as well as any other ATG applications you are running that use the ATG Business Control Center. For a
comprehensive description of the ATG Business Control Center home page, see ATG Content
Administration Guide for Business Users.
When you click ATG Merchandising, the list expands to display:
62
Manage Commerce Assets, which is the name of the workflow you use to create ATG
Merchandising projects,
Administer Commerce Search, which is the workflow administrators use to create ATG
Merchandising projects that allow them to set up Search Merchandising. This
workflow is visible only to administrative users.
Browse, which is a link to a read-only view of ATG Merchandising:
You can access your catalog in ATG Merchandising in two ways:
View your catalog in read-only mode. This option is ideal for users who want to view a
catalog, or gain a general sense for how ATG Merchandising looks and operates, but
dont need to perform any catalog activities. See Browsing ATG Merchandising in
Read-Only Mode.
From an ATG Merchandising project, select a task that you want to accomplish. See
Working in ATG Merchandising.
Browsing ATG Merchandising in Read-Only Mode

Its a good idea to browse ATG Merchandising in read-only mode if you want to see ATG Merchandising
and dont need to use it to perform any tasks. Keep in mind that the actions available to you are limited to
navigating to assets, viewing information about them, and search for them.
Note to Administrators: While you are setting up ATG Merchandising for evaluators, you should enter a
project and populate ATG Merchandising with a variety of commerce assets so that evaluators can browse
them in read-only mode. If you dont provide content, there wont be any items for evaluators to interact
with.
To access the read-only view of ATG Merchandising:
1.
From the ATG Business Control Center home page, click Merchandising.
2.
Click the Browse link.
63
A screen titled Merchandising opens, displaying the main UI used by ATG Merchandising. You can confirm
that you are in the browse mode of ATG Merchandising because the Current Project and Current Task list
below the Merchandising title, which would ordinarily name the project and task you are working with,
inform you that neither has been selected. The ATG Merchandising UI is divided into two panes: a
Navigation pane on the left and a Details pane on the right.
When ATG Merchandising opens, it displays in the Catalog view of the Browse tab. If there are any
catalogs, categories, products or SKUs in your catalog, you can view them in hierarchical tree. See ATG
Merchandising UI Basics for an overview of the UI elements available to you.
What You Dont See In View-Only Mode

Keep in mind that when you use view-only mode, you are restricted to viewing certain displays and
performing a limited number of actions. To begin with, you see the Browse and Search tabs, but you dont
see the Project tab, which is where you view the assets you have modified in the current project or the
Multi Edit tab, which is where you can edit several assets at a time. Users who have ATG Search wont be
able to see the Facets view of the Browse tab. Because there isnt an active project, you also wont see
controls for advancing from one task to another. The buttons that you would use to create assets, modify
assets, organize your assets in a catalog, and delete assets are also not present.
Working in ATG Merchandising

Usually, you access ATG Merchandising in order to perform some catalog-management tasks, such as
creating and modifying assets in your catalog that you will later deploy to your live Web site. The tasks
available to you and the order you perform them in are specified in a project workflow. So, when you
want to create a product, for example, you choose a project, and select the Author task.
To access ATG Merchandising in edit mode, you select a project and a task in that project:
1.
From the ATG Business Control Center home page, locate the project you want to
work with in the To Do List. Use the Show dropdown list to select the assortment of
64
projects you want to view. If you need to create a project, see Creating Projects That
Access ATG Merchandising for instructions.
2.
Click the project name.

The next available task and user assigned to that task display below the project.
3.
If necessary, assign the task to yourself, by selecting your name from the dropdown list
beside the Assign button, then click Assign.
4.
Click the task name to open the ATG Merchandising UI.

Once youve selected a project from the ATG Business Control Center home page, the ATG Merchandising
home page opens. The ATG Merchandising home page provides all the tools you need to complete tasks
in your project:
65
Across the top of the page, you see a navigation bar that provides a BCC Home link to the ATG Business
Control Center, which you will need to access when you want to create a new project, select a different
project, or deploy assets to a production server. Beside the BCC Home link in the navigation bar is a link
to a log out page.
You can see the name of your project in the top left corner above the name of the current task. On the
upper right side, a dropdown list contains all actions for the current task. Once you are finished with a
task, you can select a task action from that list and click Go to advance the project to the next task.
The screen elements that are visible to you depend on how your site administrator configured the current
task in the active project to appear in ATG Merchandising. The visibility of tabs, buttons, and text boxes
will vary by project and project task. This discussion covers all screen elements available in ATG
Merchandising.
The ATG Merchandising UI has two panes: a Navigation pane on the left and a Details pane on the right.
The Navigation pane provides three tabs used to navigate to the assets you want to work with:
Browse tab
This tab displays commerce assets in a tree hierarchy. Assets are displayed in three
views: Catalog view, Media view, and Catalog Orphans view. Each view has buttons for
creating and modifying the assets it displays.
Search tab
This tab lets you locate assets by specifying a type and any other descriptive content,
such as a creation date, that helps to distinguish the items you want to find from
others.
66
Project tab
This tab displays all assets that are open for editing in the current project.
Multi Edit tab
This tab simplifies the process of editing assets in bulk.
For more information about these tabs and the ways you can access your assets, see Locating Assets.
Types of Assets and Buttons

When you select an asset in the Navigation pane, regardless of what tab you use to locate the asset, you
see a list of that assets properties in the Details pane. You can discern an assets type by the image used
for its icon:
Icon
Asset Type
Base Search Configuration or Search

Configuration
Catalog
Category
Catalog Folder, Media Folder, or Price Lists

Folder
Facet
Media, Promotion, or Coupon
Price List
Product
Search Configuration Folder
SKU
67
A second way to recognize an assets type is by selecting the asset. The status bar located on the top of
the Details pane provides the assets name and type.
Some assets appear in the Browse tab beside two boxes. A box with a plus or minus sign displays only
when the asset, such as a category, folder, or product, can contain other assets. When you click the plus
sign beside a category, for example, ATG Merchandising displays the next level in the hierarchy, typically a
list of categories or products. You can continue to click plus signs to drill through a hierarchy. A minus
sign indicates that an assets nested assets are already visible. Click the minus sign to hide the nested
assets.
Each asset has a checkbox that you use to select it. Selecting an assets checkbox indicates that the next
action you initiate by clicking a button will involve that asset. To move several independent assets, for
example, check the checkbox beside each asset before clicking the Move button. At the top of each tab,
theres a checkbox that you can use to select all assets in it or, when some assets are selected, deselect
them. Note that in the Browse tab, you can use this checkbox to deselect assets only. The checkbox
appears in the Search tab after you have located assets from a search query.
There are several buttons that you may see in various tabs and views in ATG Merchandising. Heres the set
of buttons available to you in the Navigation pane:
Icon
Button Name
Create New
Description
Creates a new asset
Duplicate
Creates a copy of an existing asset
Move
Moves assets to a new place in a hierarchy
Link
Adds assets to a new part of the catalog
Unlink
Removes assets from part of the catalog
Delete
Deletes assets from the catalog
Add to Project
Adds assets to a project so that they are visible in the Project tab
Add to Multi
Edit
Adds assets to the Multi Edit tab
Search
Displays tools for building a search query
68
Remove
Removes items from a given context.

- In the Search tab, this button removes a criteria row.
- In the Project tab, this button removes assets from a project and
the Project tab, thereby reverting it to its pre-project state
- In the Multi Edit tab, this button removes assets from the tab.
Step Edit
Displays assets in Step Edit mode
List Edit
Displays assets in List Edit mode
Apply to All
Displays assets in Apply to All mode
Exit
Ends Step Edit or Apply to All mode
The following buttons are available in the Details pane:
con
Button Name
Description
Edit
Opens a dialog box that

lets you select a new
property value
Delete
Removes a property
value
69
70
6 Locating Assets
ATG Merchandising provides several ways to access commerce assets. In general, you use the tabs and
views provided in the Navigation pane to find the assets you want to work with. Regardless of how you
access an asset, the same information about it displays in the Details pane when you click the assets
name. For example, when you select a hand mixer product through the Browse tab Catalog view, you see
the same tabs containing the same properties and values youd see if you had used the Search tab or
Project tab to find the hand mixer product.
To learn how to access your assets, review the following sections:
Using Catalog View
Using Coupons View
Using Media View
Using Facet View
Accessing Assets in the Details Pane Using the Breadcrumb Dropdown List
Using Catalog View

When you click a task in a Merchandising project in the ATG Business Control Center, ATG Merchandising
opens and by default you see the Browse tab, displaying a tree view of your catalog as indicated by the
Show dropdown selection. This is the Catalog view and in it, you can see all subcatalogs, categories,
products and SKUs contained within your catalog. If you want to switch to Catalog view from another
view, select Catalog from the Show dropdown list:
71
6 - Locating Assets
To navigate through a catalog, click the plus button beside assets that have nested assets. Clicking an
asset name causes information about it to display in the Details pane. Buttons are provided for
performing the following tasks:
Create new assets
Modify asset property values
Add assets to the Multi Edit tab so you can modify many at once.
Duplicate existing assets
Link assets to an additional location
Move assets to a new location
Unlink assets from a particular location
Add assets to your project and make them visible from the Project tab

Assets that dont reside in the catalog hierarchy are orphan assets. Assets become orphans when they are
not provided with parents during their creation or when they are unlinked from all parents. An asset turns
into an orphan also when its ancestors are orphaned so even though a product has a category parent, for
example, that product is an orphan if the category that contains it is an orphan. Catalog Orphans view
displays the category and its nested products.
72
6 - Locating Assets
All orphan assets are visible from the Catalog Orphans view of the Browse tab. To access the Catalog
Orphans view, click the Browse tab and from the Show dropdown list, select Catalog Orphans. You can
work with assets in Catalog Orphans view, but keep in mind that you need to move them into the catalog
hierarchy eventually so that they display as such on your Web site:
In Catalog Orphans view, you can perform the following actions:
Create new assets
Add assets to the Multi Edit tab so you can modify many at once.
Link assets to an additional location
Unlink assets from a particular location
Delete assets

The primary place for working with promotions is the Promotions view, which you access from the
Browse tab by selecting Promotions from the Show dropdown list:
73
6 - Locating Assets
In Promotions view, you can see list of the promotions. Because they dont have parents, the promotions
you see in this list are the complete set of promotions created for your site. In Promotions view, you can
perform the following activities:
Create original promotions
Create promotions based on existing promotions
Define promotions
Add promotions to your project and make them visible from the Project tab
Add promotions to the Multi Edit tab so you can modify many at once.
Using Coupons View

All activities involving coupons are available in Coupons view, which you access by selecting Coupons
from the Show dropdown list in the Browse tab.
74
6 - Locating Assets
Open Coupons view to see a list of coupons as well as tools that let you perform the following activities:
Create coupons
Modify coupon property values
Add coupons to the Multi Edit tab so you can modify several at once
Add coupons to your project and make them visible from the Project tab
Delete coupons
Using Media View

Media view provides a tree structure with which you can view media assets, which are assets associated
with content such as an image or template, and media folders. To access Media view, open the Browse
tab and toggle the Show dropdown list to Media.
75
6 - Locating Assets
To navigate through Media view, click the plus button beside media folders that have nested media
assets. In Media view, you can perform the following activities:
Create new assets
Modify media asset and folder property values
Add assets to the Multi Edit tab so you can modify several at once
Move a media asset or folder to a different media folder
Delete media assets and folders

ATG Merchandising provides two views for working with price lists:
Price Lists view presents price lists in a tree structure that illustrates the inheritance
relationships among lists. All price lists are visible in this view.
Price Lists and Folders view permits you to arrange price lists in folders, organizing
them in the manner that works best for you. Only the price lists that exist in folders are
visible in this view.
If you see one view only, your system administrator has eliminated the other from your application.
To access a view, select its name from the Show dropdown list in the Browse tab.
76
6 - Locating Assets
Price Lists view lets you see a list of base price lists and, when you expand one, you view the lists that
descend from it. Continue expanding lists to view the entire inheritance hierarchy. By clicking a price list,
you display information about it in the Details pane.
In Price Lists and Folders view, you expand folders to see the price lists they contain. If you dont place a
price list in a folder when you create it, you wont be able to view it in Price Lists and Folders view.
The activities you perform in the views are identical, with one exception. In Price Lists and Folders view,
you create, modify, and delete price list folders as well as rearrange price lists and folders. Use either view
to:
Create price lists
Modify price list property values
Display and modify prices for products or SKUs in a list
Add price lists to the Multi Edit tab so you can modify several at once
Add price lists to your project and make them visible from the Project tab
Delete price lists
Once youve created a price list, you need to complete additional tasks in order to use it:
Define price list properties. See Modifying Price List Properties.
Provide prices to products and SKUs that are governed by price lists. See Providing
Prices to Products or SKUs
Assign the price list to users. See Providing Price Lists to Users section.
77
6 - Locating Assets
Using Facet View
Customers who use ATG Merchandising and ATG Search have a view called Facet available from the Show
dropdown list.
Facets are assets you design to create virtual groupings of products based on a product property value.
For example, a Price facet might divide products into selections, such as $1-100, $101-200, etc., using a
products list price property to decide which selection it should appear in. The products included in a
facet depend on the type of facet you create: global facets include all products whereas local facets
include the products nested in the catalog or category associated with the facet.
In Facet view, you see a hierarchy of catalogs (if you use custom catalogs), categories, products, and SKUs
that resembles the tree you see in Catalog view. You can change some property values of these assets in
Facet view, but you cant delete or re-order them. When you expand a catalog or category in Facet view,
you see the facets associated to it. At the top of the tree is a Global Facet folder that contains facets
available to all products in your catalog.
Use Facet view to:
Create facets
Define the selections for a facet and other facet properties
Associate a facet to the Global facet folder or a particular catalog or category, by

moving it
Delete facets
78
6 - Locating Assets
Determine the facets available to catalogs and categories

Customers who have ATG Merchandising and ATG Search can use the Search Configuration Tree view to
organize search configurations in a tree of search configuration folders. To access this view, select Search
Configurations Tree from the Show dropdown list in the Browse tab.
The Search Configuration Tree view displays search configuration folders that, when expanded, reveal the
other search configuration folders or search configurations they contain. One search configuration folder
exists at the top of the tree and it determines the type of dimension language or segments used to
organize its contents. A search configuration folder called Language, for example, might hold search
configuration folders French and German, each of which designates their respective language for the
search configurations they contain. The settings held by the search configurations in the German folder
are applied when searches are performed by German-reading customers only. For a detailed explanation
of the tree hierarchal possibilities, see Structuring the Search Configuration Tree.
The actions you can perform in the Search Configuration Tree depend on the limitations of your user
account and the project you use to access ATG Merchandising. All users can create and delete search
configurations as well as modify their properties, including selecting a base configuration with settings to
inherit. If you use a project based on the Administer Commerce Search workflow, you can also perform
the following tasks:
Create and delete search configuration folders as described in Managing Search

Configuration Folders.
Reorganize the search configuration folders and search configurations in the tree as
described in Moving Search Configurations and Search Configuration Folders
Define the settings used by search configurations as described in Defining Search

Configurations.
79
6 - Locating Assets

Customers who have ATG Merchandising and ATG Search can use the Base Search Configuration view to
display a list of base search configuration. A base search configuration is a group of settings that can act
as a template of settings used by search configurations. To access this view, select Base Search
Configurations from the Show dropdown list in the Browse tab.
Base Search Configuration view lists the existing base search configurations. Clicking one displays its
settings in the Details pane. In the Base Search Configuration view, you can create, modify, and delete
base search configurations.

Administrative users who have ATG Search as well as ATG Merchandising use two additional views for
setting up the application:
Segment List view
Property Prioritization view
Both views are accessible from the Show dropdown list on the Browse tab. The Search Configurations
Tree view provides additional functionality to site administrators as described in the Using Search
Configurations Tree View.
The Segment List view displays the segments available to search configurations:
80
6 - Locating Assets
From this view, you can perform the following tasks, all of which are described in detail in Configuring the
Segment Dimension:
Select segments created in the Personalization module for use in ATG Merchandising.
Rearrange the order in which segments will appear in dialog boxes to merchandisers.
Remove segments from the list of segments available to ATG Merchandising.
In the Property Prioritization view, you work with the properties that merchandisers rank in the Property
Prioritization tab of search configurations and base search configurations:
The rankings given to properties and property values determine where search results with those values
appear in the search results list. In the Property Prioritization view, you can:
Select product or SKU properties for ranking
81
6 - Locating Assets
Remove a property from the Property Prioritization tab
For information on these tasks, see Managing the Properties in the Property Prioritization Tab.

When you want to locate one or more assets of a certain asset type, use the search tool in the Search tab.
The search tool lets you build a query that is used to locate the assets in any catalog. You must provide
the asset type as a criterion, and you can limit the scope of your search further by providing additional
criteria, such as property values that must match the values held by located assets. To indicate that you
want to add more criteria, you click the Add Criteria button and to remove criteria, you select the
Remove button to the right of the criteria block.
The dropdown lists you see are determined by the selections youve made in previous dropdown lists. For
example, if you are searching for assets of type SKU and you add more criteria boxes, youll be able to
select a property from a list that includes the properties defined for SKUs only. The property you select
here determines the values in the next dropdown list and so on.
Consider a business commerce site that defines manufacturers for its products. To locate all products
manufactured by Suppell, for example, you enter the following criteria:
1.
In the Search tab, select Product from the Show dropdown list. The only criterion that
is required to perform a search is the asset type.
2.
Because you want to specify more criteria, change the Find all assets selection in the
next dropdown list to Match. Several text boxes display for adding criteria.
Alternatively, you could have clicked the Add Criteria button to display the criteria
text boxes.
82
6 - Locating Assets
Several dropdown lists display with default values that you can modify.
3.
Keep the next dropdown list set to any. This dropdown list doesnt apply to this
particular search because you are specifying only one property criterion. If you
specified several, the any value would signal an inclusive search: find any product that
matches one of these property values. The all value indicates that all returned
products must contain each specified property value criteria.
4.
From the first dropdown list, select Assets, which is the option you use when you
want your criteria to incorporate specific property values. The other options in this
dropdown list are as follows:
Use Asset ID is when you are looking for a specific asset and you know its
repository ID. The repository ID is visible in the Info tab of the Details pane
when the asset is selected.
Use Asset in group when you have created content groups for your assets and
you want to locate an asset in one such group. For information on content
groups, see the ATG Personalization Guide for Business Users.
5.
From the next dropdown list, select Manufacturers. This dropdown list displays all
properties defined for the asset type you selected: you see Manufacturers only when
you specify products as your asset type.
6.
From the next dropdown list, select Manufacturer name. This dropdown list contains
another property, as is the case here, or an operator. When a more specific property is
provided here, the next dropdown list contains operators.
7.
From the dropdown list of operators, select is.
8.
In the text box, enter Suppell, which is the manufacturers name:
9.
Click Find.
83
6 - Locating Assets
The assets that match your criteria display in a list. If there are more than 20 returned assets, your results
will appear on multiple pages that you can access using the number links at the bottom of your result set.
Clicking an assets name will display information about it in the Details pane. You can perform the
following tasks with your located assets:
Link non-media assets to an additional location
Unlink non-media assets from a particular location
Delete assets
Add assets to your project and making them visible from the Project tab
If you want to perform a new search, click the New Search button to see the criteria you previously
entered. Modify the criteria as needed. You also have the option to create an asset of the same type for
which you searched. See Creating Original Assets for instructions.

The Project tab lets you access the assets that have changed or will change in the current project. When
you modify assets, they are automatically added to the Project tab. You can think about the Project tab as
a workspace. When you deploy the project, new versions are created for the assets in the Project tab,
which are reflected on the live Web site.
84
6 - Locating Assets
When you click the name of an asset in the Project tab you display information about it in the Details
pane. A new asset created in the current project has New! in its name. If you create an asset in a different
project and delete it in the current one, the asset will appear in red with a line through it.
The Project tab provides two buttons, the first of which is Remove. Use this button to revert the changes
youve made to an asset in the current project. If you created a new asset in your project and use this
button to remove it, that asset is deleted permanently from ATG Merchandising. If you delete an asset
created in a previous project and revert your deletion, the asset returns to its pre-project location and
state.
The second button is Add to Multi Edit, which you use to add assets to the Multi Edit tab, where you can
modify asset properties in bulk.
For more information about projects, such as how to add assets to the Project tab, see Using Projects.

The Multi Edit tab is a temporary workspace that holds assets you want to modify in bulk. The tab label
records the number of assets contained by the Multi Edit tab. The assets you add to it display in a list and,
when you want to edit them, you select assets of the same type and use the appropriate button:
The Step Edit button lets you edit one asset at a time sequentially. Once youve edited
and saved your changes for one asset, the properties for the next asset are displayed
automatically.
The List Edit button lets you edit the properties on all assets in a list. You provide
property values to one asset, then scroll to the next in the list and so on: after youre
finished, you save all of your edits at once.
85
6 - Locating Assets
The Apply to All button lets you apply a set of property values to a selection of assets.
All multi edit operations require you to configure property groups, which are groups of properties
available for modification at the same time. When you select a multi edit button, you also select a
property group whose properties display in the Details pane. To learn how to create property groups, see
the Creating and Defining Property Groups section of the Configuring the Asset Manager chapter in the ATG
Business Control Center Administration and Development Guide.
The Multi Edit tab has another button, Remove Assets, that you use to remove selected assets from the
tab. Note that assets remain on the tab until they are proactively removed using this button or the session
ends. Assets that are added to the Multi Edit tab, but are not modified there or elsewhere wont be visible
in the Project tab or redeployed when you check the project in.
See Modifying Assets in Bulk for more information.
Accessing Assets in the Details Pane Using the

Breadcrumb Dropdown List
Assets can have property values that are themselves other assets. For example, a product has a template
property that holds the template used to display the product information on the Web site. In the template
property, theres a media-external asset, which represents the template and identifies its location via URL.
If you click media asset in the template property, the Details pane displays the properties of the media
asset. What you see in the Details pane is exactly the same as what youd see if you navigated to the
media asset in the Media view of the Browse tab and selected it. Above the Details pane is a dropdown list
with two entries: one for the media asset and below it one for the product. This is the Breadcrumb
dropdown list.
86
6 - Locating Assets
The Breadcrumb dropdown list tracks the navigation path you follow through the Details pane. As you
access assets that are property values of other assets, the Breadcrumb dropdown list acquires asset
entries. Select an asset from this list to return to information about it in the Details pane.
When you access an asset through the Breadcrumb dropdown list or by clicking it from within another
assets property, there are two things you should know:
The asset you initially selected in the Navigation pane remains selected as you move
from asset to asset in the Details pane. That initial asset also appears at the bottom of
the Breadcrumb dropdown list. Usually the Details pane displays information about
the asset selected in the Navigation pane; that relationship doesnt persist when you
are using the Breadcrumb dropdown list.
Any changes you make to an asset before accessing another asset in this way are
automatically saved.
The Breadcrumb dropdown list remains until you click an asset or button in the Navigation pane. The next
time you move through assets in the Details pane, a new Breadcrumb dropdown displays with new
entries that apply to your recent activities.
87
6 - Locating Assets
88
6 - Locating Assets
7 Creating and Organizing Assets
There are several ways to populate your catalog with assets. The first time you use ATG Merchandising, its
likely youll import catalog content from a legacy system into ATG, following the process specific to your
system configuration. For guidelines, see the Importing Product Catalog Content section of the ATG
Commerce Catalog Administration chapter of the ATG Commerce Guide to Setting Up a Store. Then, you can
create new assets manually as needed.
If you want one asset to appear identically in several parts of your catalog, you can link that asset to each
location. Such assets have multiple parents: one parent for each location. When you make a change to the
asset in one place, that change is reflected in all places.
Alternatively, you may want new assets that appear similar to existing assets, but have some different
property values. In this case, duplicate the assets you want copies of and modify the property values as
needed. Although the duplicated asset is independent of the original, assets contained by it are links. For
example, a duplicated category is distinct from the original, but the products it contains link to the
original products.
By unlinking an asset, you remove it from a location and if it only existed in one location, it is turned into
an orphan. Orphan assets are assets, such as products and SKUs, that require parents, but can exist
outside of the catalog hierarchy temporarily. While an asset is an orphan, it isnt visible in the catalog
hierarchy on a published Web site. You can move orphan assets back to the catalog or you can delete
them.
Because the order of the assets on your Web site is identical to that of your catalog tree, you may need to
adjust the tree structure by moving assets around and removing the ones you dont want to use. Other
ancillary assets, such as media assets and pricelists, may require re-arranging in order to improve visibility.
The capabilities provided to the assets that display in your catalog, such as products and categories, are
similar to those provided to the ancillary assets, such as media assets, media folders, promotions, price
lists, and facets. You can create original assets of these types, or duplicate existing assets as well as reorganize them. However, assets that exist in views other Catalog view have different parent requirements,
so they cant be orphans. For such assets, linking and unlinking capabilities often arent applicable.
Once you have finished your ATG Merchandising task, you signal that it is complete by selecting a task
action. See Advancing from One Task to Another for instructions.
This chapter covers the following topics:
89
7 - Creating and Organizing Assets
Linking Assets
Unlinking Assets
Moving Assets

When you use ATG Merchandising, you build a catalog by creating assets that display in it, such as
products and categories, or support the assets that display in it, such as media assets and promotions.
This section describes how to create individual assets. Note that catalog and catalog folder assets are
available only when you are using custom catalogs.
You can create assets from all tabs, although you should be aware of a few restrictions. The Browse tab is
comprised of views, each of which lets you create assets from a subset of types. The procedures below
inform you of the appropriate Browse tab view for the type of assets you are creating. When using the
Search tab, you can create assets only of the type youve recently searched for. The Project tab permits
you to create all assets. Note that your administrator can provide additional creation limitations.
Refer to the following sections for instructions:
Creating Catalogs
Creating Categories
Creating Products
Creating Media Folders
Creating Promotions
Creating Coupons
Creating Facets
Creating SKU Links

The main purpose of catalogs folders is to store product catalogs in the structure used on your Web site. If
you want to publish a catalog to your Web site, it must exist in a catalog folder even though the catalog
90
folder itself wont be visible on the site. Unlike other assets in a catalog, catalog folders reside at the top
level of the hierarchy most of the time, although they can exist anywhere in the hierarchy.
While you are developing your catalog, you may want to create a temporary structure using catalog
folders to organize assets that you are not ready to add to the catalog hierarchy, but want to make visible
in Catalog view of the Browse tab.
This section describes the properties you are required to fill in when you are creating a catalog folder. It
also described how to indicate where in the catalog you want the catalog folder to reside, which is an
important decision, but not one you are required to make now. A comprehensive list of catalog folder
properties is provided in Appendix: Asset Properties.
To create a new catalog folder:
1.
In Catalog view or Catalog Orphans view of the Browse tab, click the Create New
button, and from the dropdown list that displays, click Catalog Folder. To learn how
to access these views, see Locating Assets.
The Details pane displays empty text boxes you can use to define the catalog folder.
2.
Specify the catalog folders location in the hierarchy by adding, replacing, or removing
a parent using the Select Parent and Clear buttons on the top right of the Details
pane. A parent is preselected if you see an asset name beside Select Parent.
Add or replace a parent by clicking Select Parent and, once the Select an Item
dialog box opens, clicking the radio button beside your preferred parent. Click
OK.
Remove a parent by clicking Clear beside Select Parent. A catalog folder
without a parent resides at the top level of the catalog hierarchy.
3.
Enter a name for the catalog folder in the Name text box (Required).
4.
Click Create.
In the Navigation pane, the catalog folder displays. The Details pane contains the
Basics tab, which holds properties for the catalog folder.
Creating Catalogs
Catalogs can contain any number of other catalogs or categories and represent the entirety of what users
see on your web site. This section describes the properties you are required to fill in when you are
creating a catalog. It also described how to indicate where you want the catalog to reside, which is an
important decision, but not one you are required to make now. Know that creating a catalog without
specifying a location makes the catalog an orphan that is visible in Catalog Orphans view, not Catalog
view. At deployment time, catalogs must exist in catalog folders. A comprehensive list of catalog
properties is provided in Appendix: Asset Properties.
To create a new catalog:
1.
button, and from the dropdown that displays, click Catalog. To learn how to access
these views, see Locating Assets.
91
The Details pane displays empty text boxes you can use to define the catalog.
2.
Specify the catalogs location in the hierarchy by adding, replacing, or removing a

parent using the Select Parent and Clear buttons on the top right of the Details pane.
A parent is preselected if you see an asset name beside Select Parent.
dialog box opens, selecting the appropriate Repository item type that you are
creating and the parent asset type from their respective dropdown lists, and
then clicking Find. Click the radio button beside your preferred parent, then
click OK.
Remove a parent by clicking Clear beside Select Parent.
3.
Enter a name for the catalog in the Name text box (Required).
4.
Click Create.
In the Navigation pane, the catalog name displays. The Details pane contains two tabs:
the Basics tab holds properties you can use to define the catalog and the Info tab
holds view-only metadata, such as a catalog ID and creation date.
Creating Categories
Categories organize your catalog into a hierarchy that provides a navigational framework for your Web
site. A category can contain other categories, products, or both.
This section describes the properties you are required to fill in when you are creating a category. It also
describes how to indicate where in the catalog you want the category to reside, which is an important
decision, but not one you are required to make now. Know that creating a category without specifying a
location or indicating that the category should live at the root directory makes the category an orphan
that is visible in Catalog Orphans view, not Catalog view. A comprehensive list of category properties is
provided in Appendix: Asset Properties.
To create a new category:
1.
button, and from the dropdown that displays, click Category. To learn how to access
2.
Specify the categorys location in the hierarchy by adding, replacing, or removing a

dialog box opens, selecting the appropriate Repository item type that you are
creating and the parent asset type from their respective dropdown lists, and
then clicking Find. Click the radio button beside your preferred parent, then
click OK.
3.
If you are using standard catalogs and you want the category to appear at the top
level of the hierarchy, set the Root property to true.
4.
Enter a name for the category in the Name text box (Required).
92
5.
Click Create.
The category displays in the Navigation pane. The Details pane contains two tabs: the
Basics tab holds properties you use to define the catalog, and the Info tab holds viewonly metadata, such as the catalog ID and creation date.
Creating Products
A product is a navigational end-point in the catalog. This section describes the properties you are
required to fill in when you are creating a product. It also describes two non-required properties that you
should consider setting now:
Decide where your product will reside initially: in a part of the catalog hierarchy visible
in Catalog view or as an orphan visible in Catalog Orphans view. If you dont specify a
location, your product will be an orphan.
Supply a name to the Management Display Name property that will represent the
product in the ATG Merchandising Navigation pane only. If you do not provide a
Management Display Name, a system generated name will be used. (Custom
Catalogs only)
A comprehensive list of product properties is provided in Appendix: Asset Properties.

To create a new product:
1.
button, and from the dropdown that displays, click Product. To learn how to access
2.
Specify the products location in the hierarchy by adding, replacing, or removing a

OK.
3.
Enter a name for the product in the Name text box (Required).
4.
If you are using Custom Catalogs, provide a name in the Management Display Name
text box that will represent the product in the Navigation pane.
5.
Click Create.
The product displays in the Navigation pane. The Details pane contains four tabs:
The Basics tab holds general information about the product and its parent.
The Media tab holds tools for associating images to the product.
The SKUs tab holds tools for working with SKUs associated with the product.
The Info tab holds view-only metadata, such as the product ID and creation
date.
93
The way you create a media asset depends on the type of asset you want to create. This section describes
the properties you are required to fill in when you are creating a media asset. For a comprehensive list of
media asset properties, see Appendix: Asset Properties.
Media assets are assets that typically have content, such as a URL pointing to a Web page, a JSP template,
or a block of product copy that is managed by ATG Merchandising. In technical terms, media assets are
commerce assets that are contained in a Content Repository. There are three kinds of media assets:
Media-internal-text assets store blocks of text in a database managed by ATG

products. For example, a line of text displayed by a slot on your web site might be
stored as an media-internal-text asset.
Media-internal-binary assets store binary files, such as images or PDFs, in a database

managed by ATG products. For example, an image of a product might be stored as a
media-internal-binary asset.
Media-external assets store, in an ATG-managed database, a URL that points to files,

such as text or binary files, that exist on the Web. For example, a JSP template used for
all products might be stored as media-external assets.
Before you create your media assets, decide how you want to organize them and create folders
accordingly.
Creating Media Folders

Before creating media assets and folders, consider how you want to organize them. You can base your
organization on the following principles:
Subject matter: Blenders folder holds all blender media assets
Asset type: Images folder holds all assets representing images
This section describes the properties you are required to fill in when you are creating a media folder. It
also describes how to select a parent folder. Media folders, unlike media assets dont have to exist in
folders, but if you decide to add this folder to one, now is a good time to select the parent. If you dont
select one, the folder will exist in the top-level of the hierarchy. For a comprehensive list of media folder
properties, see Appendix: Asset Properties.
To a create media folder, follow these steps:
1.
In Media view of the Browse tab, click the Create New button and, from the dropdown
list that displays, click Media Folder. To learn how to access this view, see Locating
Assets.
The Details pane displays empty text boxes you will fill with information about the
media folder.
2.
In the Name text box, enter a name for the media folder. (Required)
3.
If the new media folder should reside in another media folder, click the Parent Folder
property Edit button to open the Select an Item dialog box, where you can navigate to
a parent folder, click the radio button beside it, and click OK.
94
4.
Click Create.
The new media folder displays in Media view in the location you specified.
Creating Media-Internal-Text Assets

To create an asset that contains a text block representing, for example, advertising copy, follow these
steps:
1.
list that displays, click Media-Internal-Text. To learn how to access this view, see
Locating Assets.
media asset.
2.
In the Name text box, enter a name. (Required)
3.
Specify a media folder parent by following these steps (Required):

Click the Edit button beside Parent Folder to open the Select an Item dialog
box.
Navigate to the media folder that will hold the media asset you are creating.
Click the radio button beside the media folder.
Click OK.
4.
In the Data text box, provide the text that you want ATG Merchandising to manage.
(Required)
5.
Click Create.
The new media-internal-text item displays in the specified media folder.
Creating Media-Internal-Binary Assets

To create an asset that has a binary file associated with it, follow these steps:
1.
list that displays, click Media-Internal-Binary. To learn how to access this view, see
Locating Assets.
media asset.
2.
In the Name text box, enter a name for the media asset. (Required)
The name you enter here will represent the binary file itself in your application. For
example, if an internal-binary asset holds a product image , a page that displays the
image identifies it by the name you provide here. For image files, including the files
extension causes the image to display on the bottom of the Details pane, once you
have uploaded the image and created the asset.
3.

box.
95
Click OK.
4.
Specify a file to upload. You can do this in one of two ways (Required):
In the Data text box, enter the path that leads to the binary file, beginning with
the drive name and ending with the file name.
Click the Browse button to open a dialog box that lets you navigate to the
binary file and select it. Click Open.
5.
Click Create.
The new media-internal-text item displays in the specified media folder.
Creating Media-External Items

To create an asset that has a URL associated with it, follow these steps:
1.
list that displays, click Media -External. To learn how to access this view, see Locating
Assets.
media asset.
2.
In the Name text box, enter a name for the media asset.
3.

box.
Click OK.
4.
In the URL text box, provide the URL that accesses the external file. (Required)
5.
Click Create.
The new media-external item displays in the specified media folder.
Creating Promotions
When you create promotions from scratch, you are required to provide values to three properties, which
are the only three described in the procedure below. Keep in mind that a promotion is not functional
unless you supply additional property values as described below.
To create a promotion:
1.
In the Promotions view of the Browse tab, click Create New and, from the dropdown
list that displays, select type of promotion you want to create. To learn how to access
this view, see Locating Assets. Promotion types include:
96
Type of Promotion
Description
Item Discount - Percent off
A specific percentage off the regular price of any item or one in

particular. For example, you could offer any UltraLight T-Bike for
10% off the regular price.
Item Discount - Amount off
A specific amount off the regular price of any product or one in

particular. For example, you could offer any UltraLight T-Bike for
$100 off the regular price.
Item Discount - Fixed price
A specific product for a fixed price. For example, you could offer
any UltraLight T-Bike for $500. Another example would be a buy
one item, get a special price on another discount; for example
you could offer a price of $5 for any helmet to any visitor who
buys a bike.
Shipping Discount - Percent off
A specific percentage off the price of shipping. For example, you

could offer a 50% discount on your regular shipping charges to
anyone who buys any three items.
Shipping Discount - Amount off
A specific amount off the price of shipping. For example, you

could offer $5 off the regular shipping charges for any order over
$200.
Shipping Discount - Fixed price
Shipping for a specific amount. For example, you could offer free
shipping to visitors who buy any bike today.
Order Discount - Percent off
A specific percentage off the total order. For example, you could
offer a 10% discount off the total cost of an order.
Order Discount - Amount off
A specific amount off the total order. For example, you could
st
offer a $50 coupon (Use this coupon by August 31 and get $50
dollars off your total order.). Another example would be a
discount of $20 on any order over $100.
Order Discount - Fixed price
The visitor pays a fixed price for his or her order. For example,
you could offer any product for $50 only.
promotion.
2.
In the Name text box, provide a unique name for the promotion.(Required)
3.
Depending on the type of promotion, youll see a text box called Discount amount,
Discount percentage, or Discount price. Enter a value for this property, excluding
symbols, such as a currency or percent sign. (Required)
4.
In the Order of Applications text box in the Usage Limits tab, enter the order in which
this promotion should be applied if a visitor qualifies for multiple promotions. The
default value is 1, the highest priority. For more information, see Order of Applications
table entry in the Updating Other Promotions Properties section.
5.
Click Create.
97
The promotion displays in the list of promotions, which is sorted alphabetically. The
Details pane displays the following tabs:
The General tab holds general information about the promotion.
The Distribution tab holds information about Closeness Qualifiers and how
promotions are applied.
The Conditions tab holds information about the circumstances in which the
promotion is offered
The Usage Limits tab contains information about how the promotions can be
used.
The Media tab holds tools for associating media to the promotion.
Once youve created a promotion, you need to set its other property values so that it provides the
appropriate discount and is available to customers. See Defining Promotions for instructions.
About Promotions
In order to use a promotion on your site, you need to create it, then perform several other tasks. Heres the
overview of the entire process:
1.
Create the promotion. If you are creating the promotion from scratch, refer to Creating
Promotions. Otherwise, refer to Creating Assets Based on Existing Assets.
2.
Set up the promotion so that it applies in the appropriate circumstances, and associate
the relevant media asset to it. See Defining Promotions.
3.
Design how the promotion looks. You may store the promotion as text in a mediainternal-text asset or as an image in a media-internal-binary asset. See Creating Media
Assets and Folders.
4.
Decide how visitors will receive the promotion:

It will display on your web site to all visitors. See the Implementing Promotions
chapter of the ATG Commerce Guide to Setting Up a Store.
It will display on your web site only to the visitors who qualify for it. Follow
instructions in the Specifying the People Who Receive the Promotion section of
the Creating a Promotion chapter of the ATG Commerce Guide to Setting Up a
Store to learn how to create the scenario. Then, implement the scenario in a JSP
as described in the Serving Targeted Content with ATG Servlet Beans chapter of
the ATG Page Developers Guide.
It will be advertised in an email sent to the visitors who qualify for it. Follow
instructions in the Specifying the People Who Receive the Promotion section of
the Creating a Promotion chapter of the ATG Commerce Guide to Setting Up a
Store to learn how to create the scenario.
Creating Coupons
Coupons are promotions applied to an order when a user enters a coupon code. Essentially, creating a
coupon involves associating a coupon code with a promotion. To create a coupon, follow these steps:
98
1.
Create and define a promotion that determines the circumstances under which the
promotion and, consequently, the coupon youll create are offered and active. See the
Creating Promotions and Defining Promotions sections.
2.
In the Coupons view of the Browse tab, click the Create New button, and from the
dropdown list that displays, select Deployable Coupon.
The Details pane displays empty text boxes you fill with information about the
coupon.
3.
Associate the coupon with a promotion, by selecting the Edit button beside the
Promotion property. When the Select an Item dialog box displays, click Find to view a
list of promotions. Click the radio button beside the promotion you want to use, then
click OK.
The coupon is identified in the Navigation pane by the promotions name.
4.
In the ID textbox, replace the automatically generated ID with a name that has
significance for the coupon. Keep in mind that users use this ID as a coupon code
when redeeming the coupon. Also note that once the coupon is created, you cant
change it.
5.
In the Expiration Date text box, enter the date and time on which the coupon
becomes unredeemable. Although a coupons expiration date is separate from the
promotions usage date, be sure to make these two dates coincide: when a user
redeems a coupon, the promotion must be active. Conversely, you may set a coupon
to expire before the promotion if you want to offer it in conjunction with a different
delivery mechanism, such as a scenario.
6.
Click Create.
The new coupon displays in the Navigation pane, and information that describes it
displays in the Details pane.
For more information about coupons, see the Setting Up a Coupon Promotion section of the Creating and
Maintaining Promotions chapter in the ATG Commerce Guide to Setting Up a Store.

A price list lets you specify a set of product and SKU prices for a particular group of customers. For a given
price list, you can define different prices for a product or SKU based on the quantity of items purchased.
Its a good idea to create a hierarchy of price lists, the first of which being a base price list or the first list
from which other price lists inherit prices. That way, you need to provide prices to other lists only when
you want to override the defaults from the base list. Keep in mind that you can create as complex a price
list hierarchy as you like. Each list can inherit prices from the lists related to it: for a given product or SKU, a
price may be inherited from a base list or the nearest list that has a price for it.
There are two views that you can use to create and delete price lists. Your system administrator may
eliminate one view from your application or keep both available to you, in which case you should know
the differences between them:
Price Lists view organizes price lists in a tree that reflects the inheritance relationships
among lists. Base price lists display on top and nested within them are their child lists.
99
Price Lists and Folders view organizes price lists in the folders of your choosing. If you
dont add price lists to folders, they appear alphabetically in the top-level of the
hierarchy.
If you use Price Lists and Folders view, consider how you want to organize your price lists, then create the
appropriate folder structure before creating the price lists youll add to it.
Creating Price Lists

This section describes the properties you are required to fill in when you are creating a price list. In
addition, youll find information about selecting a base price list because most price lists inherit prices
from a base list. If you are using Price Lists and Folders view, add your price lists to folders, so they are
visible in that view. For a comprehensive list of price list properties, see Modifying Price List Properties.
To create a price list:
1.
In the Price Lists view or Price Lists and Folders view of the Browse tab, click the Create
New button and, from the dropdown list that displays, select Price Lists. To learn how
to access these views, see Locating Assets.
The Details pane displays empty text boxes you fill with information about the price
list.
2.
Provide a name for the price list in the Name text box. (Required)
3.
From the Locale dropdown, select the appropriate locale, if you prefer a locale other
than the default, en_US. The locale you provide here determines the currency and
symbol used by the prices in the price list. Note that when prices are displayed in
browsers supporting other locales, prices are calculated based on the units in the Price
List Pricing tab and currency that represents the locale you supply here. (Required)
4.
If you want the new price list to inherit prices from another list, click the Edit button
beside the Base Price List property. When the Select an Item dialog box opens,
navigate to the price list, select it, then click OK.
5.
If you are using Price Lists and Folder view, specify the price lists location in the folder
tree by adding, replacing, or removing a parent using the Select Parent and Clear
buttons on the top right of the Details pane. A parent is preselected if you see a folder
name beside Select Parent.
Add or replace a folder parent by clicking Select Parent and, once the Select an
Item dialog box opens, clicking the radio button beside your preferred parent.
Click OK.
Remove a folder parent by clicking Clear beside Select Parent.
6.
Click Create.
The new price list displays in the Navigation pane, and information that describes it
displays in the Details pane.
Once you have created the price lists, it automatically displays in the Price List Pricing tab table for all
products and SKUs. Now, you need to define the prices for the list by overriding existing prices or
providing new ones as necessary. Also, its a good idea to assign the price list to users. See the Using and
Defining Price Lists section for instructions.
100
Creating Price List Folders

This section describes the properties you are required to fill in when you are creating a price list folder. It
also describes how to select a parent folder. Price list folders dont have to exist in other folders, but if you
decide to add this folder to one, now is a good time to select the parent. If you dont select one, the folder
will exist in the top-level of the hierarchy. For a comprehensive list of folder properties, see Appendix:
Asset Properties.
To a create price list folder, follow these steps:
1.
In Price Lists and Folders view of the Browse tab, click the Create New button and,
from the dropdown list that displays, click Price Lists Folder. To learn how to access
this view, see Locating Assets.
price list folder.
2.
In the Name text box, enter a name for the price list folder. (Required)
3.
Specify the price list folders location in the folder tree by adding, replacing, or
removing a parent using the Select Parent and Clear buttons on the top right of the
Details pane. A parent is preselected if you see a folder name beside Select Parent.
Add or replace a folder parent by clicking Select Parent and, once the Select an
Item dialog box opens, clicking the radio button beside your preferred parent.
Click OK.
Remove a folder parent by clicking Clear beside Select Parent.
4.
Click Create.
The new price list folder displays in the location you specified.

An individual search configuration can include any number of rules and settings, and for some sites, the
various search configurations may differ only in a few of the rules. For example, you might want to include
rules in every search configuration to exclude items that are not in stock. To avoid having to create the
same rules repeatedly, you can use a special type of search configuration called a base search
configuration. A base search configuration is like a template of settings that can be associated with any
number of standard search configurations. Unlike a standard search configuration, a base search
configuration is never applied directly to a search query.
To use a base search configuration, you associate it with one or more standard search configurations and
then select, in the standard search configuration, which settings to inherit and which to override.
A search configuration can use only those base search configurations that dont have conflicting
languages. The languages need not be identical: a search configuration that supports US English can have
a base configuration supporting English or Any language. Likewise, a search configuration that supports
any language that has All Others as its language value can use any base search configuration.
The order in which you create your search configurations and base configurations has no significance,
assuming that any search configuration folders have been created already by your site administrator. (For
instructions on creating search configuration folders, see Managing Search Configuration Folders.) You
101
may, however, find it easier to create base search configurations first, especially if you define them
immediately after creating them. That way, when you create the search configurations, you can associate
a base configuration immediately and see the inherited settings.
Creating Base Search Configurations

A base search configuration acts as a template by providing settings that are inherited and may by
overridden by the search configurations with which it is associated. Using one base search configuration
for multiple search configurations saves you time when youre defining settings. Be sure to assign a
language to your base search configuration that coincides with the language held by one or more search
configurations, which may specify a language directly or inherit it from a search configuration folder. You
can assign Any as the language for a base search configuration to ensure that its available to all search
configurations.
To create a base search configuration:
1.
In Base Search Configurations view of the Browse tab, the Search tab, or the Project
tab, click the Create New button, and from the dropdown that displays, click Base
Search Configuration. To learn how to access these views, see Locating Assets.
base search configuration.
2.
In the Name textbox, provide a name for the base search configuration. Providing a
name that identifies the language used by the base search configuration will help to
distinguish it from others.
3.
From the Language dropdown list, select a language or Any. The languages you see
in the list are provided by your site administrator.
4.
Click Create.
Once you have created a base search configuration, provide settings to it, as described in the Defining
Search Configurations section.
Creating Search Configurations

Before you create search configurations, be familiar with factors you need consider concerning the tree
structure, described in Structuring the Search Configuration Tree. When you create a search
configuration, you specify a name and, optionally, a base configuration.
If you want to have multiple search configurations, you need to create them in a search configuration
folder. Each search configuration folder specifies a dimension type for which the search configurations it
contains must provide a value. For example, a search folder with a dimension type of segment holds
search configurations that each identify a unique segment.
To create a search configuration:
1.
In Search Configurations view of the Browse tab, the Search tab, or the Project tab,
click the Create New button, and from the dropdown that displays, click Search
Configuration. To learn how to access these views, see Locating Assets.
configuration.
102
2.
In the Name textbox, provide a name for the search configuration. Providing a name
that identifies the dimension value used by this search configuration will help to
distinguish it from others.
3.
If you want the search configuration to exist in a folder, complete these tasks:
Check to see if theres a search configuration folder name beside Select Parent.
If you dont see a name or you dont see the name of the search configuration
folder that should hold the search configuration youre creating, click Select
Parent and, once the Select an Item dialog box opens, click the radio button
beside your preferred parent. Click OK.
Youll see a dropdown list named for the type of dimension used by the parent
folder Language or Segment. Select the dimension value from this dropdown
list. The options in this list represent the values for that dimension type that
have not been assigned to other search configurations in the same tree branch.
4.
If you want your search configuration to base its settings on those supplied by a base
search configuration, click Select beside the Inherit From Base textbox to open the
Select an Item dialog box. Click the radio button beside the base search configuration,
then click OK.
5.
A secondary dialog box prompts you to determine whether you also want to use
settings for the Property Prioritization tab from the base search configuration. If you
performed these tasks in a different order than recommended here and have already
provided settings to the Property Prioritization tab, accepting settings from the base
configuration will override the current settings.
6.
Click Create.
Define the settings on the search configurations tabs as described in the Defining Search Configurations.
Creating Facets
Before you create a facet, consider how your site will use it. Do you want the facet to be available to all
products on your site (global) or products in a particular catalog or category (local)? In general, a global
facet has a faceting property thats used by all products, such as Wholesale price or On sale price, and a
local facet uses a faceting property thats specifically designed for a subset of products, such as Monitor
size or Keyboard style. Its also a good idea to consider how you want the selections to divide up your
products and whether those selections will easily accommodate a large number of products and still
present them in a usable fashion.
Once you decide the type of facet you want, you can create it, by providing the appropriate faceting value
and specifying where in the tree it should reside. You are not required to decide the facets position now,
but it must have a parent in order for it to be visible on your site. The parents available to facets are:
The Global Facets folder (global)
A facet (global or local)
A catalog (local, if you are using Business Commerce)
A category (local)
103
Thinking about facets as global or local helps when you are designing the facets on your site, especially
when you use multiple facets in conjunction with each other as you would to present, for example,
products organized by price and size. Technically, theres no difference between the two types of facets,
so if you create a global facet and decide youd prefer to associate it with a category, for example, simply
move it to the new location.
Know that during the creation process, you specify how your selections will appear on your site, using the
Facet Property. Regardless of the strategy you choose, its likely you will need to provide additional
information using other properties, although you are not required to do so now. Be sure to provide that
information before you deploy the facet because without it, your facet may not generate any selections or
the selections you had intended.
To create a facet:
1.
In the Facet view, click Create New and, from the dropdown list that displays, select
Facet.
facet.
2.
From the Faceting Property dropdown list, select the property that represents the
facet.
The properties that display in the Details pane Basics tab correspond to the data type
of the property you just selected.
3.
Beside the Defining Selections property, select a selection strategy that determines
the selections that display on your site:
One Selection for Each Faceting Property Value creates one selection for each
faceting property value. For a manufacturer facet, for example, each selection
represents one manufacturer name.
Dynamic Selections uses the guidelines you specify to create selections
dynamically. Typically, each selection represents several faceting property
values. A price facet, for example, produces selections that represent a range of
prices.
Guided Selection Ranges uses the exact requirements you provide to create
selections dynamically. Typically, each selection represents several faceting
property values. A Monitor size facet, for example, produces selections that
represent a range of sizes. This option is available only if the faceting property is
a number.
Specified Selections creates the exact selections you define. Each selection
represents a range of faceting property values. A price facet, for example,
creates selections, each of which represents the exact range of faceting
property values you provided. This option is available only if the faceting
property is a number.
4.
In the Name textbox, provide a name for the facet. Its a good idea to use a name that
describes the faceting property you selected.
104
5.
Add or replace a parent by clicking Select Parent on the top right of the Details pane
and, once the Select an Item dialog box opens, clicking the radio button beside your
preferred parent. Click OK.
6.
Click Create.

A product can have several different SKUs associated with it, representing varieties, sizes, and colors.
While a regular SKU represents a single item, such as size medium blue shirt, a configurable SKU
represents an object that is sold as a single item, but has variable components, such as a computer
system, or a car.
This section describes the properties you are required to fill in when you are creating a SKU or
configurable SKU. It also described how to indicate where in the catalog you want the SKU to reside,
which is an important decision, but not one you are required to make now. Know that creating a SKU
without specifying a location makes the SKU an orphan that is visible in Catalog Orphans view, not
Catalog view. For a comprehensive list of SKU and configurable SKU properties, see Appendix: Asset
Properties.
To create a new SKU or configurable SKU:
1.
button, and from the dropdown that displays, click SKU or Configurable SKU. To
learn how to access these views, see Locating Assets.
2.
Specify the SKUs location in the hierarchy by adding, replacing, or removing a parent
using the Select Parent and Clear buttons on the top right of the Details pane. A
parent is preselected if you see an asset name beside Select Parent.
OK.
3.
Enter a name for the SKU in the Name text box (Required).
4.
If you are creating a configurable SKU and you are using standard catalogs, provide a
base price in the List Price property. (Required)
5.
Click Create.
The SKU displays in the Navigation pane. The Details pane contains four tabs:
The Basics tab holds general information about the SKU and its parent.
The Media tab holds tools for associating images to the SKU.
The Pricing tab holds prices for the SKU.
The Info tab holds view-only metadata, such as the SKU ID and creation date.
105
Creating SKU Links
SKU links consist of a SKU and a quantity. Several SKU links that are purchased as a single item are bound
together by a SKU bundle. For a detailed definition, see the SKU Items and SKU Links section of the Using
and Extending the Standard Catalog chapter of the ATG Commerce Programming Guide.
This section describes the properties you are required to fill in when you are creating a SKU link. For a
comprehensive list of SKU link properties, see Appendix: Asset Properties.
To create a SKU link that will be added to a SKU:
1.
In the Browse tab, Search tab, or Project tab, select a SKU. To learn how to access these
tabs, see Locating Assets.
2.
In the Basics tab, find the Bundle links property, and click Add New beside it.
The Details pane displays empty text boxes that you fill in to define a SKU-link. At the
top of the Details pane, a Breadcrumb dropdown list has an entry for the SKU you were
just editing and the SKU link you are creating now.
3.
In the Item text box, specify the SKU that is being added to the Bundle Links property.
(Required):
Supply a SKU by clicking the Edit button, which opens the Select an Item dialog
box. Locate a SKU, click the radio button beside it, and then click OK .
Remove a SKU by clicking the Clear button.
4.
Enter a quantity for the bundle link In the Quantity text box (Required).
5.
Enter a name for the bundle link in the Name text box (Required).
6.
Click Create.
Note: To return to the SKU, select it from the Breadcrumb dropdown list on the top of the Details pane.

A configurable property appears to customers as one purchasable item, but is actually a combination of
variable components. A computer could be a configurable property, for example, if customers are
permitted to select on the fly the amount of memory, size of the monitor, and the software that will be
installed on it. The components that make up a configurable property (computer), called configurable
options (monitor of this size), are associated with existing SKUs. If you set a price in a configurable option,
that price overrides the price supplied in the SKU.
This section describes the properties you are required to fill in when you are creating a configurable
property. Additionally, the Configurable Options property is described here because its likely youll want
to define them now. For a comprehensive list of the properties for configurable properties, see Appendix:
Asset Properties.
To add a new configurable property to a configurable SKU:
1.
In the Browse tab, Search tab, or Project tab, select a configurable SKU. To learn how to
access these tabs, see Locating Assets.
106
2.
In the Basics tab, find the Configurable Properties property and click Add New beside
it.
The Details pane displays empty text boxes that you fill in to define the configurable
property. At the top of the Details pane, the Breadcrumb dropdown list has an entry
for the configurable SKU you were just editing and the configurable property you are
creating now.
3.
Enter a name for the configurable property in the Name text box. (Required).
4.
Specify the configurable options:

Replace one configurable option with another by clicking the Edit button
beside the option you want to replace, which opens the Select an Item dialog
box. Locate all configurable options by clicking Find. Locate the replacement
configurable option, click the radio button beside it, and click OK.
Rearrange the position of a configurable option in the list by changing the
number beside it. To preview the new order, click Reorder.
Remove a configurable option from the list by clicking the checkbox beside the
one you want to move, and then clicking Remove Selected.
Add a configurable option to the list by clicking Add Existing to add a row to
the table and clicking the Edit button beside it in order to open the Select an
Item dialog box. Locate all configurable options by clicking Find. Locate the
configurable option, click the radio button beside it, and click OK.
Create a configurable option that will be added to the list by clicking Add New.
The Details pane holds properties that you fill in to define the configurable
option. See Creating Configuration Options for instructions. To return to the
configurable property, select it from the Breadcrumb dropdown list on the top
of the Details pane.
5.
Click Create.

A configuration option is an item, such a 17 monitor by Suppell, thats purchased as part of a collection of
configurable options associated together by a configurable property, such as a computer.
This section describes the properties you are required to fill in when you are creating a configurable
option. Additionally, youll find instructions for associating products and SKUs to the configurable option,
which are necessary actions for making a configurable option usable. Keep in that mind that you should
associate products or SKU with a configuration option, but not both. For a comprehensive list of
configurable option properties, see Appendix: Asset Properties.
To add a new configuration option:
1.
In the Browse tab, Search tab, or Project tab, select a configurable SKU. To learn how to
access these tabs, see Locating Assets.
2.
In the Basics tab, find the Configurable Properties property and click the name of the
configurable property to which you want to add a configurable option.
107
The Details pane displays text boxes for the configurable property. At the top of the
Details pane, the Breadcrumb dropdown list has entry for the configurable SKU you
were just editing and the configurable property.
3.
Locate the Configurable Options property, and click Add New beside it.
The Details pane displays text boxes for the configurable option and an entry for that
configurable option is added to the Breadcrumb dropdown list.
4.
Specify a product, if this configurable option will represent a product:

Add or replace a product by clicking the Edit button to open the Select an Item
dialog box. Navigate to the product you want to use, click the radio button
beside it, and then click OK.
Remove a product by clicking the Clear button.
Create a product that will be automatically associated with the configurable
option by clicking Create. The Details pane displays with empty product
properties that you should fill in as described in Creating Products
5.
Specify a SKU, if this configurable option will a represent a SKU:

Add or replace a SKU by clicking the Edit button to open the Select an Item
dialog box. Navigate to the SKU you want to use, click the radio button beside
it, and then click OK.
Remove a SKU by clicking the Clear button.
Create a SKU that will be automatically associated with the configurable option
by clicking Create. The Details pane displays with empty SKU properties that
you should fill in as described in Creating SKUs and Configurable SKUs. To
return to the configurable option, select it from the Breadcrumb dropdown list
on the top of the Details pane.
6.
Click Create.

When you are assembling your catalog, you may find it easier to duplicate an existing portion of your
catalog tree rather than creating individual assets one at a time. Customers who use custom catalogs may
need to create several catalogs that share many characteristics, such as structure and product set, but
differ, for example, in price. The duplicate feature is ideal for them.
If you duplicate a category, for example, you create a copy of the existing category and links to nested
assets. Although you are basing a new category on an existing one, the two are independent of each
other: changes made to one have no bearing on the other. However, nested assets, which retain their
hierarchy in the duplicated asset, are links to the assets in the original category. If you change a property
value in the original set of nested assets that change is visible in the second set. The reverse is also true.
However, when you duplicate price list folders or media folders that have nested assets, their duplicated
counterparts remain autonomous.
108
By default, the name given to a duplicated asset is the name of the original followed by (copy). If youd
like to use a different format to distinguish the original from the duplicate, see Customizing the Duplication
Identifier section of the Configuring the Asset Manager chapter in the ATG Business Control Center
Administration and Development Guide.
The assets you duplicate can exist anywhere in ATG Merchandising, and you can duplicate as many
related or unrelated assets as you like at a time, as long as the originals live in the same view and the
resultant duplicates will have the same destination.
To duplicate assets:
1.
Locate the assets you want to duplicate using the Catalog Orphans, Catalog, Media, or
Promotions view of the Browse tab or the Search tab. See Locating Assets for
instructions.
2.
Click the checkbox beside each asset you want to duplicate. Keep in mind that
selecting an asset selects its nested assets as well, even though they dont appear
checked.
3.
Click the Duplicate button to open the Select Destination dialog box.
4.
When the Select Destination dialog box opens, navigate to the asset that will contain
the duplicates, and click the radio button beside it.
5.
Click OK.
The Select Destination dialog box closes, and the new assets appear in the specified
location, temporarily highlighted in yellow. The new asset uses the name of the
original beside (copy).
Once you have duplicated assets, you should adjust property values, such Name and Discount Amount for
promotions, to ensure that the asset is unique and usable. See Modifying and Previewing the Properties
of Assets in a Catalog.
Linking Assets
An asset can appear in multiple locations on your site. For example, you may want to represent a product,
such as a grille, in several categories, including the Outdoor Furniture category and the Fathers Day Gifts
category. Rather than create two independent, identical products, you can create one product and link it
to both locations. That way, a change you make to the grille asset in one place will be reflected in both. An
asset that exists in multiple locations is considered to have multiple parents.
If you want to link several assets to a new location at once, you can do so as long as all assets exist in the
same view and have the same destination location. When you link one asset, the assets nested in it are
also linked to the new location.
Keep in mind that most assets can link to multiple locations, and, for customers who use custom catalogs,
across catalogs. The one exception to this rule involves categories, which cant have multiple parents that
are in different catalogs or subcatalogs. You can, however, duplicate a category so that it exists in both
places. In this case, the categories are independent, and each has one parent.
109
Note that other views such as Promotions, Media, Facets, Search Configurations, and Base Search
Configurations dont have Link buttons because the multi-parent model isnt applicable for them.
To link assets to another part of the catalog:
1.
Locate the assets you want to link using the Search tab or the Catalog Orphans or
Catalog view of the Browse tab. See Locating Assets for instructions.
2.
Click the checkbox beside each asset that you want to appear in another part of your
catalog.
3.
Click the Link button to open the Select Destination dialog box.
4.
In the Select Destination dialog box, navigate through the catalog tree to the new
location, and click the radio button beside the parent asset that will contain the assets.
Alternatively, you can locate the parent asset by building a query in the Search tab.
5.
Click OK.
The Select Destination dialog box closes and the assets appear highlighted in the new
location. When you select a linked asset, you can see in the Basics tab of the Details
pane that it has multiple parents:
For catalog folders, see the Parent Folder property.
For categories, see the Default Parent Category property.
For products, see the Parent Categories property.
For SKUs and configurable SKUs, see the Parent Products property.
Unlinking Assets
When you no longer want an asset to reside in a given part of a catalog, unlink it. The unlinking option
lets you decide if you want to remove the asset from one part of the tree or all parts of the tree at once.
For an asset that is linked to several locations in the catalog, unlinking it from one location does not affect
the others or the assets visibility in Catalog view.
When you unlink an asset that exists in one part of the catalog only or you decide to unlink it from all
locations at once, the asset loses its parent(s) and turns into an orphan. Although its nested assets still
have a direct parent, because their parent is an orphan, they, too, become orphans. Orphan assets are
accessible from the Catalog Orphans view of the Browse tab, where you can delete them or link them
back to the catalog.
To see all parents for an asset, click the asset name and check the following property in the Basics tab:
For catalog folders, see the Parent Folder property.
For categories, see the Default Parent Category property.
For products, see, the Parent Categories property.
For SKUs and configurable SKUs, see the Parent Products property.
110
Note that because media assets must exist in media folders, the unlink operation isnt available for them.
It is available in the Media view, however, for use with folders as a means for moving a folder to the toplevel directory. Unlinking isnt available to other assets that permit no parents (promotions, global facets,
base search configurations) or only one parent (local facets, price lists, search configurations).
To remove an asset from one part of the catalog:
1.
Locate the assets you want to unlink in the Search tab or Catalog view, Media view, or
Catalog Orphans view of the Browse tab.
2.
Navigate to the assets in the location from which youd like them removed.
3.
4.
Click the Unlink button, and from the dropdown list that displays, select the option
that suits your purpose:
Use Unlink from selected location to remove the asset only from the parent
that contains the iteration you checked.
Use Unlink from all locations to remove the asset from the catalog tree.
The selected assets are no longer visible in that part of the hierarchy.
Moving Assets
When you are organizing your catalog, you may find you need to make adjustments to its structure. You
may need to move an orphan asset to a place in the catalog hierarchy, thereby providing it with a parent,
or move an asset currently in the catalog to a different location, which replaces an old parent with a new
one. When you move an asset, you have the option to move one asset to a new location and, additionally,
to eliminate all links to it. Any assets nested in a moved asset are also moved.
The assets you want to move can exist anywhere in a given view, and you can move as many as you like at
a time, as long as they have the same destination. In addition to the assets in a catalog, you may also want
to re-arrange media assets and facets. Other types of moving is described in the following sections:
To move items in your catalog:

1.
Locate the assets you want to move using the Search tab or Catalog view, Catalog
Orphans view, Facet view or Price Lists views of the Browse tab. See Locating Assets for
instructions.
2.
Navigate to the assets you want to move.
3.
Click the checkbox beside each asset you want to move.
4.
Click the Move button and, from the dropdown list that displays, select the
appropriate option:
111
Use Move from selected locations to replace the location holding the selected
asset with a new location.
Use Move from all locations to remove the selected asset from all locations
and add it to a new one.
The Select Destination dialog box opens.
5.
Navigate through the tree to find the asset that will contain the assets being moved.
Alternatively, you can locate the destination asset by building a query in the Search
tab.
6.
Click the radio button beside the destination asset.
7.
Click OK.
The Select Destination dialog box closes and the catalog hierarchy displayed in the
Catalog view of the Browse tab reflects the new organization. The names of moved
assets appear temporarily highlighted in yellow.

If you want to move a media or price list folder thats currently nested in another folder to the root of the
hierarchy, follow these steps:
1.
In Media view or Price Lists and Folders view of the Browse tab, navigate to the media
folder or folders you want to move. See Locating Assets for instructions.
2.
Click the checkbox beside the assets you want to move.
3.
In the Details pane, the Parent Folder property is set to the media folders parent. Click
the Clear button near the parent folder name.
4.
Click Save.
The media folder displays in the first level of the hierarchy.

After you create your search configuration tree, you may need to alter the order of the search
configurations and search configuration folders it contains. You can move the position of an asset in its
given level, but you cant move, for example, a search configuration folder from the top-level of the tree
to the second level. If you want to move an asset in this way, its best to redefine the asset, if you want to
replace it with a different asset, or delete it.
Within a search configuration folder, search configurations and search configuration folders are grouped
and managed separately, and when they are on the same level, search configurations always appear
above search configuration folders. The out-of-the-box settings permit any user to create and modify
search configurations from any Merchandising project. Only administrators can create and move search
configuration folders, using a project based on the Administer Commerce Search workflow.
The ordering of the assets in the tree is significant because it reflects the order ATG Search uses to locate
the search configuration appropriate for each site visitor. For that reason, you cant move a search
configuration or search configuration folder when its dimension value is All Others: it must be last. For
112
more information about the capabilities and restrictions of the tree, see Structuring the Search
Configuration Tree.
To reorder the search configurations or search configuration folders on a particular level:
1.
In Search Configurations Tree view of the Browse tab, click the name of the search
configuration folder that holds the assets you want to reposition. See Locating Assets
for information on this view.
The Details pane contains properties about the search configuration folder, including
a table you can use to reposition its nested assets.
2.
In the Details pane, find the table containing the type of asset search configurations
or folders that you want to reposition. Beside each asset is the number that
represents its order in the tree. Provide a new number beside the asset you want to
move.
Note: Specifying 1 gives an asset the first position and moves the asset currently in the
first position to the second.
3.
To preview the order, click Reorder.

The order of assets shifts in the Details pane table.
4.
Click Save to save the new order.

The assets in the tree display in the new order you provided.
113
114
8 Modifying and Previewing the

Properties of Assets in a Catalog
As you work with assets, its likely youll need to modify the property values youve assigned to them. One
way to update property values is to address assets individually, which is ideal if your changes are small in
scope. If you find you need to update many assets of the same type, you may prefer to update them at the
same time using the multi edit operations. Once youve made changes, you can eliminate them if you
need to by reverting to property values provided in the previous checked in version.
This chapter describes how to modify property values: for a description of the properties themselves, see
Appendix: Asset Properties. All properties are described there except promotion and price list properties,
which are described in their respective chapters.
When you modify assets, they are automatically added to your current project and visible in the Project
tab. If youd like to add an asset to the Project tab directly, because youd like modify it later, for example,
you can add it manually by following the instructions provided in Adding Assets to the Project Tab. Once
you have finished your ATG Merchandising task, you signal that it is complete by selecting a task action.
See Advancing from One Task to Another for instructions.
This chapter covers the following topics:
Previewing Assets

In general, the way you update a property depends on the property itself and what you want to do with it.
You may edit a text box by providing a new product description, for example, or assign a SKU a new
parent that you select from a list. A more complicated modification involves associating one asset to
another, such as an image to a category.
You can also create an asset in the context of another. From a category asset, for example, you can create
a media asset template that will be associated with the category. In the process of creating the media
asset template, the Details pane shifts from displaying the category assets properties to the properties
you fill in to define the media asset. There are two things you should know about this circumstance:
115
8 - Modifying and Previewing the Properties of Assets in a Catalog
As soon as the media asset properties display in the Details pane, any changes you
made to the categorys properties are automatically saved.
After you define the media asset and click Create, the media asset continues to display
in the Details pane. In order to navigate back to the category, you can select it from
the Breadcrumb dropdown list on the top of the Details pane. For more information
on this navigational device, see Accessing Assets in the Details Pane Using the
Breadcrumb Dropdown list.
To provide new property values to an asset:

1.
Locate the asset you want to modify using the Browse tab, the Search tab, or the
Project tab. See Locating Assets for instructions.
For SKU links, select a SKU that uses the SKU link. Find the Bundle links property,
and then click the SKU link name.
For configurable properties, select a configurable SKU that uses the
configurable property. Find the Configurable Properties property, and then
click the configurable property name.
For configurable options, select a configurable SKU that has a configurable
property that uses the configurable option. Find the Configurable Properties
property, and then click the configurable property name. Find the Configurable
Options property, and then click the configurable option name.
2.
Click the name of the asset that has property values you want to modify.
The Details pane displays properties for the selected asset.
3.
Modify the asset properties as needed.
4.
Once you are done, Click Save.

If you have multiple assets of the same type to modify, use the Multi Edit tab to edit them in bulk. There
are three types of multi edit operations:
Step Edit lets you edit one asset at a time sequentially. Once youve edited and saved
your changes for one asset, the properties for the next asset are displayed
automatically. See Modifying Assets Sequentially.
List Edit lets you edit properties on all assets in a list. You provide property values to
one asset, then scroll to the next in the list and so on: after youre finished, you save all
of your edits at once. See Modifying All Assets in a List at Once.
Apply to All lets you apply a set of property values to a selection of assets. See
Applying One Set of Property Values to Several Assets at Once.
Before you can edit assets in bulk, you need to first add the assets to the Multi Edit tab. See Adding assets
to the Multi Edit Tab for instructions.
116
All multi edit operations require you to configure property groups, which are groups of properties
available for modification at the same time. When you select a multi edit button, you also select a
property group whose properties display in the Details pane. To learn how to create property groups, see
the Creating and Defining Property Groups section of the Configuring the Asset Manager chapter in the ATG
Note that you can use multi edit to update properties in all of the same ways as you can when you modify
assets individually, except one: you cant create a new asset in the context of another asset. For example, a
product has a Small image property that might hold a media-internal-binary asset. Its possible to select
an existing media-internal-binary asset, but not create a new one here. Also, global and local facets cant
be modified in bulk.
Adding Assets to the Multi Edit Tab

When you want to modify assets in bulk, you need to add them to the Multi Edit tab. Any asset can by
added to the Multi Edit tab, except facets, base search configurations, search configurations, and search
configuration folders. To add assets:
1.
Locate the assets you want to add to the Multi Edit tab in the Browse tab, Search tab,
or Project tab. See the appropriate section in this chapter for instructions on locating
assets.
2.
Click the checkbox beside each asset. Keep in mind that the assets you add can be
different asset types or unrelated to each other.
3.
Click the Add to Multi Edit button.

The Multi Edit tab label accounts for the number of asset added to the tab. If you open
the tab, you see the assets you added in the alphabetized asset list.
Assets are removed automatically from the Multi Edit tab when a session expires or you log out. You can
also select assets and use the Remove from Multi Edit tab button to remove them.
Modifying Assets Sequentially

Use the Step Edit option when you want to modify the property values in a series of assets, one at a time.
Once youve made changes to one asset in the list, the next asset is presented to you automatically.
After you begin the editing process, you cant add other assets to the Multi Edit tab. You can exit out of a
Step Edit operation at any time by clicking the Exit Step Edit button on the Navigation pane.
Use Step Edit as follows:
1.
In the Multi Edit tab, select the type of asset you want to edit from the Filter by
dropdown list. If all of the assets in the Multi Edit tab are the same asset type, skip this
step.
The list that displays includes only assets of the selected type.
2.
Insert a check in the checkbox besides the assets you want to edit now, either by
clicking the checkbox beside each asset individually, or clicking the global checkbox
on the top of the asset list to check all at once.
117
3.
Click the Step Edit button and, from the dropdown list that displays beneath it, select
the property group that holds the properties you want to modify. The All option,
which is the only option provided out-of-the-box, displays the properties that are
visible when the asset is selected in other tabs or views.
Screen elements that arent usable in the Step edit process, such as the Apply to All
button, List Edit button and checkboxes beside assets are removed from the
Navigation pane. The Details pane displays Step Edit, the name of the property
group, and the properties in that group.
4.
Modify properties as needed.
118
5.
Use the appropriate button to complete the operation:

The Review Changes button overwrites the current property values with
values in the last checked in version of the asset. See Undoing Property Value
Changes for information.
The Prev button selects the previous asset in the list and displays the assets
properties in the Details pane. Changes you made to the current asset are not
saved.
The Save Prev button saves your updates to the current asset and selects the
previous asset, displaying its values in the Details pane.
The Save button saves your changes to the current asset.
The Save Next button saves your updates to the current asset and selects the
next asset, displaying its values in the Details pane.
The Next button selects the next asset, displaying its values in the Details pane.
Changes you made to the current asset are not saved.
The Exit button leaves the Step Edit operation, returning the Navigation pane
to its pre-Step Edit state.
Modifying All Assets in a List at Once

Use the List Edit option to view properties from multiple assets in a list and provide unique values to each
property, which are then updated at the same time. The assets you edit must be the same asset type.
After you begin the editing process, you cant add other assets to the Multi Edit tab. You can exit out of a
List Edit operation at any time by clicking the Exit List Edit button on the Navigation pane.
To use the List Edit multi edit option:
1.
step.
2.
119
3.
Click the List Edit button and, from the dropdown list that displays beneath it, select
the property group that holds the properties you want to modify. There are no
property groups provided out-of-the-box.
Screen elements that arent usable in the List Edit process, such as the Step Edit
button, Apply to All button, and checkboxes beside assets, are removed from the
Navigation pane. The Details pane displays List Edit, the name of the property group,
and the properties in that group.
4.
To jump to properties for a particular asset, click an asset in the Navigation pane.
5.
Modify properties as needed.
120
6.
Click Save All.

A confirmation page displays in the Details pane, listing all changed assets in the
Successful section and assets you attempted to change that encountered errors in the
Unsuccessful section. Also, by looking at the assets in the Navigation pane, you can
see a green check beside changed assets and a red dot beside the assets that couldnt
be changed due to errors.
7.
Click the Exit button.
Applying One Set of Property Values to Several Assets at Once

Use the Apply to All option when you want to provide the same property values to a set of assets. The
assets you edit must be the same asset type. When you edit properties, you fill in a sheet of properties by
indicating to overwrite current property values with new ones, clear current values from a property, or
keep the current property value. Its also possible to click one selected asset and apply its values to all
other selected assets. Properties that require values upon asset creation, for example the list price of a
SKU, must have a value at all times. If you attempt to clear a value from such a property in Apply to All
mode, all of your modifications on that set of assets are canceled.
After you begin the editing process, you cant add other assets to the Multi Edit tab. You can exit out of
Apply to All operation at any time by clicking the Exit Apply to All button on the Navigation pane.
To use the Apply to All multi edit option:
1.
step.
2.
121
3.
Click the Apply to All button and, from the dropdown list that displays beneath it,
select the property group that holds the properties you want to modify. There are no
property groups for Apply to All provided out-of-the-box.
Screen elements that arent usable in the Apply to All process, such as the Step Edit
button and checkboxes beside assets are removed from the Navigation pane. The
Details pane displays Apply to All, the name of the property group, and the
properties in that group.
122
4.
If you want to use one assets property values as the basis of your update, click that
asset name in the Navigation pane.
5.
You are required to indicate the value you want ATG Merchandising to use for each
property:
To provide a new property value, click the Select Update Action button and,
from the dropdown list that displays, select Change. Then, use the text box or
buttons beside the property to insert a new value for the property.
To clear the current value from a property, click the Select Update Action
button and, from the dropdown list that displays, select Clear.
To indicate that a value should not change, click the Select Update Action
button and, from the dropdown list that displays, select Keep Existing Value.
(This action is selected by default, so you dont need to do this unless you
previously selected a different update action.)
6.
Save your changes by clicking Apply to All.

The Details pane displays a confirmation page that lists assets that have changed and
those that have not. Also, by looking at the assets in the Navigation pane, you can see
a green check beside changed assets and a red dot beside the assets that couldnt be
changed due to errors.
7.
Click the Exit button.
123
Previewing Assets
See how your assets will display on your site by previewing them in the actual JSPs your site uses. An
administrator must first set up asset preview by following the instructions provided in the Setting up
Preview Features chapter in the ATG Business Control Center Administration and Development Guide.
When you preview assets, you see how they would appear on your site with the property values they
have in the current project. Follow these steps to preview an asset:
1.
Using the Browse tab, Search tab, Project tab, or Multi Edit tab locate the asset you
want to preview, then click its name. See Locating Assets for instructions.
2.
If youve made recent changes to the asset, click Save, so those changes will be
reflected in the preview. Otherwise, use Revert to revert properties to their previously
saved values.
3.
In the Details pane, click Preview.

A second browser window opens with the asset information organized in the JSP
designed for that asset type.
4.
When you are finished, close the secondary browser window.

When there are differences between an assets currently property values and those in the last checked-in
version, you can view the set of values side-by-side and select which ones youd like to use. You may use
some values provided in this project (the Name, for example) and some from the previous one (Template).
To override property values in the current project with values from the previous one, follow these steps:
1.
Using the Browse tab, Search tab, Project tab, or Multi Edit tab, locate the asset you
want to modify, then click its name. See Locating Assets for instructions.
For SKU links, select a SKU that uses the SKU link. Find the Bundle links
property, and then click the SKU link name.
For configurable properties, select a configurable SKU that uses the
configurable property. Find the Configurable Properties property, and
then click the configurable property name.
For configurable options, select a configurable SKU that has a configurable
property that uses the configurable option. Find the Configurable
Properties property, and then click the configurable property name. Find the
Configurable Options property, and then click the configurable option
name.
2.
Click Review Changes in the Details pane to display the properties for the current and
previous project side-by-side. Notice that only the properties that have different
values in the two versions display here.
124
3.
Click the checkbox beside each property for which youd like to use the earlier
versions value.
4.
Click Revert Selected Properties to save your selection.
The list of differing property value refreshes and properties you selected are removed
from the list.
5.
Click the Back to Asset link.
6.
Click Save.
125
126
9 Defining Promotions
Once you have created a promotion, you need to define how and when it is used. Unlike other assets,
promotions are only significant and usable when their properties are filled in. This section describes the
various properties defined for promotions. Keep in mind that your version of ATG Merchandising may
display more or fewer properties, depending on how your site administrator configured your product.
To define a promotion:
1.
Locate the promotion you want to define using the Search tab, the Project tab, or
Promotions view of the Browse tab. See Locating Assets for instructions.
2.
Click the name of the promotion.

The Details pane displays the properties for the promotion.
3.
Provide values to its properties. Each property is described in one of the following
sections:
Define discount rules in the Conditions tab. See Building Discount Rules.
For item discount promotions, specify the items that a promotion applies to in
the Offers tab. See Defining a Promotion for a Particular Asset.
Decide when a promotion is active and usable. See Specifying When a
Promotion is Active.
Provide general information about the promotion. See Updating Other
Promotions Properties.
4.
Click Save.
Information on defining coupons, which are a type of promotion, see Updating Coupon Properties.
Building Discount Rules

As part of the process of defining the properties in a new promotion, you create a discount rule, which
specifies the circumstances under which a promotion applies.
You begin to build a discount rule by selecting a promotion and clicking the Conditions tab. Beneath the
Grant the discount under the following conditions label is a text box that you use to build discount rules.
By default, the condition is Always. If you leave this rule as it is, the system applies the discount defined
by the Discount type and Discount price properties to all items in the product catalog.
127
9 - Defining Promotions
To limit the scope of the promotion, you define a particular situation in which the promotion is offered.
Click Always to display a dropdown list with options Always, When, and For. Selecting When or
For displays a series of conditions that appear as a sentence. The items you see in the rule are the first
item in a dropdown list from which you can select a different item. Sometimes an item will be an empty
space that you fill in by selecting a repository item or entering text.
Rules can be as simple as When customers express checkout is true or as complicated as For next 3
products in the Mens Jerseys category or (Womens Active Wear and Womens accessories). Note that
discount rules can incorporate complex and/or statements that designate an order of operations using
parentheses. The rule wizard will sometimes include parentheses automatically to organize items into
phrases.
At the end of most rules, youll see a diamond or parenthesis. If you want to add a new phrase to a rule,
click the last element and select the appropriate conjunction: and or or.
Defining a Promotion for a Particular Asset

When you create promotions that use an item discount type, you can focus the promotion on a particular
item or set of items. For example, a visitor qualifies for a Free Water Bottle promotion when that visitor
buys 3 pairs of brand X biker shorts. If you dont specify a particular item, the promotion applies to all
items; all users qualify for a free water bottle regardless of the contents of their cart.
To specify the items that a promotion applies to, click the name of the promotion, then click the Offer tab.
Use the space beneath the Apply the discount to the following items label to build an offer rule, by
changing the default selection, all items, to every or up to. You build an offer rule in much the same
way you build a discount rule in the Conditions tab. See Building Discount Rules for guidance.
Specifying When a Promotion is Active

When you configure a promotion, you define the promotions lifecycle. Click the promotions name and
update the properties that determine when a promotion is active, delivered, and usable.
The Enabled property on the General tab is the most important of a promotions properties because it
governs the promotions availability. If a promotion is disabled (enabled=false), the promotion is not
advertised or useable despite the values provided to its other properties. An enabled promotion is visible
to visitors only when youve implemented them in a JSP or scenario. By default, promotions are enabled.
If you want to specify a range of dates during which promotions may be applied, you need to do three
things:
1.
Keep the Automatically apply to all orders property in the Distribution tab set to
false. This property is set to false by default, indicating that values you provide to
promotion properties are used. For more information about this property, find it in the
table in the Updating Other Promotions Properties section.
2.
Set the Usage period property on the Usage Limits tab to true.
128
3.
Use the Usage start date and Usage end date properties on the Usage Limits tab to
define the date range during which the promotion can be used. Or, if you want to
make a promotion available for some number of minutes, use the Redeemable for
property, also on the Usage Limits tab.
Promotions that dont have usage dates expire only when they are disabled.
Updating Other Promotions Properties

Update the following properties as needed. This table contains the complete set of properties available
for promotions.:
Property Name and Location
Description
Automatically apply to all orders
Indicates whether the promotion applies for all

visitors who meet the discount rule (true) or to
a restricted grouping of visitors based on
additional promotion property values (false).
In the Target Audience grouping on the

Distribution tab
If you set this property to true, all visitors who

meet the criteria in the promotions discount
rule defined in the Conditions tab and offer rule
in the Offer tab (if specified) qualify for the
promotion. That means, the promotion is
offered an unlimited number of times, to all
visitors (including anonymous visitors), for use
on an unlimited number of orders, for as long
as the promotion is enabled.
If you set this property to false, you can
specify values to the following properties in
order to restrict who will receive the
promotion:
- Give to a customer more than once
- Give to anonymous customers
- Number of uses allowed per customer
- Usage period
- Redeemable for
- Usage start date
- Usage end date
Also, if you set this property to false, you
must create a scenario that offers the
promotion to the appropriate visitors.
129
Closeness Qualifiers
In the Promotion Upsell grouping on the

Distribution tab
Holds the Closeness Qualifiers associated with

the promotion. A Closeness Qualifier is an
upselling incentive thats made visible to
visitors who nearly qualify for a promotion.
- Replace one Closeness Qualifier with another
by locating the Closeness Qualifier in the table
and clicking the Edit button beside it in order
to open the Select an Item dialog box. Navigate
to the Closeness Qualifier replacement, click
the radio button beside it, and then click OK.
- Disassociate a Closeness Qualifier from the
selected promotion by clicking the Delete
button beside the Closeness Qualifier.
- Create a new Closeness Qualifier that will be
associated with this promotion by clicking Add
New. The Details pane contains properties for
creating and defining a Closeness Qualifier.
Provide a name and other necessary
information, then click Create.
- Add an existing Closeness Qualifier by clicking
Add Existing to open the Select an Item Dialog
box. Locate all Closeness Qualifiers by clicking
Find. Navigate to the Closeness Qualifier you
want to add, click the radio button beside it,
and then click OK.
Creation date
In the Basics grouping on the General tab
Description
Discount amount

Discount percentage
Discount price
Holds the time and date that you created this

new promotion. This is a read-only text box,
and ATG Merchandising provides a value to it
automatically.
Holds a short display name for this promotion.
You can use this name to identify the
promotion to visitors on, for example, a
checkout page or an order form.
Holds the amount reduced from the price. Do
not include a currency symbol. This property
exists for amount off promotions only.
Holds the percentage that will be deducted
from the total when the promotion is applied.
Do not include a percentage sign. This property
exists for percentage off promotions only.
Holds a discounted price. Do not include a
currency symbol. This property exists for fixed
price promotions only.
130
Discount type
Distribute starting
In the Schedule grouping on the Distribution tab
Distribute through
In the Schedule grouping on the Distribution tab
Enable Closeness Qualifiers
In the Promotion Upsell grouping on the

Distribution tab
Enabled

Give to a customer more than once
In the Multiple Uses grouping on the Usage Limits

tab
Holds the type of promotion you specified

when creating the promotion. The value in this
property corresponds to the name of the
Promotions repository item type that
represents this kind of promotion. This is a
read-only text box, and ATG Merchandising
provides a value to it automatically.
Holds a date and time. This property does not
affect promotion distribution unless you
configure a scenario to use to it. For example,
you can set up a scenario that gives a
promotion when the current date is after the
Distribute starting date.
Holds a date and time. This property does not
affect promotion distribution unless you
configure a scenario to use to it. For example,
you can set up a scenario that stops
distributing a promotion when the current date
is after the Distribute through date.
Indicates whether Closeness Qualifiers are
currently available to visitors (true). A
Closeness Qualifier is an upselling incentive
displayed to visitors who nearly qualify for a
promotion.
Indicates whether the promotion is active
(true). See Specifying When a Promotion is
Active for more information.
Indicates whether a promotion may be offered
to a visitor more than once (true) or one time
only (false).
Note that a visitor who has several copies of a
promotion can apply it to a given order once,
by default. You can permit such promotions to
apply multiple times to a given order, if you
change this behavior as described in the Using
and Extending Pricing Services section in the ATG
Commerce Programming Guide for more
information.
Note: This property is applicable only if the
Automatically apply to all orders property is set
to false.
131
Give to anonymous customers
In the Target Audience grouping on the

Distribution tab
Indicates whether the promotion is offered to

all site visitors (true) or logged in visitors only
(false).
to false.
Media
On the General tab
Holds the media assets associated with the

promotion. Use the buttons beside it to:
- Associate a media asset to this promotion by
clicking Add Existing to add a row to the table.
Provide a label that identifies the media assets
usage in the Key column, and click the Edit
button to open the Select an Item dialog box.
Navigate to the media asset, click the radio
button beside it, and then click OK.
- Create a new media asset that will display as
media for this promotion by clicking Add New,
selecting a media type from the Select Asset
Sub-Type dropdown list, entering a label for
media assets usage in the Key text box, and
clicking Next. The Details pane displays with
empty media properties that you should fill in
as described in Creating Media Assets and
Folders.
- Disassociate a media asset from the selected
promotion by clicking the Delete button
beside the media asset.
Name
In Basics grouping on the General tab

Number of uses allowed per customer

tab
Holds the name that identifies the promotion

in the ATG Merchandising UI and ATG Control
Center.
Holds the number of orders for which a visitor
can use this promotion. Setting this property to
infinite, for example, permits the promotion
to be used in a limitless number of orders.
Note that this property does not restrict the
number of times a promotion is applied to a
given order. You can enforce that limitation to
shipping promotions only. See the One use per
order property to learn more about that
restriction.
to false.
132
One use per order

tab
Order of application
In the Priority grouping on the Usage Limits tab
Indicates whether a shipping promotion can be

applied once per an order (true) or multiple
times to the same order (false). Note that this
property is available for shipping promotions
only.
Holds the order in which this promotion should
be applied if a visitor qualifies for multiple
promotions.
If a visitor qualifies for more than one
promotion, the system applies each promotion
cumulatively, calculating the new price for the
order by combining the various discounts. The
order in which the system combines the
discounts might be important in situations
such as the following: You give two discounts
to the same visitor, one (Promotion A) offering
$10 off any product and another (Promotion B)
offering 50% off any helmet. Suppose the
visitor orders a helmet that usually costs $30. If
the system applies the promotions in the order
A-B, the final price of the helmet is $10. If the
order is B-A, the final price is $5.
Note that if you give the same order of
application number to more than one
promotion, when the system cycles to that
number, it calculates the discounts for those
promotions randomly.
promotionId
In the Info grouping on the General tab
Holds the unique identifier for the promotion.

In the ATG Merchandising UI and the ATG
Control Center, a promotion is identified by its
name, not ID.
Updating Closeness Qualifier Properties

Closeness Qualifiers, which inform customers who nearly qualify for promotions what they must do, have
the following properties:
133
Property Name
Description
Grant the Discount
Holds the rules that define when the Closeness Qualifier is used. See
Building Discount Rules for an explanation of how to define this
property.
In the Conditions tab

ID
In the General tab

Name
Holds the automatically generated repository ID for the Closeness

Qualifier.
Holds the name that identifies the Closeness Qualifier.
In the General tab

Order of Applications
In the General tab

Upsell Action
In the General tab
Holds the number used to prioritize this Closeness Qualifier when a

user qualifies for multiple Closeness Qualifiers.
Holds the Upsell Action that contains the products affected by the
Closeness Qualifier. Use the buttons beside this property to:
-- Replace one Upsell Action with another by locating the Upsell
Action in the table and clicking the Edit button beside it in order to
open the Select an Item dialog box. Locate all Upsell Actions by
clicking Find. Navigate to the Upsell Action you want to add, click the
radio button beside it, and then click OK.
- Disassociate a Upsell Action from the selected promotion by clicking
the Delete button beside the Upsell Action.
- Create a new Upsell Action that will be associated with this
promotion by clicking Create. The Details pane contains properties
for creating and defining a Upsell Action. Provide a name and other
necessary information, then click Create.
- Add an existing Upsell Action by clicking Edit to open the Select an
Item Dialog box. Locate all Upsell Actions by clicking Find. Navigate
to the Upsell Action you want to add, click the radio button beside it,
and then click OK.
Updating Upsell Actions

An Upsell Action holds the products that you want to upsell. By purchasing products in the Upsell Action,
a user could qualify for the promotion. The following are properties of Upsell Actions:
134
Property Name
Description
Dynamic Upsell Products
Holds the products that are part of the content group identified in
the Upsell Products Group property. This property is populated
automatically at runtime.
Fixed Upsell Products
Holds a fixed list of products included in the Upsell Action. See

Fixed Child Categories for a description, substituting product for
category as the type of asset you are replacing, rearranging,
removing, moving, or creating.
ID
Holds the automatically generated repository ID for the Upsell

Action.
Name
Holds the name that identifies the Upsell Action.
Upsell Products Group
Holds the content group that dynamically determines products

affected by the Closeness Qualifiers.
Upsell Products
Holds the complete set of products specified using the two

methods (assembled by content groups or entered directly) for an
Upsell Action. This property is populated automatically at runtime.
Updating Coupon Properties

Coupons have three important properties:
Property Name
Description
Expiration Date
Holds the date and time on which the coupon becomes inactive. Although a
coupons expiration date is separate from the promotions usage date, be
sure to make these two dates coincide: when a user redeems a coupon, the
promotion must be active. Conversely, you may set a coupon to expire before
the promotion if you want to offer it in conjunction with a different delivery
mechanism, such as a scenario. See Specifying When a Promotion is Active
for information on setting usage promotion dates.
ID
Holds the unique identifier for the coupon, which also serves as the coupon
code a user enters in order to redeem the coupon.
- Associate a promotion to the coupon by clicking the Edit button to open
the Select an Item dialog box. Click Find to locate all promotions. Navigate to
the promotion, click the radio button beside it, and then click OK.
- Disassociate a promotion from the selected promotion by clicking the Clear
button beside the media asset.
135
Promotion
Holds the name of the promotion that defines the circumstances in which the
coupon is offered and active.
136
10 Using and Defining Price Lists
A price list is made up of a list of prices for products and SKUs. Typically, prices are defined in a base price
list and inherited by other price lists. That way, you can create a hierarchy of price lists and enter prices
only when you want to override inherited values. Use the following sections define your price lists and the
prices they provide:

The following table contains all properties available for price lists. Keep in mind that your version of ATG
Merchandising may display more or fewer properties, depending on how your site administrator
configured your product.
Property Name
Description
Base price list
Holds the price list from which the selected list inherits prices.
- Associate a base price list to the selected list, by clicking the Edit button.
When the Select an Item dialog box opens, navigate to the price list, select it,
then click OK.
- Disassociate a base price list from the selected list, by clicking the Delete
button. When a base list is deleted, any prices from it that are inherited by
other lists are removed from them.
- Create a new price list, by clicking the Create button. The Details pane
displays with empty price list properties that you should fill in as described in
Creating Price Lists and Price List Folders.
Creation Date
Holds the time and date on which the price list was created. This is a read-only
text box, and ATG Merchandising provides a value to it automatically.
Description
Holds a description for the price list.
137
10 - Using and Defining Price Lists
End date
Holds an end date and time. This property is used in conjunction with the
Start Date property to provide the date range during which the selected asset
is active on the Web site. In order for these dates to be used, you need to
implement the Start And End Date collection filter.
Id
Holds the unique identifier for the price list. Price lists are identified by name,
not ID in ATG Merchandising and ATG Control Center. This is a read-only text
box, and ATG Merchandising provides a value to it automatically.
Last modified date
Holds the time and date on which the price list was edited. This is a read-only
text box, and ATG Merchandising provides a value to it automatically.
Locale
Holds the locale used to determine the currency and symbol used by the
prices in the price list. Note that when prices are displayed in browsers
supporting other locales, prices are calculated based on the units in the Price
List Pricing tab and currency that represents the locale you supply here.
Name
Holds the name of the price list, which is used to identify it in ATG
Merchandising and the ATG Control Center.

When you create a price list for the first time, it is empty, so prices need to be provided for each product
and SKU. Other price lists you create can inherit all prices from existing price lists, or inherit some prices
and override others. Keep in mind that changing a price in a base list also changes the price in the lists
that inherit it.
One advantage of price lists is that they permit you to define one of three types of prices for each asset.
Each price applies for a specific purchased quantity:
A single price applies the same price to each item regardless of how many are
purchased.
A bulk price, which is a type of volume pricing, provides the same price to each item,
and the price used depends on the quantity purchased.
A tiered price, which is a type of volume pricing, defines pricing levels based on
quantity or weight. For example, one price applies to the first 10 items and second
price applies for the next 10.
For a complete explanation of volume pricing, see the Description of Volume Pricing section in the Using
Price Lists section of the Using and Extending Pricing Services chapter in the ATG Commerce Programming
Guide.
There are two ways to locate prices:
If you want to modify the prices for products or SKUs in the same price list, find the
price list in a price list view.
138
If you want to modify the prices for a given product or SKU across price lists, locate
that product or SKU.
Each product, SKU, and price list has a Price List Pricing tab that contains a table for managing prices. For
products and SKUs, each row represents a price list, and the type of price is visible in the Prices column.
The contents of the table visible when a price list is selected depends on whether you indicate youd like
to see products, SKUs, or both listed. The rows hold prices given to a specific asset for that price list.
The way you modify a price in the table is the same regardless of how you accessed it. You use the
checkboxes and links in the Prices column to indicate whether you want to enter a single price, enter a
volume price, or inherit a single or volume price from a base list.
Follow these steps to update prices in pricelists:
1.
Locate the price you want change by either selecting a product, SKU, or price list in the
Search tab, the Project tab, the Multi Edit tab or Catalog view or Catalog Orphans view
of the Browse tab. See Locating Assets.
2.
Click the Price List Pricing tab.

The Details pane contains a table in which each row represents a price list.
3.
Locate the price list you want to modify, by scrolling through the table.
If you selected a product or SKU in the Navigation pane, you can use the Hide
Price Lists with Inherited Prices checkbox to display only the price lists that have
unique prices.
If you selected a price list in the Navigation pane, select the type of assets you
want to modify from the Show dropdown list. You can also limit the assets in
the table by entering a few letters in the Starts with box and clicking List to
display the assets that begin with those letters.
4.
If you want to provide a single price, follow the steps below:

To override an inherited price, deselect the Inherited checkbox beside the price
list. Then, enter the new price in the text box that displays.
To replace a price unique to this list with a new unique price, enter the new
price in the text box beside the price list.
To replace a price unique to this list with an inherited price, click the Inherited
checkbox beside the price list.
5.
If you want to provide a volume price, follow the steps below:

To override an inherited price, deselect the Inherited checkbox beside the price
list. Click the Vol. checkbox, then the Volume Price link in the Price column. See
Defining Volume Pricing section.
To replace a volume pricing strategy unique to this list with a new volume
pricing strategy, click the Volume Price link in the Price column. See Defining
Volume Pricing section.
To replace a volume pricing strategy unique to this list with an inherited
volume pricing strategy, click the Inherited checkbox beside the price list.
139
To replace an individual price unique to this list with a unique volume pricing
strategy, click the Vol. checkbox in the Price column. See Defining Volume
Pricing section.
6.
Click Save.
Defining Volume Pricing

By providing volume prices, the price of an item is based on the quantity being purchased. Follow these
steps:
1.
Once youve opened the Volume Pricing dialog box, click the radio button beside the
type of volume pricing you want to use:
Use Bulk to apply the same price for all items. The price is determined by the
quantity purchased.
Use Tiered to define quantity ranges, so that one price is used for items in one
quantity range (for example, the first 10 items) and different price used for
others (the next 6).
2.
Click Add Price to add a row for supplying a quantity range and price.
3.
In the Quantity column, provide the number that represents the fewest number of
items to which the price in the corresponding Price column should apply.
4.
In the Price column, enter the price that will be used when items of the specified
quantity are purchased.
5.
Click Add Price to add a second row.
6.
In the Quantity and Price columns, provide the appropriate values, taking into account
the way that prices are tallied:
For bulk pricing, the second quantity represents the fewest number of items to
which the price in the corresponding Price column should apply. If the first
quantity is 10 and the second 20, an order of 19 items uses the first price for
each item; however, an order of 29 uses the second price for each item.
For tiered pricing, the second quantity represents the top of the range that
begins with the first quantity. If the first quantity is 10 and the second 20, the
price for an order of 19 uses the first price for the first 10 items and the second
price for the remaining 9.
7.
Repeat steps 5 and 6 as needed.
8.
Click OK.
9.
Click Save.
Providing Price Lists to Users

There are two static ways to provide price lists to users:
Assign a price list directly to individual users. See Assigning Price Lists to Users.
140
Assign a price list to an organization, so all users in an organization are provided with
prices from that list. This option is available to customers who use ATG Business
Commerce with ATG Merchandising. See Assigning Price Lists to Organizations.
Its also possible to provide a price list to users dynamically, by specifying a price list based on a set of
circumstances. For example, you can create a scenario that, when a user registers, assigns a price list to
him or her. Then, after the user makes a purchase or clicks a particular link, you can assign a different price
list. To learn more about scenarios, see the ATG Personalization Programming Guide.

To assign price lists to individual users, follow these steps:
1.
On the ATG Business Control Center home page, expand the Personalization entry in
the Operations list. Click Users.
2.
In the Navigation pane, click the name of the user to whom you want to assign a price
list.
3.
Click the BtoB Commerce tab.
4.
Find the Price list property and associate a list to it:

To create a new price list, click Create to display empty textboxes that you use
to describe the price list. See Creating Price Lists and Price List Folders for
instructions. Once you are done, the price list is automatically associated with
the user.
To assign a price list, click the Edit button to open the Select an Item dialog box.
Navigate to the price list in the Browse tab or use the Search tab to search for it.
Once youve located the price list, click it, then click OK.
5.
Click Save.
Assigning Price Lists to Organizations

Customers who use ATG Business Commerce can define organizations and assign users to them. That
way, you can define properties for an organization, which are inherited by all users in the organization.
One property identifies a contract, which is an asset that associates a catalog, price list, and payment
terms. So, if you want to assign a price list to all members of an organization, you assign the price list to
the contract, then assign the contract to the organization.
To associate a price list to an organization, follow these steps:
1.
On the ATG Business Control Center home page, expand the Personalization entry in
the Operations list. Click Users.
2.
From the Show dropdown list, select Organizations.
3.
In the Basics property grouping on the Details pane, find the Contract property.
4.
If you havent assigned a contract to the organization, do so now:

To create a new contract, then assign it to the organization, click Create. When
the Details pane contains properties that describe a contract, enter a contract
141
name, then click Create. The new contract is automatically associated with the
organization. Skip to step 6.
To assign a contract, click the Edit button to open the Select an Item dialog box.
Navigate to the contract in the Browse tab or use the Search tab to search for it.
Once youve located the contract, click it, then click OK.
5.
Click the contracts name to make its properties visible in the Details pane.
6.
Find the Price List property, and associate a price list to the contract:
To create a new price list, then assign it to the contract, click Create, and see for
instructions. Once you are done, the price list is automatically associated with
the contract. Return to the contract by selecting it from the Breadcrumb
dropdown list on the top of the Details pane.
To assign a price list, click the Edit button to open the Select an Item dialog box.
Navigate to the price list in the Browse tab or use the Search tab to search for it.
Once youve located the price list, click it, then click OK.
7.
Click Save.
142
11 Defining Facets
Facets are assets you design to organize virtual groupings of products based on a product property value.
When you implement facets in site pages, you see groupings that appear as a range of selections named
for product property values or letters in the alphabet that represent them. By clicking an A-C selection,
you can view products, for example, that have a manufacturer name that begins with those letters.
Creating facets involves selecting a faceting property (Manufacturer Name, in this example) and making a
general decision on how selections will be organized. In order for your facets to be useful, you need to
consider how you want to control the way your selections are generated. If you want dynamically
generated selections, approximately how many and how many property values should be represented in
each. Or, if selections are fixed, should each represent one property value or a range?
This section provides guidance on setting those and other facet property values, which are visible when
you click a facet in Facet view of the Browse tab, the Search tab, or the Project tab, all of which are
described in Locating Assets. Before you define specific facets, its a good idea to develop a design for the
facets on your site because facets can have a complex inheritance and nesting strategy. For guidance, see
Designing a Site with Multiple Facets.
Use the following sections to learn how to set facet properties:
Note: If selections arent displaying on your site, one of the following situations may have occurred:
All products available to a facet have the same value for the Faceting Property. See
Setting General Facet Properties.
The rules you provide for building selections are too restrictive and cant be applied to
your products. See Setting the Defining Selections Property.
Designing A Site With Multiple Facets

The main benefit to facets is that they create virtual groupings of products organized by a product
property. You dont need to decide precisely which products to include or exactly how they should be
grouped: you need only to create a facet and specify the product properties it uses to organize products,
then decide what products it includes based on where in the catalog hierarchy it resides.
143
11 - Defining Facets
Once you define one facet, it is easy to see how you might want to use several facets together, so one
facet organizes products by price, for example, and another facet organizes them by manufacturer. When
you use multiple facets, consider the following:
What kind of facets work best together?
On your site, do you want facets to work and appear independently of each other or
nested in one another?
What products should the facets include and should all facets include the same
products?
Common Collaborative Facets

You can create facets that organize products based on any product or SKU property defined in your
catalog, but some properties are particularly good candidates. They are described in this section.
Many examples in this guide use a pricing facet that has a product list price or wholesale price property as
the faceting property. Organizing products by price is a helpful navigational device, given that price is an
important factor when purchasing products. Facets may produce ranges in $100 increments: $1-100,
$101-200, $201-300, etc. Sites that have products spanning a large array of prices may find it useful to nest
one pricing facet in another, so that larger groupings of products by price are then broken down into
smaller ones. For example, one pricing facet creates selections in $100 increments and, clicking one
selection, accesses a list of selections in $10 increments.
It may also be a good idea to create a facet that organizes products by category. For example, a clothing
category facet might contain facets for size, materials, or sale status. A category facet provides a good
starting point for a series of nested facets.
Most sites display products by category using a traditional tree hierarchy; using a category facet provides
two added benefits:
As is the case for all facets, the selections that organize products are generated on the
fly and the products contained in them are also determined dynamically.
Depending on the property you choose to be the faceting property Default parent or
Ancestor categories you can control whether a product is included only in the
category that contains it (the former), or that category as well as all of its parent
categories (the latter).
Keep in mind that a category facet is different from a facet associated with a category. A category facet
uses a product property that holds category information as the faceting property. For example, a category
facet appropriate for a clothing store is clothing type, which might divide products into selections for
womans clothing, mens clothing, shoes, and gear. Such a facet would be associated with the Global
Facets folder so that all categories defined in the catalog are available to it.
A facet associated with a category, conversely, is most likely to use a faceting property thats suited only
to the products in a particular category. A clothing store site might have a petite size facet associated with
the womans clothing category, for example, so women can view all clothing based on petite sizes.
Products in other categories (mens clothing, shoes, and gear) wont have petite sizes.
144
The main way to tell them apart is by knowing that a category facet is defined by how products are
organized (by category), whereas a facet associated with a category is defined by the products available
to the facet (the products in a particular category lineage).
Most faceting properties are the custom properties you design for your catalog that are unique to the
products you sell. For example, a rug store might have facets for dimensions, materials, country of origin,
and handmade/machine made. Usually, it is the values of properties unique to a set of products that best
distinguishes one product from another; such properties are ideal for facets. Any enumeration properties,
for example a material property that has options wool, polyester, and cotton, that can be divided up
further (types of wool include angora and cashmere) may be easily represented as nested facets.
Facets: Independent or Nested?

Consider a site that uses a price facet and a manufacturer facet. You may choose to have both facets
display on your site side-by-side, so users can navigate to products through price selections or
manufacturer selections. Each facet is independent of the other and provides the complete set of
products: you are giving users the option to locate products in one of two ways. Heres how the facets
may appear on your site in this situation:
Prices
Under $100
$101-200
$201-300
$301-400
Manufacturer
Bavary
Devonit
Fulksome
Horck
Illique
Pewvire
Tapple
Alternatively, you can nest the manufacturer facet in the price facet, which provides one set of products
organized in a two-tier system. You nest facets when you want to find the intersection of products that fit
both criteria, such as products for a certain price by a certain manufacturer. On the site, the facets might
be visible as follows:
Prices
Under $100
$101-200
$201-300
$301-400
Clicking the Under $100 selection might display the list of manufacturers that have products which cost
under $100, for example:
Under $100
145
Manufacturers
- Devonit
- IIllique
- Tapple
Again, clicking a manufacturer name might display the list of products by that particular manufacturer in
that price range.
The essential difference between nested and independent facets is that nested facets organize one set of
products in a tiered hierarchy, whereas independent facets organize the same products in two separate
groupings. It is possible to mix independent and nested facets. For example, you may want to present
price and manufacturer facets independently, but within the price facet, you can nest another price facet.
If your first price facet displays selections that range $100 and your site has many products under $100, a
second price facet could define smaller ranges of $10 increments. The initial site display resembles the
independent example:
Prices
Under $100
$101-200
$201-300
$301-400
Manufacturer
Bavary
Devonit
Fulksome
Horck
Illique
Pewvire
Tapple
Clicking the Under $100 link might display the following selections:
Under $100
$1 - 10
$11- 20
$21- 30
$31- 40
$41 - 50
$51- 60
$61- 70
$71- 80
$81 - 90
$91- 100
What determines whether a facet is independent or nested on site is its position relative to other facets in
Facet view. A facet that appears nested on a site also appears nested in Facet view. The facets described
earlier are represented as Price 100 Range, Price 10 Range, and Manufacturer Name facets in this Facet
view:
146
Notice that Price 100 Range and Manufacturer Name are located on the same level, but Price 10 Range
descends from Price 100 Range. In this example, all facets are global facets located in the Global Facets
folder. Nested facets can be associated with catalogs or categories as well as the Global Facets folder: for
example, a Size facet associated with a Clothing category may have Tall, Petite, and Regular facets
representing alternate proportions as follows:
Facets that dont have a nested relationship are independent of each other. If you have one global facet
and one local facet associated with a category, those facets are independent of each other. Likewise,
nested facets must exist in the same part of the hierarchy: you cant nest a local facet in a global one.
Place your facets in the appropriate position in the hierarchy either by specifying a parent to a facet when
you create it or by rearranging it later. For instructions on moving a facet, see Moving Assets.
Products Included in Facets

There are two ways to determine whether a product will be included in a facet:
Is the facet associated with a part of the catalog tree that makes it available to the
product?
147
Have catalogs or categories that contain the product been actively excluded from the
facet?
Global facets, by definition, include all products in the catalog. Local facets are associated with a catalog
or category and include only the products nested in that catalog or category. A price facet associated with
a Womens Clothing category includes products in subcategories Swimsuits, Shirts, and Pants, for
example.
That said, you have the option to hide individual global or inherited facets for catalogs and categories.
When you select a such a category on a site, for example, you see a subset of facets. Each category has
properties that control whether a category inherits global facets, facets associated with parent catalogs
(when custom catalogs are used), and facets associated with parent categories. You can also indicate that
only the products nested directly in that category use the facets associated with it, by blocking facets
from child categories.
Corresponding settings are available on catalog assets, when custom catalogs are used. Facet inheritance
properties are visible on the Facet tab when you select a category or catalog. Know that if a facet is
blocked from a category, such as Womens clothing, it is automatically blocked from all subcategories,
such as swimsuits.
For information on specific category and catalog properties, see Appendix: Asset Properties.
148

There are two general facet properties: Faceting Property and Name. Faceting Property refers to the
product property used to organize products into virtual selections. A facet that displays products
organized by price might have a Faceting Property set to child SKU List Price.
Note that a product accesses the properties of its child SKUs, so the faceting property includes most SKU
properties as well as most product properties by default. One side effect to this capability is that if a
product has two SKUs and a different price for each, a price facet may represent the product twice in its
selections: once for each SKU.
If you want to modify the properties available to be faceting properties, by adding custom properties or
removing out-of-the-box properties, follow the instructions provided in the Repository Indexing chapter of
the ATG Commerce Search Guide for instructions. All properties indexed by the search engine are
automatically included in the Faceting Property dropdown list.
The properties you see when you select a facet depend on the Faceting Property you selected. If you
change the Faceting Property and then change back to the original value, you are likely to lose property
values you set previously. If you want to use a different Faceting property for a given facet, it may be
simpler to create a new facet.
Its important to note that if all products have the same value for the Faceting property, for example, all
products are on sale so the on sale property, which is used as the faceting property, is set to true, the facet
is ignored and no selections are displayed. If selections were generated in this situation, there would be
just one, holding all products, which is unnecessary and not useful.
The name you give to a facet should loosely represent the Faceting Property you choose. The facet that
organizes products by price mentioned earlier might be called Price. Name your facets in a way that
makes it clear how products are organized by it.

The Defining Selections property governs the selections your site will use. The selections that display on
your site contain products with a property value that matches the faceting property value associated with
the selection. Use the Defining Selections property to decide how selections are created and
consequently, what they will contain. There are four options for this property:
One Selection for Each Value creates one selection for each faceting property value.
For a manufacturer facet, for example, each selection represents one manufacturer
name.
Dynamic Selections uses the guidelines you specify to create selections dynamically.
Typically, each selection represents several faceting property values. A price facet, for
example, produces selections that represent a range of prices.
Guided Selection Ranges uses the exact requirements you provide to create selections
dynamically. Typically, each selection represents several faceting property values. A
149
Monitor size facet, for example, produces selections that represent a range of sizes.
This option is available only if the faceting property is a number.
Specified Selections creates the selections you define. Each selection represents a
range of faceting property values. A price facet, for example, creates selections, each of
which represents the exact range of faceting property values you provided. This
option is available only if the faceting property is a number.
Keep in mind that, when you use any value other than One Selection for Each Faceting Property Value,
you specify parameters that determine the selections that display. If it is impossible to generate selections
based on the parameters you specify, for example you use the Guided Selection Ranges and require 5
selections when only 4 are possible, ATG Merchandising wont generate any selections.
With the Defining Selections property, you specify settings that determine selections on your site, which
in turn determines the criteria for the products held by each selection. Note that the order of products in
the selection is in no way affected by settings you provide here. For example, defining alphabetical
selections ensures that each selection contains products in the appropriate letter range, but it doesnt
alphabetize the products in that selection.
Using One Selection for Each Faceting Property Value

When you use One Selection for Each Faceting Property Value , you cause one selection for each faceting
property value to be generated. For a facet called manufacturer, each manufacturer has its own selection.
Its a good idea to use One Selection for Each Value when your faceting property has values that are
words, not numbers, and many products have the same value.
By default, all manufacturers are displayed; you have the option, however, to eliminate some
manufacturers or to cause only the manufacturers you specify to display. Keep in mind that implicitly or
explicitly excluding a manufacturer from displaying as a selection prevents the products that use that
manufacturer also from displaying.
Use the Specified Faceting Property Values property to list the particular faceting property values that you
want represented on your site as selections. Know that the values you specify here display on your site
even if those selections dont contain any products.
If you want to display the products manufactured by your two featured manufacturers, Callap and
Devonit, for example, you include them in the Specified Faceting Property Values property as follows:
1.
Beside the Specified Faceting Property Values property, click Add.
2.
In the row that displays, enter the faceting property value, Callap.
3.
To add another value, click Add again.
4.
In the row that displays, enter Devonit.

Two selections, one called Callap and the other called Devonit, will display to site
visitors. Products will appear in the selection named for the manufacturer they use.
5.
Because the selection appears on the site in the order you provide here by default, up
and down arrows are provided for making order adjustments. Click the Up arrow
beside Devonit so that it appears first and will display first on the site.
6.
Click Save.
150
To remove a faceting property value from the Specified Facet Values property, click the delete button
beside the value.
The Excluded Faceting Property Values property lets you prevent specific selections and their
corresponding products from displaying. If you are a clothing retailer, you might use this property to
display products by type then by size, which requires two facets: one called Type of Clothing and one
called Size. In order to exclude all pants, use this property to remove them from the Type of Clothing
facet:
1.
Beside the Excluded Facet Values property, click Add.
2.
In the row that displays, enter the faceting property value, Pants.
To remove a faceting property value from the Excluded Facet Values property, click the delete button
beside the value.
Note that if a property value exists in both the Specified and Excluded Facet Values properties, it will be
excluded from your site.
Using Dynamic Selections

The Dynamic Selections option lets you provide guidelines that ATG Merchandising uses to determine the
number of selections to display as well as the property value span used for each dynamically. So, when
you select this option, you must provide the information to the following properties:
Maximum Number of Selections specifies the highest number of selections that are
generated.
Minimum Faceting Property Values per Selection holds the minimum number of
property values that will display in a selection. For a Price facet, for example, the facet
values are the actual prices, so setting this property to 20 indicates that each selection
must include products that span at least 20 prices. Keep in mind that selections divide
products by the value they have for a given property. You use this property to define
the minimum number of property values per selection, not products per selection.
Minimum Span of Letters/Numbers Per Selection defines, for selections that organize
products alphabetically, the fewest number of letters represented in each selection.
For example, setting this property to 3 permits selections to assemble in groupings no
smaller than A-C, D-F, G-I, etc. Likewise, this property holds the fewest number of
numbers when the faceting property holds number values.
Its important to understand how these values are computed together to determine how selections are
arranged. Consider a facet called Manufacturer that organizes products by manufacturer name. The
properties are set as follows:
Maximum Number of Selections= 6
Minimum Faceting Property Values per Selection= 3
Minimum Span of Letters/Numbers per Selection= 2
Heres an alphabetized list of manufacturers: Baddell, Bavary, Bisputal, Callap, Devonit, Dralter, Fulksome,
Gacroy, Guster, Horck, Illique, Keckin, Laurate, Lemonsquash, Manfro, Pewvire, Prixsass, Quizle, Sellis,
Tapple, and Zer.
151
In order to determine the selections to create, ATG Merchandising works through the following logic:
1.
First, ATG Merchandising determines the first letter in the alphabet that begins a
manufacturer name (B) and the corresponding last letter to begin a manufacturer
name (Z) . Then, it determines the number of letters that span from one to the other
(25). Note that all letters, even those such as X, that do not begin a manufacturer
name, are included.
2.
Next, ATG Merchandising begins to apply the three property values you specified
systematically, beginning with the first. It divides the total number of letters (25) by
the maximum letters in a range (6) to compute a possible number of letters in each
selection (4).
3.
Then, ATG Merchandising creates selections that meet these parameters and
determines if they also meet the Minimum facet values per range setting (3). Note that
in the selections below, the number in parentheses is the number of manufacturers
represented in the selection:
B-E (6)
F-I (5)
J-M (4)
N-Q (3)
R-U (2)
V-Z (1)
4.
Because the last two selections have fewer manufacturers than the minimum (3), ATG
Merchandising runs through steps2 and 3 again using the next greatest possible
number of selections (5), and repeats this process until it produces selections that
meet both the maximum number of selections and minimum number of values
requirements.
5.
Once a list of selections fits those two criteria, the third criteria, maximum span of
letters in a range is applied. If ATG Merchandising can compute selections that meet
all three pieces of criteria, those selections will display on the Web site as follows:
Actual Selection
Selection as It May
Appear on the Site
Manufacturers in the Selection
B-I
A-I
*Baddell, Bavary, Bisputal, Callap, Devonit, Dralter,

Fulksome, Gacroy, Guster, Horck, Illique (11)
J-Q
J-Q
*Keckin, Laurate, Lemonsquash, Manfro, Pewvire,

Prixsass, Quizle (7)
R-Z
R-Z
*Sellis, Tapple, Zer (3)
* Products in selections wont appear in alphabetical order unless ATG Search or Search Merchandising
settings indicate they should.
152
Take note of the following two points. For one, even though the first manufacturer name in the alphabet
begins with B, the selection visible on the site will include an A. To provide a consistent feel, all letters,
even those that dont begin a manufacturer name, are available to the site.
Although the Dynamic Selections option attempts to distribute manufacturers and letters evenly across
selections, its unlikely for all selections to be equal on both counts.
If your faceting property is a number, a Round Selection Values to Nearest textbox works in conjunction
with the Dynamic Selections option. Specifying a number to this property causes ATG Merchandising to
factor this requirement into the calculations used to determine the appropriate selections just after
computing the Minimum Span of Letters/Numbers per Selection requirement. Note that the Round
Selection Values to Nearest property does not merely round up the values in a range used by a selection
name, but is part of the logic applied when generating the selections.
Using Guided Selection Ranges

When a faceting property is a number, the Guided Selection Ranges option is available to you. Guided
Selection Ranges lets you define exact requirements that are used to generate selections dynamically.
Guided Selection Ranges is different from the Dynamic Selections option because it provides exact
parameters, rather than maximum and minimum guidelines. When you use this option, you need to
provide additional information to these properties:
Number of Selections defines the precise number of selections you want to be

available to your site.
Numerical Size of Selections determines how many numbers are represented in a

selection. For example, setting this property to 5 permits selections to assemble in
groupings of 1-5, 6-10, etc.
Note that if a facet represents a size, for example, and there are no items in size 6, size 6 is excluded from
both the selection ranges displayed on your Web site and the selection name. Selections 2-4, 8-10, 12-14
display on the site for this example when the number of selections is 3 and the number span is 2.
Using Specified Selections

Specified Selections, which is visible only when the faceting property is a number, lets you create the
exact selections that will be visible on your site. Each selection is made up of a range that begins and ends
with the points you specify. Note that the end point for one selection is the starting point of the next, for
example, points 1, 8, 23, 66 produces selections 1-8, 8-23, and 23-66.
Follow these steps:
1.
Beside Add Range Point button, provide the number that begins the first selection.
Click Add Range Point.
2.
To add an end point, enter another number, and click Add Range Point.
3.
Repeat steps 1 and 2 until youve defined the start and end points for each selection.
153
The Facet Value Sorting property determines the order selections are displayed in. Select one of the
following three options:
Numeric/Alphanumeric arranges selections numerically or alphabetically, such as 1-5,

6-10, etc. or A-F, G-L, etc.
Value Count arranges selections by the number of products they contain. The
selection with the most products displays first and the selection with least displays
last.
Specified Order uses the order of faceting property values in the Specified Faceting
Property Values property.
This order affects selections only. Products in those selections are not influenced by the order you provide
here.

Each facet has a Child Facets tab you can use to manage the facets nested in the selected facet, by
creating, ordering and deleting such child facets. On the Child Facets tab, a Child Facets Table provides
the following tools:
Use Add New to display empty facet properties that, once filled in, are used to define a
new facet. When you click Create, the new facet displays in the Navigation hierarchy
beneath the originally selected facet.
Use the numbers beside a facet to rearrange its position in the tree. To preview the
new order, click Reorder.
Use Delete beside a facet to delete it.
154
12 Defining Search Configurations
Search configurations are sets of rules that affect the display of search result. When a site visitor issues a
search query on the Commerce site, ATG platform components determine which search configuration to
associate with the query, based on the visitors language and the user segments he or she is a member of.
When ATG Search returns the results from the query, it applies the rules in the search configuration to
those results.
As described in the Structuring the Search Configuration Tree and Administering Search Merchandising
sections, an administrative user creates the folders that make up the search configuration tree. The
merchandiser then creates search configurations to populate these folders. The ATG Merchandising UI
includes a set of five tabs for defining the various settings that make up a search configuration. The
following table lists these tabs and describes the kinds of settings specified in each one:
Tab
Task
General
Specify the name of the search configuration and either the language or
segment value (depending on the tree structure).
Redirection
Define rules for redirecting to other pages rather than displaying search
results.
Property Prioritization
Specify the relative priority of different properties and their values for
determining the ordering of search results.
Result Exclusion
Define rules for excluding certain items from the search results.
Result Positioning
Define rules for moving certain items higher on the list of search results.
The settings are applied in the order listed in the table. So, for example, if product A gets moved to the
top of the search results based on property prioritization, and then product B gets moved to the top
based on result positioning, then product B will end up ahead of product A.
This chapter includes the following sections:
Defining Rules
155
12 - Defining Search Configurations

When you create a search configuration, you have the option of associating it with a base search
configuration. A base search configuration is like a template that provides settings that can be inherited
by standard search configurations. A base search configuration cannot be applied to a search query
directly, but standard search configurations that inherit settings from it can be.
You can create any number of base search configurations, and any number of standard search
configurations can inherit from a single base search configuration. Note, however, than an individual
standard search configuration can inherit from only one base search configuration.
When you define the settings for a standard search configuration that inherits from a base search
configuration, you can decide which inherited settings to enable. See Applying Inherited Rules and
Applying Inherited Prioritization Settings for more information.
Note that the user interface for specifying the rules and property prioritizations for a base search
configuration is virtually identical to the UI for defining standard search configurations. The main
difference is that standard search configurations have options for specifying which inherited settings to
enable or disable. Base search configuration dont have these options, because a base search
configuration cannot inherit from another base search configuration.
Defining Rules
A search configuration has three types of rules: redirection rules, result exclusion rules, and result
positioning rules. These rule types are described in the table at the beginning of this chapter.
Each rule has two main parts, a condition and an action. When the rule is applied, the condition is
evaluated, and if it is true, the action is performed. If the condition is false, the action is not performed.
The following example shows the rule editor for the Result Exclusion tab. In this example, the condition
being evaluated is whether the search query contains the exact phrase fuel injection. If it does, the
action excluding products in the Carburetors category from the search results is performed:
You create and modify a rule by clicking on portions of the rule that are enclosed in gray boxes. When you
click on one of these areas, the editor displays a dropdown menu, a text field, or an asset picker for
specifying that portion of the rule. For example:
156
Products vs. SKUs

Depending on how your site is configured, the results returned by ATG Search can either be products or
SKUs. You can use ATG Merchandising to create rules for either of these configurations. The examples in
this chapter are based on a site that returns products. If your site is instead configured to return SKUs,
youll see a few differences in the ATG Merchandising UI:
The word products is replaced by SKUs in the text of the rules.
The names of properties appear differently in rules. For example, the description
property of a product appears as Description if your site returns products, but
appears as Product -> Description if your site returns SKUs.
Creating a New Rule

When you first create a search configuration, each rule tab includes one empty rule (that is, a rule for
which neither the condition nor the action has been specified). You can create a new rule by editing this
empty rule to specify the condition and action.
A search configuration can include multiples rules of each type. For example, a search configuration
might have 2 redirection rules, 4 result exclusion rules, and 3 result positioning rules.
To create an additional rule for any of these rule types, display the tab associated with the type and click
Add Rule. A new empty rule is added to the tab. For example:
Edit the new rule to specify the condition and action, as described in this chapter.
Specifying the Order of the Rules

Each rule has an Order value that you can modify. These values indicate the order of importance of the
rules, not necessarily the actual order in which the rules are applied.
157
The order in which the rules are applied depends on the type of rule:
Redirection rules are applied in the order of importance. For example, if there are three
redirection rules, ATG Search applies rule 1 first, then rule 2, and then rule 3. This is
because only one redirection can be performed for an individual search query; if you
have several redirection rules and the site visitor enters a search query that matches
the conditions of more than one rule, the first rule that it matches is the one that
actually takes effect.
Result positioning rules are applied in the reverse order of importance. For example, if
there are three result positioning rules, ATG Search applies rule 3 first, then rule 2, and
then rule 1. Since these rules change the ordering of the search results by moving
some items to the top of the list, the later a rule is applied, the stronger its effect.
For result exclusion rules, the order of the rules does not matter. Applying a certain set
of exclusion rules produces the same effect, regardless of the order.
Rules inherited from a base search configuration are always treated as being of lower importance than the
rules defined in a standard search configuration. So inherited redirection rules are applied after locally
defined redirection rules, while inherited result positioning rules are applied before locally defined result
positioning rules.
To change the order of the rules in a tab, enter a new number in the Order field of each rule in the tab,
and click Save. The rules will be redisplayed on the tab in the order you specified. Note, however, that you
cannot change the order of rules inherited from a base search configuration (except by changing them in
the base search configuration itself).
Specifying the Condition

When you create a rule, the condition you specify determines which search queries the rule applies to. For
result exclusion and result positioning rules, you have the option of creating rules that apply to all search
queries. For example, here is a result exclusion rule that applies to all search queries:
To specify a more restrictive condition, click on the first box. A dropdown menu is displayed:
158
Select If the search query. The editor now displays additional fields for specifying the criteria for
determining if a query meets the condition:
Note that the Redirection Rules tab does not have the For all search queries option. A redirection rule
always begins with If the search query.
Now click on contains all of the word(s). A dropdown menu is displayed:
Select an option from this menu, and then enter text in the text field next to it. The following table
describes what each option means and how the text you enter is interpreted:
159
Option
How the text is interpreted
contains all of the word(s)
The text field contains one or more words, separated by

spaces. For the condition to be true, the site visitor must enter
a search query that includes all of these words. The order of the
words in the query does not need to match the order in the
text field, and the query can contain additional words that are
not in the text field.
For example, if the text field contains:
red blue green
The condition is true for this query:

green trees with blue and red leaves
But false for this query:

green trees with red leaves
contains at least one of the

words

a search query that includes one or more of these words. The
query can contain additional words that are not in the text
field.
red blue green

trees with red leaves

purple trees
160
contains this exact phrase

a search query that includes all of these words, in exactly the
order they appear in the text field. The query can contain
additional words not in the field, before or after the words in
the field.
green leaves

trees with green leaves and red branches

green hairy leaves
contains only this exact phrase

a search query that includes all of these words, in exactly the
order they appear in the field. The query cannot contain
additional words not in the field.
green leaves

green leaves

trees with green leaves
matches the query rule pattern
The text is treated as an ATG Search query rule pattern. It can

include special characters (such as wildcards) that are
interpreted by the search engine.
You should use this option only if you are familiar ATG Search
query rules. For information, see the ATG Search Administration
Guide
Specifying Additional Criteria for the Condition

You can define rules that have multiple criteria for evaluating the condition. For example, the criteria
might be:
If the search query contains the exact phrase fuel injection or
contains at least one of the words emissions catalytic
161
In a condition with multiple criteria, the condition is true if any criterion is true. In the example above, a
query containing just the word emissions is true because it meets the second criterion, even though it
doesnt meet the first.
To create a condition with multiple criteria, click on the diamond next to the first criterion, and select or...
from the dropdown menu:
Additional fields are displayed for specifying another criterion:
You can add any number of criteria in this way.
Specifying the Action

Each rule has an action that is performed if the search query satisfies the condition. For a redirection rule,
the action is to display a certain page, which you specify by entering its URL:
You can enter the URL in one of two forms:
Specify the URL relative to the top level of your site. For example:
/products/gifts/diamonds.jsp
Specify the complete URL, including the protocol (http or https). For example:
http://www.mysite.com/products/shoes/index.jsp
162
For a result exclusion rule, the action initially looks like this:
The action for a result positioning rule looks similar:
To specify the action for a result exclusion rule or result positioning rule, click on named. A dropdown
menu is displayed:
Select an option from the menu. Depending on the option you select, different fields will appear for
specifying the products that the action should be applied to. These fields provide tools such as text boxes
or asset pickers for specifying the appropriate values. For example, if you select in category, a blank field
is displayed to the right of the option; clicking on this field displays an asset picker for selecting the
category.
Note that this menu includes not and parenthesis options. These can be useful for specifying complex
logic. For example, if you want to return only items in the category Electrical, you could create a result
exclusion rule with an action like this:
Specifying Additional Criteria for the Action

You can specify multiple criteria for determining which products the action applies to. For example, the
criteria might be:
do not return products in category Carburetors or whose
Stock Availability Status is Out of Stock
This action excludes from the search results all products that are out of stock, as well as all products in the
category Carburetors (assuming, of course, that the query matches the condition).
163
To create an action with multiple criteria, click on the diamond next to the first criterion, and select or... or
and... from the dropdown menu:
Additional fields are displayed for specifying another criterion:
You can add any number of criteria in this way, combined using and or or. It is important to understand
the differences in the resulting logic:
If the criteria are all combined using or, the action is applied to items that meet any of
the criteria.
If the criteria are all combined using and, the action is applied to items that meet all of
the criteria.
It is possible to create very complex expressions for selecting the items to apply the action to. You should
make sure that the rules you create actually encapsulate the logic you want. For example, if there are
three or more criteria, and some are combined using and and others are combined using or, it is a good
idea to use parentheses to ensure that the criteria are interpreted in the way you expect.
Disabling and Deleting Rules

If a search configuration contains a rule that you no longer want to apply to search results, you can delete
it by clicking the red X to the right of the rule. Note, however, that you cannot delete a rule inherited from
a base search configuration (except by deleting it in the base search configuration itself).
In some cases, you may have rules that you want to apply at certain times but not at others (e.g., rules that
apply in spring and fall but not during other seasons). Rather than periodically deleting these rules and
then recreating them later, you can simply disable them at times when you dont want them to be
applied, and enable them when you do. To disable a rule, uncheck the Enable Rule checkbox to the left
of the rule. To enable a rule, check the Enable Rule checkbox.
Applying Inherited Rules

If you associate a search configuration with a base search configuration, then the rules inherited from the
base search configuration are displayed on the corresponding rule tabs of the standard search
configuration. For example:
164
By default, inherited rules are enabled. If you dont want the search configuration to use an inherited rule,
uncheck the Enable Rule checkbox.

You use the Property Prioritization tab to specify the priority of different properties for influencing the
order of search results. The priority of a property takes into account the weighting of the property relative
to other properties, and the ranking of the propertys values relative to each other (e.g., whether high
values are considered better or worse than low values). For example, you might specify that price is
the highest-priority property of products, and that high-priced products should be emphasized. When the
search configuration is applied, higher-priced products will tend to appear higher on the list of search
results than lower-priced products.
As described in Administering Search Merchandising, an administrative user configures the ATG
Merchandising UI to make certain properties available for specifying their priorities. These properties are
displayed in a table on the Property Prioritization tab. For example:
To specify the weighting of a property, use the dropdown menu in the Search Results Weight column.
The menu has values from 1 (the lowest weighting) to 10 (the highest), plus Ignore. The initial setting for
165
each property is Ignore, which means the property is not considered when determining the order of
search results.
Note that the weighting specifies not only the importance of each property, but also a relative
importance. Giving one property a weighting of 5 and another 10 separates them farther in the results list
than if their weightings were 5 and 6 respectively.
After you select a value from a propertys dropdown, text appears in the Property Value Ranking column
describing the criteria for ranking the property values:
The text in this column is a link to a screen where you can specify the criteria for ranking the propertys
values. For properties with a fixed set of possible values (such as SKUs -> On sale and Stock Availability
Status in this example), the software can automatically assigning rankings to the values, though you may
want to click the link to change these, because the default rankings may not be what you want. For
properties whose ranking criteria cannot be determined automatically, the text Rank these values
appears. In this case, you must click the link to specify further ranking information.
Specifying the Ranking of Property Values

The ranking options displayed when you click a Property Value Ranking link depend on the data type of
the property. The following table describes the options:
Data Type
Options
Numeric
You can specify that higher values are better (have higher ranking) or that lower
values are better. If you select one of these options, you must also specify the
minimum and maximum expected values for the property. The other option is to
divide up the data into ranges and then specify a relative ranking for each range.
Date
You can specify that earlier dates are better (have higher ranking) or that later
dates are better. If you select one of these options, you must also specify the
earliest and latest expected dates. The other option is to divide up the dates into
ranges and then specify a relative ranking for each range.
Text
You can specify a set of text values (e.g., red, green, and blue, for a color
property) and a relative ranking for each value.
166
Enumeration
An enumeration is a property with a fixed set of possible values (e.g., a days of the
week property would have 7 possible values). You can specify a relative ranking
for each value.
Boolean
A boolean is a property with whose value is either true or false. You can specify
the relative ranking for the two values.
For every property value type, you have the option of specifying value ranges and number rankings that
order the importance of each range relative to others. Consider the Creation Date property which uses
Date data type. In order to promote new seasonal items, you might create the following ranges:
That way, customers see the newest items created for spring before other items. Notice that the All Other
Values is last in the list, so items created at any date other than one included in the specified ranges will
appear later in the list.
When you are defining ranges, the All Other Values option automatically appears at the top of a list but
can be moved to any position as shown in the previous example. If you want to hide products created in
the winter of 2005-2006, you might move the All Other Values to a middle position, for example:
In these examples, rankings are unique and consecutive although they neednt be. Giving two property
values the same ranking means that for this one criterion, ATG Search sets them as equals. Keep in mind,
however, that a ranking is one of several settings that determines a results place in the results list.
Nonconsecutive rankings work much like nonconsecutive weightings. Consider the following example:
167
In addition to providing a relative order, ranking provides a relative distance that determines how far
apart results appear from others. Products created during November-February 2005 (with a ranking of 12)
will appear significantly lower as much as 3 times lower - in the results list than those created on a date
that doesnt fall into a specified range (with a ranking of 4). A ranking settings exact influence on a search
results position may be difficult to determine because it incorporates a number of factors, such as
property weightings and the order of the result list before search configuration settings are applied.
When you specify rankings, its important to know exactly what effect you are trying to define. For
example, you would create the rankings in the prior example if you want products created in the winter of
2005-2006 to display, but to display after all others. If you dont want such products to display at all, its
best to use a result positioning or exclusion rule to hide them rather than specify a wide range of rankings
here. Giving winter products a ranking of 100, for example, serves to eliminate the distinctions between
the ranges that are ranked closely together (spring products for 2007, 2006, and 2005) rather than deemphasize the winter products.
Copying Prioritization Settings from Another Search Configuration

If you have multiple search configurations that require similar property prioritization settings, you can
copy the settings from an existing search configuration into the one youre editing. To do this, click the
Copy Settings From button on the Property Weighting screen. This displays an asset picker that you can
use to select the search configuration to copy the settings from. All of the weightings and rankings are
copied from the search configuration you select.
When you define the rankings for a propertys values, that screen also has a Copy Settings From button.
This option copies just the rankings for the one property, not the weightings and rankings for all the
properties.
Note that in either case the settings are simply copied; the two search configurations are not associated in
any way. If you subsequently change the settings in one of the search configurations, this has no effect on
the settings in the other one. (This is different from inheriting settings from a base search configuration.
Changing the settings in a base search configuration also changes them in any standard search
configuration that inherits them.)
The Copy Settings From button does not appear on the Property Prioritization tab if the search
configuration is inheriting prioritization settings from a base search configuration. To display the button,
uncheck the Use prioritization settings checkbox on the Property Weighting screen, as discussed in the
next section.
168
Applying Inherited Prioritization Settings

If you associate a search configuration with a base search configuration, by default the search
configuration inherits the property prioritization settings from the base search configuration. The
Property Weighting screen on the Property Prioritization tab displays the inherited settings, but they are
not editable. For example:
If you dont want the search configuration to use inherited prioritization settings, uncheck the Use
prioritization settings checkbox. This clears the inherited settings and enables you to specify new
settings that are local to the search configuration.
Note that a search configuration can inherit either all of the prioritization settings from a base search
configuration or none of them. Unlike rules, inherited prioritization settings cannot be enabled or
disabled individually.
169
170
13 Removing Assets
Assets that are no longer useful on your site may be removed. Its a good idea to make promotions
defunct by deactivating them; all other assets can be deleted.
Refer to the following sections for instructions:
Deleting Assets
Once you have finished an ATG Merchandising task, you signal that it is complete by selecting a task
action. See Advancing from One Task to Another for instructions.

Deleted assets are handled differently depending on the project in which they were created. When you
create an asset and then delete it in the same project, the asset is removed immediately from ATG
Merchandising and the underlying database.
If you delete assets created in previously checked-in projects, those assets display in the Project tab with a
red line through them. Note that such assets appear as deleted only in your project. Users working in
other projects will not see the deletion until your current project is checked in. In your project, however,
the deleted asset wont appear in any tabs except the Project tab, which you can use to restore the asset
to its pre-project state. When you check in a project that includes deleted assets, you remove the asset
from the ATG Merchandising UI and the deployment target database; however, previous versions of the
asset exist in the database and are visible in the ATG Business Control Center. See the Viewing an Assets
History section of the ATG Content Administration Guide for Business Users for information.
When you delete an thats a parent, the rules that govern how the assets children are handled depends
on the types of assets you are working with. You should be familiar with these three circumstances:
171
13 - Removing Assets
First of all, when you want delete assets in your catalog, locate them in the Search tab, or if they are
orphans, in the Catalog Orphans view of the Browse tab. Note that you cannot delete assets from the
Catalog view of the Browse tab.
What happens to child assets when their parent is deleted depends on the types of assets involved:
Deleting a catalog folder containing a child folder moves the child folder to the toplevel of the catalog hierarchy.
In all other circumstances, the child assets are turned into orphans, retaining their
hierarchal relationships to each other.
Consider a situation in which you want to delete the Entertainment Category, which exists in the
following hierarchy in Catalog view:
Entertainment Category
TV Category
HDTVs Product
Generic TV Brand 23" Widescreen SKU
Using the Search tab, you locate the Entertainment Category and delete it. This action turns TV Category
into an orphan and removes the TV Category, HDTVs Product and Generic TV Brand 23 Widescreen SKU
from Catalog view; you need to open Catalog Orphans view to see the TV Category and the assets nested
in it. In that view, you can delete the remaining assets or provide a new parent to TV Category, which
moves all assets back into the catalog and makes them visible again in Catalog view.

When you want to delete a media folder, consider how you want to handle the items it contains. If that
media folder holds media assets, you need to delete the child media assets first, or move them to a
different media folder. Deleting a media folder that contains child folders moves the child folders to the
top-level of the Media view hierarchy.
Consider a structure that includes an Images Folder containing a navigation bar image as well as a media
folder called Logos Folder that holds other images and media folders:
Images Folder
Nav.jpg
Logos Folder
logoSmall.jpg
logoLarge.jpg
Old Logos Folder
To delete the Images Folder and Nav.jpg, you should first delete Nav.jpg, then the Images Folder. Once
you delete the folder, the Logos Folder will be moved to the top level hierarchy, retaining the hierarchy of
images and media folders inside it.
172

Price lists are organized in an inheritance structure in which the prices in one list, called a base list, are
available to lists that descend from it. Because the inheritance structure can be several levels deep,
deleting one price list has consequences for others related to it. Consider the following price list hierarchy:
United States
East Coast
New England
Prices defined in the United States list are inherited by the East Coast list. Some prices in East Coast list
may be modified, so the prices inherited by the East Coast list are different from those in the United States
list. The same may also be true for the New England list. For example:
Price List
Suppell Helmet
Suppell Hybrid 1071 Bike
Fast Racer
Shoes
United States
$89.99
$3679.00
$73.99
East Coast
$89.99*
$3850.00
$83.99
New England
$89.99*
$3850.00*
$85.99
* = Inherited price
If you delete the East Coast price list, New Englands new base list automatically becomes the United
States list. Where the New England list uses an inherited price, as is the case with the Hybrid 1071 Bike, the
United States price is now used. If you delete the East Coast list, the other lists appear as follows:
Price List
Suppell Helmet
Fast Racer
Shoes
United States
$89.99
$3679.00
$73.99
New England
$89.99*
$3679.00*
(formerly $3850.00)
$85.99
* = Inherited price
If, instead, you delete the United States list, prices inherited from that list by others are eliminated. In this
case, all prices in the United States and East Coast lists that are entered in those lists remain the same; the
only price that changes is the Suppell Helmet price, which is now empty. The East Coast and New England
lists appear as follows:
173
Suppell Helmet
Fast Racer
Shoes
East Coast Price List
Null
(formerly $89.99)
$3850.00
$83.99
New England Price List
Null
(formerly $89.99)
$3850.00*
$85.99
Because lists depend on other lists for prices, its important to note how deleting one list alters others, and
avoid deleting base price lists whenever possible. Keep mind that a price list is used only when it is
assigned to a user segment, so theres no harm in letting unassigned price list remain.

ATG Merchandising permits you to delete search configurations, base search configurations, and search
configuration folders at all times. There are two behaviors to keep in mind:
Deleting a base search configuration thats associated with a search configuration

causes the standard configuration to lose any settings it inherited from the base
configuration.
Deleting a search configuration folder deletes any search configurations it contains.
For information on removing a segment from the merchandising segment list and removing properties
from the Property Prioritization tab, see Administering Search Merchandising.

Deleting a facet also deletes the facets nested in it. If you want to delete the parent facet only, move all
nested facets to another part of the hierarchy before deleting the parent.
Deleting Assets
Delete assets when you are certain you wont use them in the future and deleting them wont produce
difficulties in your application.
Note on Deleting Promotions: Because promotions are attached to other Repository items, such as
profiles, other promotions, and coupons, deleting a promotion could cause your Web site to process an
order in a way you dont expect. You cant delete promotions, but you can disable them. See Deactivating
Promotions for instructions.
To delete assets:
1.
Locate the assets you want to delete using the Search tab, or Catalog Orphans view,
Media view, Price Lists views, Coupons view, or Promotions view of the Browse tab.
See Locating Assets for instructions.
174
2.
Click the checkbox beside each asset you want to delete.
3.
Click Delete.
4.
When prompted for confirmation, click OK.
The best way to deactivate a promotion is to set the Enabled property to false. Disabled promotions
arent distributed to visitors or usable even when the Usage start and Usage end date properties may
indicate otherwise. If you find that you need to cancel a promotion immediately, you should disable it.
175
176
14 Customizing the ATG Merchandising

User Interface
This chapter covers customization procedures specific to ATG Merchandising:

Creating Workflows
Customizing Views
For a complete set of the UI customizations available to applications that use the Asset Manager
framework, refer to the Configuring the Asset Manager chapter of the ATG Business Control Center
Administration and Development Guide.
Creating Workflows
ATG Merchandising comes with one workflow, Manage Commerce Assets, that can refer to one of several
deployment workflows. These workflows are described in the Configuring Workflows section. If you find
the ATG Merchandising workflows are insufficient for your business needs, modify them or create custom
workflows. To learn how to work with workflows, refer to the following resources:
For general information about workflows, see the Creating and Configuring Workflows
chapter of the ATG Personalization Programming Guide.
Also, for information about configuring workflows in a Content Administration

environment, see the Setting Up Workflows and Guidelines for Customizing Project
Workflows sections of the Adapting Workflows to Content Management Projects chapter
When you create a workflow in the ATG Control Center, it automatically displays in the ATG Business
Control Center under Merchandising in the Operations list as long as you save the workflow in the
/atg/registry/data/epubworkflows/Commerce directory. If youd prefer to keep the workflow in a
different directory, you need to update the /atg/commerce/web/CommerceActivitySource
component workflowDirectories property to with the new directory name and path.
177
14 - Customizing the ATG Merchandising User Interface
Customizing Views
ATG Merchandising comes with seven views - Catalog, Catalog Orphans, Media, Price Lists, Price Lists and
Folders, Coupons, and Promotions that you can modify as needed. The way you modify views depends
on whether they display assets in a tree, as the Catalog, Catalog Orphans, Price Lists, and Media views do,
or in a list as the Promotions and Coupons views do. Refer to the following sections for information:
If you want to customize the views in the Search tab to, for example, accommodate a different set of asset
types, see Creating and Defining a Task Configuration File section of the Tailoring the UI for Specific
Workflows, Tasks, and Activities chapter in the ATG Business Control Center Administration and Development
Guide for instructions.
Note: Customers who have ATG Search and ATG Merchandising have an additional view Facets which
is not customizable.

You can modify tree views by:
Changing the Types of Assets You Can Create in a View
Changing the Types of Assets Visible in a Tree View
Changing Bucket Size
Changing the label used for the view in the Browse tab Show dropdown list as
described in Working with Resource Bundles.
For instructions on creating views, see Creating Views section of the Configuring the Asset Manager chapter
of the ATG Business Control Center Administration and Development Guide.
Changing the Types of Assets You Can Create in a View

The types of assets available in the dropdown list displayed when you click the Create New button are
tailored for each view. You can add or remove types from this list by modifying the
createableTypesList property in the appropriate component of
atg.web.assetmanager.configuration.BrowseTreeViewConfiguration class:
Catalog view:
/atg/commerce/web/assetmanager/CatalogBrowseTabConfiguration
Catalog Orphans view:

/atg/commerce/web/assetmanager/OrphanBrowseTabConfiguration
Media view:
/atg/commerce/web/assetmanager/MediaBrowseTabConfiguration
Learn more about the BrowseTreeViewConfiguration class and its properties in the Creating Views
section in the Configuring the Asset Manager chapter of the ATG Business Control Center Administration and
Development Guide.
178
Changing the Types of Assets Visible in a Tree View

Another way to modify an existing tree view is by adding new asset types to or removing existing asset
types from a tree in a view. Modify the treeLinks and rootNodeRQL properties in the appropriate view
component located in the /atg/commerce/web/browse directory:
Catalog view for standard catalogs: StandardCatalogTreeDefinition
Catalog view for custom catalogs: CustomCatalogTreeDefinition
Catalog Orphans view for standard catalogs:

StandardCatalogOrphanTreeDefinition
Catalog Orphans view for custom catalogs: CustomCatalogOrphanTreeDefinition
Media view: MediaTreeDefinition
For instructions, see the Customizing the Asset Picker section in the Configuring the Asset Manager chapter
Changing Bucket Size

A bucket is a folder thats automatically generated when you view a tree that contains a large number of
assets. Adjust the number of assets held in a bucket by modifying the bucketSize and bucketRatio
properties of /atg/web/tree/CountBasedBucketer, which is the component that defines buckets for
all trees. If you want each tree to handle bucketing differently, create new Count Based Bucketer
components. For more information on this component and its properties, see the Configuring the Asset
Manager chapter of the ATG Business Control Center Administration and Development Guide for instructions.

You can modify a list view by:
Changing the types of assets you can create in the view, the specific assets visible in a
view, the ordering of assets in the view, and the number of assets visible on a page, as
described in the Changing Navigation Pane Settings section below.
Changing the label used for the view in the Browse tab Show dropdown list as
described in Working with Resource Bundles.
Notice that, even though you can change the types of assets a view lets you create, you cant change the
types of assets that are visible in a view. Each list view displays one type of assets and its subtypes. If you
want a view to display a different type of asset, create a new view as described in Creating Views section of
the Configuring the Asset Manager chapter in the ATG Business Control Center Administration and
Development Guide.
Changing Navigation Pane Settings

Each view has a component of class
atg.web.assetmanager.configuration.FilterableBrowseListViewConfiguration that
governs how the Navigation pane displays assets for that view. The Promotions view, for example, uses
the /atg/commerce/web/assetmanager/PromotionsBrowseTabConfiguration component for that
purpose. Adjust the following properties on this component as needed:
179
Change the types of assets you can create in a view by adding or removing the values
in the createableTypesList property.
Limit the assets visible in the Navigation pane to a subset of the selected type by
modifying the value of the queryRQL property.
Change the number of assets that appear on a page by updating the itemsPerPage
property value.
You can find more information about the FilterableBrowseListViewConfiguration class and its
properties in the Creating Views section in the Configuring the Asset Manager chapter of the ATG Business
Control Center Administration and Development Guide.

Resource bundles hold labels for views, buttons, tabs and other UI elements, so you can localize your
application. Most labels that you see in ATG Merchandising are defined in the following resource bundle:
<ATG2007.1dir>/DCS-UI2007.1/DCS-UI/management/lib/classes.jar/atg/commerce/
web/WebAppResources.properties. For example, the names of the views visible in the Browse tab are
specified there. Other resource bundles hold labels for elements, such as the Browse tab, that are
common to all Asset Manager applications. For information on other resource bundles or instructions for
adding or creating labels, see the Changing UI Labels section of the Configuring the Asset Manager chapter

Like other Asset Manager applications, you can adapt ATG Merchandising so that the UI is tailored to the
actions you aim to perform in it. For example, activities let you browse ATG Merchandising, but do not
permit you to edit commerce assets. To ensure that users cant perform prohibited actions, the UI hides
certain buttons and tabs from users who enter ATG Merchandising through the Browse activity.
When you customize the UI for tasks or activities, you define tags in a task configuration file. ATG
Merchandising comes with one such file, but others are included with the Personalization module. To
learn about the Personalization files as well as basic information about the process for customizing the UI
in this way, see the Tailoring the UI for Specific Workflows, Tasks, and Activities chapter of the ATG Business
Control Center Administration and Development Guide.
Note: Another task configuration file is provided to display Search Merchandising and Faceted Search
and Navigation UI elements to users who also have ATG Search. Altering the parts of the UI for those
features is not recommended.
One activity (Browse) and one workflow (Manage Commerce Assets) are included with ATG
Merchandising. Since there are no specific UI configuration settings defined for them in the task
configuration file, they use the settings for the default activity and default task, respectively, verbatim.
180
Merchandising-Specific Task Configuration Manager

ATG Merchandising defines a Task Configuration Manager that it uses to process the out-of-the-box task
configuration file and any custom files you intend to work with Merchandising resources. Using a Task
Configuration Manager different from the one used by the Personalization module keeps the
Merchandising files separate from the Personalization ones: none of the configurations from the
Personalization files are inherited by the Merchandising file. This approach simplifies maintenance, by
keeping Merchandising modular and autonomous.
The Task Configuration Manager is implemented by the Activity Manager. You provide settings to the
Task Configuration Manager in the task configuration file using the <configuration> tag. Using a Task
Configuration Manager different from the ones that come out-of-the-box is not currently supported.
For information on how the task configuration file is processed and the tags are parsed, see How the UI is
Configured section in the Tailoring the UI for Specific Workflows, Tasks and Activities chapter of the ATG
The Merchandising Task Configuration File

Its a good idea to familiarize yourself with the default configuration settings in this file, so you can learn
where settings are specified, which may affect how you modify them in your custom task configuration
file. Keep in mind that the tags and attributes used in the this file are a subset of those available to you.
You can find taskConfiguration.xml in the <ATG2007.1dir>/DCS-UI2007.1/DCS-UI/
management/config/config.jar/atg/commerce/web/assetmanager directory.
Open the file so you see it in its entirety. The file is enclosed in a <task-configuration> tag. Inside it,
the file is divided roughly into two sections: one enclosed in a <default-activity> tag and the other
enclosed in a <default-task> tag.
The <default-activity> tag encloses settings that apply by default to all activities. An activity can
involve an ATG Merchandising operation, such as browsing or searching for assets, that doesnt produce
or affect versioned assets. When you click the Browse activity link from the ATG Business Control Center
Operations list, you see a version of the ATG Merchandising UI that is determined by the code enclosed in
the <default-activity> tag.
In addition to specifying the settings for the default activity, the <default-activity> tag encloses
settings that apply to all ATG Merchandising workflows and tasks, unless they are explicitly overridden
elsewhere in the file. You can think about these tags as setting the foundation for all displays in ATG
Merchandising. Before you customize the ATG Merchandising UI, check the default settings provided
here.
The <default-task> tag defines the appearance of ATG Merchandising accessed through a task as it
differs from the appearance of ATG Merchandising accessed through an activity. The <default-task>
settings take effect when a user enters ATG Merchandising using a task for a project based on a workflow,
such as the Author task of the Manage Commerce Assets workflow.
Enclosed in the <default-task> tag, there are other tags that add buttons, add a tab and view, remove
buttons, and change the view mapping settings. The structure of the task configuration file is derived
from the DTD that specifies the tags each tag can contain. Within that structure, a grouping of tags can
exist anywhere in its parent tag the DTD permits. For example, the <operations> tag grouping is
181
currently the first grouping beneath the <default-task> tag, but moving it to another place in the
<default-task> tag would have no bearing on tag inheritance.
Some of the many configuration values specified in the default task configuration file are JSPs used by
various parts of the UI. All JSPs are located in the DCS-UI-Management.war file that you find in
<ATG2007.1dir>/DCS-UI2007.1/DCS-UI/management/j2ee-apps/DCS-UI-Management.ear. All
other file locations are specified below.
Default Activity Settings

As mentioned earlier, the default activity tag defines the appearance of ATG Merchandising for the out-ofthe-box activity and specifies general settings that serve as defaults to all tasks and workflows. When
settings are inappropriate for a given workflow, for example, they should be disallowed in the task
configuration defined for that workflow.
As you scan through the default activity settings, you may notice that there are no buttons defined here.
Since activities are for browsing assets and not editing them, buttons are not added here. You can see
buttons represented in the default task section.
Defining General Activity Settings
The default activity section of the file begins as follows:
<default-activity>
<resource-bundle>
atg.web.assetmanager.WebAppResources
</resource-bundle>
<page>
/assetManager.jsp
</page>
<asset-editor>
<page>
/assetEditor/editAsset.jsp
</page>
</asset-editor>
The main resource bundle for ATG Merchandising is called atg.web.assetmanager.WebAppResources,

and you can find the properties file for it in <ATG2007.1dir>/AssetUI/lib/classes.jar. The next
tags specify the page that provides the structure to the ATG Merchandising UI called assetManager.jsp.
Among other specifications, assetManager.jsp shapes the UI into a two-paned structure. The structure
for the Details pane is provided in editAsset.jsp.
Defining General Tab Settings
This section describes the general tab settings provided by the following tags:
<tabs>
<tab-order>
182
<tab-id>browse</tab-id>
<tab-id>search</tab-id>
</tab-order>
<initial-tab>
browse
</initial-tab>
The <tabs> tags correspond to the first organizational screen elements in the Navigation pane which are
defined in assetManager.jsp. The first such element is defined as a tab. The second is a dropdown list
defined by view tags.
This code specifies two standard tabs, Browse and Search, which will display in this order. When you enter
ATG Merchandising, the Browse tab always displays open because it is specified as the initial tab.
Defining the Browse Tab and its Views
This section describes the Browse tab:
<tab id="browse">
<display-name-resource>
assetManager.tab.browse
</display-name-resource>
<page>
/browse/browseTab.jsp
</page>
The Browse tab name is specified to the assetManager.tab.browse key in the global resource bundle
named in the <resource bundle> tag described above. The browseTab.jsp file provides the tab
content.
The views on the Browse tab are configured as follows:
<views>
<view-order>
<view-id>catalogTree</view-id>
<view-id>catalogMedia</view-id>
<view-id>catalogOrphans</view-id>
<view-id>promotions</view-id>
<view-id if="usingPricelists">priceLists</view-id>
<view-id if="usingPricelists">pricelistFolders</view-id>
<view-id>coupons</view-id>
</view-order>
<initial-view>
catalogTree
</initial-view>
<view id="catalogTree">
<resource-bundle>
183
atg.commerce.web.WebAppResources
<resource-bundle>
browseTab.view.catalog
<configuration>
/atg/commerce/web/assetmanager/CatalogBrowseTabConfiguration
</configuration>
<page>
/browse/tree.jsp
</page>
</view>
There are seven views defined for the Browse tab:
View Name
Default View Name in the UI
catalogTree
Catalog
catalogMedia
Media
catalogOrphans
Catalog Orphans
promotions
Promotions
priceLists
Price Lists
priceListFolders
Price Lists and Folders
coupons
Coupons
The views display in a dropdown list in the order specified here, and when you open ATG Merchandising,
the catalogTree view displays in the Browse tab because it is specified as the initial view.
View labels are held in a resource bundle different from the default, so, in addition to providing the key
that maps to the view name, the resource bundle name itself is specified for each view. The name
provided to a view is visible in the dropdown list you use to access it. Each view also has a configuration
component that defines settings that are common to all uses of that view. There are many configuration
options for the Browse tab views so storing them in a Nucleus component simplifies and reduces clutter
in taskConfiguration.xml. You can access the Nucleus component in the ACC using the path provided
in the task configuration file. See the Creating Views section of the Configuring the Asset Manager chapter
of the ATG Business Control Center Administration and Development Guide for more information about this
component.
Note that, in the list of views, the price list views include an if attribute. This attribute specifies that the
display of price list views is controlled by the value in the usingPricelists property of the
atg/commerce/web/Configuration component specified at the start of the file. This convention is not
supported in custom task configuration files.
184
Because the same kind of information is provided for all views, catalogTree is provided here as an
example that represents the others.
Defining the Search Tab
The Search tab general settings are defined as follows:
<tab id="search">
assetManager.tab.search
<page>
/search/searchTab.jsp
</page>
<views>
<initial-view>
form
</initial-view>
The Search tab definition begins with the key mapped to the tab name identified in the resource bundle.
Note that a resource bundle isnt specified here because the default, defined earlier in the file, is used. The
content displayed in the Search tab is contained in searchTab.jsp. Note that although the Search tab
has views, they arent displayed in an ordered list because they arent available for user selection. The
searchTab.jsp file is designed to display one view (form) for entering search criteria and another for
search results (results described below). The view that displays when the Search tab is first accessed is
form.
<view id="form">
<page>
/search/searchForm.jsp
</page>
<item-types>
<item-type>/atg/commerce/catalog/ProductCatalog:sku</item-type>
<item-type>/atg/commerce/catalog/ProductCatalog:configurableSku</item-type>
<item-type>/atg/commerce/catalog/ProductCatalog:product</item-type>
<item-type>/atg/commerce/catalog/ProductCatalog:category</item-type>
<item-type>/atg/commerce/catalog/ProductCatalog:catalog</item-type>
<item-type>/atg/commerce/catalog/ProductCatalog:folder</item-type>
<item-type>/atg/commerce/catalog/ProductCatalog:promotion</item-type>
<item-type>/atg/commerce/catalog/ProductCatalog:Item Discount</item-type>
<item-type>/atg/commerce/catalog/ProductCatalog:Shipping Discount</item-type>
<item-type>/atg/commerce/catalog/ProductCatalog:Order Discount</item-type>
<item-type>/atg/commerce/catalog/ProductCatalog:media</item-type>
<item-type>/atg/commerce/catalog/ProductCatalog:media-external</item-type>
<item-type>/atg/commerce/catalog/ProductCatalog:media-internal-binary
</item-type>
<item-type>/atg/commerce/catalog/ProductCatalog:media-internal-text
185
</item-type>
<item-type if="usingPriceLists">/atg/commerce/pricing/priceLists/
SecurePriceLists:priceList</item-type>
<item-type if="usingPriceLists">/atg/commerce/pricing/priceLists/
SecurePriceLists:priceListFolder</item-type>
/atg/commerce/claimable/ClaimableRepository:DeployablePromotionClaimable
</item-type>
</item-types>
</view>
<view id="results">
<page>
/search/searchResults.jsp
</page>
</view>
The first view, form, uses searchForm.jsp as the page in which you build a search query. In the Search
tab, theres a dropdown list that contains asset types, one of which you are required to select when you
want to perform a search. You make asset types available to the list by including them in between <itemtype> tags. The actual name that appears in the list is the display name defined for the asset type in the
assets repository item descriptor. The asset types in the list include a subset of the asset types defined for
ATG Merchandising. For a complete view of available asset types, see the item descriptors used by your
product catalog. For example, you can find the Business Commerce item descriptors in
<ATG2007.1dir>\B2Bcommerce\config\atg\commerce\catalog\productcatalog.xml.
The second view uses searchResults.jsp to display the assets that result from the query.
You may notice the Find, Add Criteria, and New Search buttons arent defined in the task configuration
file. Because it seems unlikely that youd want to remove or replace these buttons, they are hardcoded
into the search JSPs.
Defining View Mappings
The view mapping settings define the asset properties that are visible and editable in the Details pane for
a given context. The following configurations are specified for the default activity:
<view-mappings>
<view-mapping mode="AssetManager.edit">
<item-mapping>
<item-type>*</item-type>
<item-mapping-name>AssetManager</item-mapping-name>
<view-mapping-mode-override>AssetManager.view</view-mapping-mode-override>
</item-mapping>
</view-mapping>
<view-mapping mode="AssetManager.multiEdit">
<item-mapping>
</item-mapping>
186
</view-mapping>
<view-mapping mode="AssetManager.view">
<item-mapping>
</item-mapping>
</view-mapping>
<view-mapping mode="AssetManager.create">
<item-mapping>
</item-mapping>
</view-mapping>
<view-mapping mode="AssetManager.diff">
<item-mapping>
</item-mapping>
</view-mapping>
<view-mapping mode="AssetManager.conflict">
<item-mapping>
</item-mapping>
</view-mapping>
</view-mappings>
</default-activity>
A JSP passes a map mode to the task configuration file: this code determines whether the same mode
passed in is returned to the JSP. Because this resource is an activity and no assets should be editable, an
input of AssetManager.edit map mode has an output mode of AssetManager.view. The
AssetManager.conflict, AssetManager.create and AssetManager.diff map modes are passed
only when asset editing complications occur, so they dont apply for activities. Because these activity
settings are inherited by other resources, the AssetManager.conflict and AssetManager.diff map
modes are specified here and are to remain unchanged when returned to a JSP.
Note the use of * as a value indicates the inclusion of all items, such as all asset types, as is the case here.
Using an * in the context of the view mapping name in the view mapping repository has a different
meaning than it does in the task configuration file.
Default Task Settings

The default task tags define UI settings that are applied, in combination with those defined for the default
activity, to all tasks in all workflows unless they are overridden by other explicit configurations. Notice that
the buttons added here apply to all tabs and views, including those defined in the <default-activity>
tags. If a button isnt necessary for a tab or view, the button is removed in the section for the tab or view.
187
If there were conflicting values among settings defined in the default task and the default activity (there
are none in this file), the default task settings would be used for tasks. These settings are specified for the
tasks in the default workflow but are inherited by all tasks and workflows.
Defining Common Buttons and General Tab Settings
The buttons that are common for all tabs are implemented here:
<default-task>
<operations>
<operation>create</operation>
<operation>duplicate</operation>
<operation>delete</operation>
<operation>move</operation>
<operation>link</operation>
<operation>unlink</operation>
<operation>addToProject</operation>
<operation>addToMultiEdit</operation>
</operations>
The operation tags define the buttons available to projects. Unlike other screen elements, the placement
and ordering of the <operations> tag is defined in the JSP. The buttons named here are subset of the
list of buttons available in ATG Merchandising, which are described in the Types of Assets and Buttons
section.
Two additional tabs are visible for the default task:
<tabs>
<tab-order>
<tab-id>project</tab-id>
<tab-id>multiEdit</tab-id>
</tab-order>
Because the Project tab displays assets used in the current project, it is useful for users who are
performing tasks in projects, not those who access ATG Merchandising through activities. So, the Project
tab is defined as part of the default task. Similarly, the Multi Edit tab is inapplicable unless you are editing
assets, so its excluded from the default activity, by being specified in the default task.
According to this setting, the Project tab displays third and Multi Edit displays fourth because this list is
added to the end of the list of tabs defined in the default activity. To specify a different tab order, all tabs
would have needed to be listed in that order here.
Modifying the Browse Tab Settings
The settings for the Browse tab are modified as follows:
188
<tab id="browse">
<views>
<view id="catalogTree">
<operations>
<operation combine="remove">delete</operation>
</operations>
</view>
<view id="promotions">
<operations>
<operation combine="remove">delete</operation>
</operations>
</view>
<view id="priceLists" if="usingPriceLists">
<operations>
<operation combine="remove">link</operation>
</operations>
</view>
<view id="coupon">
<operations>
<operation combine="remove">duplicate</operation>
</operations>
</view>
<view id="catalogMedia">
<operations>
<operation combine="remove">link</operation>
</operations>
</view>
</views>
</tab>
The default activity tag specifies a resource bundle key and JSP for the Browse tab as well as three views
that each have a position in the dropdown list, resource bundle key, and configuration component. The
default task tag adds buttons to all tabs, but tags included here remove one of those buttons Delete
from the Catalog and Promotions views. Because deleting assets involved in orders may cause
unexpected results, the Delete button is made less available to users. Likewise, the Link button is removed
from Media and Price Lists view because price lists and media items are always unique items, so theres no
purpose in creating links of them. Note the syntax used for removing a button.
The Duplicate button is removed from Coupons view because coupons require few pieces of identifying
information, most of which is unique to a given coupon. It is more sensible to create coupons from
scratch rather than duplicate them.
Defining the Project Tab
The Project tab is defined as follows:
<tab id="project">
189
assetManager.tab.project
<page>
/project/projectTab.jsp
</page>
<operations>
<operation combine="remove">addToProject</operation>
<operation>removeFromProject</operation>
</operations>
</tab>
The name for the Project tab is mapped, in the resource bundle named earlier, to the key
assetManager.tab.project. The content for the Project tab is provided by projectTab.jsp, and
there are two changes to the list of buttons made available to it. The Add To Project button that was
added as one of the eight provided to all tabs and views is removed here because it is inapplicable: you
wouldnt add assets already on the Project tab to it. The Remove From Project button is added instead. In
order for buttons to be visible in ATG Merchandising, they must be permitted by the task configuration
file and implemented in a given JSP. Some buttons Move, Link, Unlink, Create, Duplicate, Delete are
permitted in the Project tab by the task configuration file, but are not visible there because
projectTab.jsp does not support them. A configuration component holds additional settings: see
Creating Views section of the Configuring the Asset Manager chapter of the ATG Business Control Center
Administration and Development Guide for more information about this component.
Defining the Multi Edit Tab
The Multi Edit tab is defined as follows:
<tab id="multiEdit">
assetManager.tab.multiEdit
<page>
/multiEdit/multiEditTab.jsp
</page>
<operations>
<operation combine="remove">addToMultiEdit</operation>
<operation>removeFromMultiEdit</operation>
<operation>stepEdit</operation>
<operation>applyToAll</operation>
<operation>listEdit</operation>
</operations>
<configuration>
/atg/commerce/web/assetmanager/configuration/MultiEditTabConfiguration
</configuration>
</tab>
</tabs>
190
Similar to the Project tab definition, the Multi Edit tab stores its tab name in a resource file, mapping the
string provided here to the tab name. The tab structure is defined in multiEditTab.jsp. The Multi Edit
button is extraneous in the Multi Edit tab so it is removed. Multi Edit-specific buttons are added to the tab:
Remove from Multi Edit, Step Edit, List Edit, Apply to All. A configuration component holds additional
settings that you shouldnt need to modify under any circumstances: see the Creating Views section of the
Configuring the Asset Manager chapter of the ATG Business Control Center Administration and Development
Guide for more information about this component.
Modifying the View Mapping Settings
In order to determine the asset properties to display, the JSP specifies a view mapping mode based on the
whether a project (AssetManager.edit) or an activity (AssetManager.view) is present. The view
mapping settings are modified as follows:
<view-mappings>
<view-mapping mode="AssetManager.edit" combine="replace">
<item-mapping>
</item-mapping>
</view-mapping>
<view-mapping mode="AssetManager.multiEdit" combine="replace">
<item-mapping>
</item-mapping>
</view-mapping>
</view-mappings>
</default-task>
The view mapping settings provided for the default activity are used except when the JSP recommends
AssetManage.edit mode or AssetManager.multiEdit, in which case the input mode is also the
output mode. Replacing these tags with editable map modes permits users to who access ATG
Merchandising through a project to edit assets one at a time or in bulk.
191
192
The following tables list all properties available to catalog folders, catalogs, categories, products, SKUs,
configurable SKUs, SKU links, configurable properties, and configurable options out of the box. Media
assets and folder are also covered here. Note that the only major asset types excluded from this appendix
are promotions and price lists, which are described in Defining Promotions and Using and Defining Price
Lists respectively.
The properties you see in ATG Merchandising depend on three factors:
the type of catalogs you use: standard or custom,
the type of commerce product you have installed: Consumer Commerce or Business
Commerce, and
the way your administrator has configured your product. An administrator can define
additional properties or hide properties from the UI.
This appendix includes several tables, each of which lists property names and descriptions provided by a
feature or product. In the descriptions, the phrase selected asset refers to the asset that the set of
properties comprise. One way to see the properties for an asset is to click its name in the Navigation pane.
Refer to the following sections to learn about asset properties:
Base Properties
Base Properties
The following table describes the properties provided out-of-the-box by ATG Merchandising to all users,
regardless of type of catalog or commerce product you use:
193
Property and Location
Description
Auxiliary Media
Lists auxiliary media as a mapping between a

media asset and a label that identifies its
purpose, such as sale image. Use the buttons
beside this property to:
In the Media tab for Categories, Products, SKUs,

and Configurable SKUs
- Associate an auxiliary media asset to the

selected asset by clicking Select to open the
Select an Item dialog box. Navigate to the
auxiliary media asset, click the radio button
beside it, and then click OK. Provide the catalog
ID in the Key column.
- Create a new media asset that will display as
auxiliary media for the selected asset by
clicking Add New, selecting a media type from
the Select Asset Sub-Type dropdown list,
entering a label for media assets usage in the
Key text box, and clicking Next. The Details
pane displays with empty media properties
that you should fill in as described in Creating
Media Assets and Folders.
- Disassociate an auxiliary media asset from the
selected asset by clicking the Delete button
beside the media asset.
194
Bundle Links
In the Basics tab for SKUs and Configurable SKUs
Lists the SKUs links that are part of a SKU

bundle. A SKU bundle is a virtual SKU that is
composed of several other SKUs. Bundles allow
the product catalog to offer a SKU that can be
purchased as a single item, although it is
treated as multiple items in fulfillment. Use the
buttons beside this property to:
- Replace one SKU link with another by locating
the SKU in the table and clicking the Edit
button beside it in order to open the Select an
Item dialog box. Navigate to the SKU
replacement, click the radio button beside it,
and then click OK.
- Rearrange the position of a SKU link in a
bundle by changing the number beside it. To
preview the new order, click Reorder.
- Remove a SKU link from the bundle by
clicking the Delete button beside the SKU link.
- Add an existing SKU link to the bundle by
clicking Add Existing to open the Select an
Item Dialog box. Locate all SKUs by clicking
Find. Navigate to the SKU you want to add,
click the radio button beside it, and then click
OK.
- Create a SKU link that will be a link in a bundle
by clicking Add New. The Details pane displays
with empty SKU properties that you should fill
in as described in Creating SKUs and
Configurable SKUs.
Child Categories (group)
In the Basics tab for categories
Holds the content group comprised of

categories listed in the Dynamic Child Category
property. Use the buttons beside this property
to:
- Add or replace a content group by clicking
the Edit button to open the Select an Item
dialog box. Search for the content group, click
- Remove a content group by clicking the
Delete button.
195
Child Products (group)
In the Products tab for categories

categories listed in the Dynamic Child Products
to:
Delete button.
Configurable Properties
In the Basics tab for Configurable SKUs
Lists the names used to characterize a group of

subSKUs. Use the buttons beside this property
to:
- Replace one configurable SKU property with
another by locating the property in the table
and clicking the Edit button beside it in order
to open the Select an Item dialog box. Navigate
to the replacement, click the radio button
- Rearrange the position of a configurable SKU
property in the list by changing the number
beside it. To preview the new order, click
Reorder.
- Remove a configurable SKU property from the
list by clicking the Delete button beside the
configurable SKU.
- Add an existing configurable SKU property to
the list by clicking Add Existing to open the
Select an Item dialog box. Locate all
configurable SKU properties by clicking Find.
Navigate to the configurable SKU property ,
OK.
- Create a configurable SKU property that will
be added to the configurable properties list for
the selected configurable by clicking Add New.
The Details pane displays with empty SKU
properties that you should fill in as described in
Creating SKUs and Configurable SKUs.
196
Configurable Options
In the Basics tab for Configurable Properties
Holds the individual items that can be linked to

existing SKUs. Use the buttons beside this
property to:
- Replace one configurable option with another
by clicking the Edit button beside the option
you want to replace, which opens the Select an
Item dialog box. Locate all configurable
options by clicking Find. Locate the
replacement configurable option, click the
radio button beside it, and click OK.
- Rearrange the position of a configurable
option in the list by changing the number
Reorder.
- Remove a configurable option from the list by
clicking the Delete button beside the
configurable property.
- Add a configurable option to the list by
Item dialog box. Locate all configurable
options by clicking Find. Locate the
replacement configurable option, click the
radio button beside it, and click OK.
- Create a configurable option that will be
added to the list by clicking Add New. The
Details pane holds properties that you fill in to
define the configurable option. See Creating
Configuration Options for instructions.
Data
In the Basics tab for Media-Internal-Binary Assets
Data
In the Basics tab for Media-Internal-Text Assets
Holds the uploaded file represented by the

Media-internal-binary asset. To upload a file,
enter the file name and path manually, or click
the Browse button to open the Select Item
dialog box. Navigate to the binary file, select it,
then click Open.
Holds the text you want to associate with the
media asset.
197
Default Parent
Category
In the Basics tab for Categories and Products
Holds the name of the asset that contains the

selected asset. If a parent isnt specified, the
asset is an orphan, visible from Catalog
Orphans view, not Catalog view. Use the
- Add or replace an existing parent, by clicking
dialog box. Navigate to the asset, click the radio
- Remove an existing parent, click the Clear
button.
- Create a category that will be a parent to the
selected category, by clicking Create. The
Details pane displays with empty category
Creating Categories.
Description
Holds a description for the selected asset.
In the Basics tab for Media Assets, Media Folders,

Catalog Folders, Categories, Products, SKUs,
Configurable SKUs, SKU Links, Configurable
Properties, and Configurable Options
Displayable SKU Attributes
In the Basics tab for products
Holds the names of the SKU properties that you

can make visible on your Web site. Use the
- Rearrange the position of an attribute in the
list by changing the number beside it. To
- Remove an attribute by clicking the Delete
button beside it.
-Add a new attribute by clicking Add Existing,
which adds a row in the table. Enter the new
attribute in the row.
Dynamic Attributes
Lists properties created on the fly for a given

SKU. Use buttons beside this property to:
- Add a dynamic attribute by clicking Add. In
the Key text box, enter a property name, and in
the Value text box, enter a value for the
property.
- Remove a dynamic attribute by the Delete
button beside it.
198
End Date
In the Basics tab for Media Folders, Categories,

Products, SKUs, Configurable SKUs, and SKU Links
Fulfiller

Item
In the Basics tab for SKU Links
Holds an end date and time. This property is

used in conjunction with the Start Date
property to provide the date range during
which the selected asset is active on the Web
site. In order for these dates to be used, you
need to implement the StartAndEndDate
collection filter.
Holds the fulfillment component used during
the fulfillment process.
Holds the SKU name. Use the buttons beside
this property to:
- Supply a SKU by clicking the Edit button,
which opens the Select an Item dialog box.
Locate a SKU, click the radio button beside it,
and then click OK .
- Remove a SKU by clicking the Clear button.
Keywords
Lists keywords used when searching for the

selected product in ATG Merchandising or on
your Web site. Use the buttons beside this
property to:
- Rearrange the position of a keyword in the list
by changing the number beside it. To preview
the new order, click Reorder.
- Remove a keyword by clicking the Delete
button beside it.
- Add a keyword, by clicking Add Existing to
add a row to the table and entering a keyword
in it.
199
Large Image

Holds the media asset representing the

selected assets large image. Use the buttons
- Associate an existing media asset to the
selected asset by clicking Select to open the
media asset, click the radio button beside it,
and then click OK.
- Create a media asset for the image that will be
associated with the selected asset by clicking
Add New, selecting the media asset type
(typically media-external or media-internalbinary), and then clicking Next. The Details
pane displays with empty media asset
Creating Media Assets and Folders.
- Modify the associated media assets
properties by clicking Edit Media to display the
assets properties in the Details pane. See
Modifying and Previewing the Properties of
Assets in a Catalog for editing instructions.
- Disassociate a media asset from the selected
asset by clicking Clear Media.
List Price
Holds the base price.
In the Pricing tab for SKUs and Configurable SKUs

Long Description

Media
In the Media tab for Promotions

Name
Holds a detailed description of the selected

asset. You might use this text box to hold the
product copy that appears on the Web site.
Holds the media asset that represents the
promotion. See the Large Image property for
a detailed description.
Holds the name of the selected asset.
In the Basics tab for Media Assets, Media Folders,

Catalog Folders, Catalogs, Categories, Products,
SKUs, Configurable SKUs, SKU Links, Configurable
Properties, and Configurable Options
On Sale
Indicates whether the sale price (true) or the

list price (false) is used.
200
Parent Folder
In the Basics tab for Media Assets and Media

Folders
Holds the name of the assets parent. Use the

button beside this property to:
- Add or replace a parent by clicking the Edit
Navigate to the asset parent you want to use,
OK.
- Remove a parent by clicking the Clear button.
Price
In the Basics tab for Configurable Options
Product
Holds the price used for the SKU associated

with the configurable option. If no price is
provided here, the price supplied in the SKU is
used.
Holds the product represented by the
configurable option. Use the buttons beside
this property to:
- Add or replace a product by clicking the Edit
Navigate to the product you want to use, click
- Remove a product by clicking the Clear
button.
Quantity
In the Basics tab for SKU Links

Related Categories (group)
In the Basics tab for categories
Holds the quantity of SKUs to include in the

bundled link.
categories listed in the Dynamic Related
Category property. Use the buttons beside this
property to:
Delete button.
201
Related Products (group)
In the Cross-Sell tab for products

products listed in the Dynamic Related Product
to:
Delete button.
Sale Price
Holds the price used when the asset is on sale.

SKU
Holds the SKU represented by the configurable

option. Use the buttons beside this property to:
- Add or replace a SKU by clicking the Edit
Navigate to the SKU you want to use, click the
- Remove a SKU by clicking the Clear button.
- Create a SKU will be automatically associated
with the configurable option by clicking
Create. The Details pane displays with empty
SKU properties that you should fill in as
described in Creating SKUs and Configurable
SKUs.
202
SKUs
In the SKUs tab for Products
Lists the SKUs nested in the selected product.

Use the buttons beside this property to:
- Replace one SKU with another by clicking the
Edit button to open the Select an Item dialog
box. Navigate to the SKU replacement, click the
- Rearrange the position of a SKU in the
product list by changing the number beside it.
To preview the new order, click Reorder.
- Remove the SKU as a child of the product by
clicking the Delete button beside it. If the
selected product was the SKUs only parent, the
SKU is an orphan visible in the Catalog Orphans
view, not Catalog view.
- Move a SKU into the selected product by
Item Dialog box. Navigate to the SKU, click the
- Create a SKU that will be a child to the
selected product by clicking Create. In the
Details pane, select SKU or configurable SKU
from the dropdown list, then click Next. The
Details pane displays with empty SKU
Creating SKUs and Configurable SKUs.
Small Image

Start Date
In the Basics tab for Media Folders, Categories,

Products, SKUs, Configurable SKUs, and SKU Links
Holds the media asset that represents the large

category image. See the Large Image property
for a detailed description.
Holds a start date and time. This property is
used in conjunction with the End Date
property to provide the date range during
which the selected asset is active on the Web
site. In order for these dates to be used, you
need to implement the StartAndEndDate
collection filter.
203
Template
In the Basics tab for Categories, Products, SKUs,

Holds the media asset that represents the JSP

template used to display the selected asset on
your Web site. Use the buttons beside this
property to:
- Add or replace a template by clicking the Edit
Navigate to the media asset you want to use,
OK.
- Remove a template by clicking the Clear
button .
- Create a media asset for your template that
will be automatically associated with the
selected asset by clicking Create, selecting the
type of media asset (typically media-external),
and then clicking Next. The Details pane
displays with empty media asset properties
Media Assets and Folders.
Thumbnail Image

URL
Holds the media asset that represents the

thumbnail category image. See the Large
Image property for a detailed description.
Holds the URL that accesses the external file.
In the Browse tab for Media-External Assets

Wholesale Price
Holds the wholesale price.

The following table describes the properties provided by standard catalogs that dont exist also for
custom catalogs:
204
Description
Child Categories
Lists the categories nested in the selected category. Use the

In the Basics tab for Categories
- Replace one category with another, by clicking the Edit button

to open the Select an Item dialog box. Navigate to the category
replacement, click the radio button beside it, and then click OK.
- Rearrange the position of a nested category in the selected
one by changing the number beside it. To preview the new
order, click Reorder.
- Remove a category from the catalog, click the Clear button. If
the nested category had only one parent, it is now an orphan
visible in the Catalog Orphans view, not Catalog view.
- Move a category into the selected one by clicking Add
Existing to open the Select an Item Dialog box. Navigate to the
category, click the radio button beside it, and then click OK.
- Create a category that will be a fixed child category, by clicking
Add New. The Details pane displays with empty category
properties that you should fill in as described in Creating
Categories.
Related Categories
Lists a grouping of categories related to the selected category.

Use the buttons beside this property to:
- Replace one category with another by clicking the Edit button
to open the Select an Item dialog box. Navigate to the category
replacement, click the radio button beside it, and then click OK.
- Rearrange the position of a category in the group by changing
the number beside it. To preview the new order, click Reorder.
- Remove a category from the group by clicking the Clear
button. If the removed category had only one parent, the
removed category is now an orphan visible in the Catalog
Orphans view, not Catalog view.
- Move a category into the selected category by clicking Add
Existing to open the Select an Item Dialog box. Navigate to the
category, click the radio button beside it, and then click OK.
- Create a category that will be part of this related categories
group, by clicking Add New. The Details pane displays with
empty category properties that you should fill in as described in
Root
Indicates whether the selected category is at the top level of the

hierarchy (true) or nested in another category (false).
205
Related Products
In the Cross-Sell tab for Products
Lists a grouping of products related to the selected product. Use

the buttons beside this property to:
- Replace one product with another by locating a product in the
list and clicking the Edit button beside it in order to open the
Select an Item dialog box. Navigate to the replacement product,
click the radio button beside it, and then click OK.
- Rearrange the position of a product in the group by changing
the number beside it. To preview the new order, click Reorder.
- Remove an existing product from the group by clicking the
Clear button.
- Move a product into the group by clicking Add Existing to
open the Select an Item Dialog box. Navigate to the product,
click the radio button beside it, and then click OK.
- Create a product that will be part of the related product group
by clicking Add New. The Details pane displays with empty
product properties that you should fill in as described in
Creating Products.

The following table describes the properties provided by custom catalogs that dont also exist for
standard catalogs:
206
Description
Catalog Specific Information
Holds mappings that consist of a catalog ID

and catalog specific information asset (info
object), which defines custom properties. This
property can display catalog-specific properties
organized by catalog when you have assets
that are part of more than one catalog. Use the
In the Cross-Sell tab for Products and in the Basics

tab for SKUs and Configurable SKUs
- Replace the info object, by clicking the Edit

button beside it to open the Select an Item
dialog box. Click Find to locate all info objects
of that type. Click the radio button beside your
selection, and then click OK.
- Remove a list mapping by clicking the Delete
button beside it.
- Add a new entry in the list by clicking Add
New, entering a catalog ID in the Key text box,
and clicking Next. Click Create.
Child Catalogs
In the Basics tab for Catalog Folders
Lists catalogs nested in the catalog folder. Use

the buttons beside this property to:
- Remove a nested catalog from the catalog
folder by clicking the Delete button beside it. If
the removed catalog had only one parent, it is
now an orphan visible in the Catalog Orphans
- Rearrange the position of a nested catalog in
the catalog folder by changing the number
Reorder.
- Move an existing catalog into the catalog
folder by clicking Add Existing to open the
Select an Item Dialog box. Navigate to the
catalog, click the radio button beside it, and
then click OK.
- Create a catalog that will be nested in the
catalog folder by clicking Add New. The Details
pane displays with empty catalog properties
Catalogs
207
Child Folders
In the Basics tab for Catalog folder
Lists catalog folders nested in the selected

catalog folder. Use the buttons beside this
property to:
- Remove a child folder by clicking the Delete
button beside it.
- Rearrange the position of a nested folder in
the catalog folder by changing the number
Reorder.
- Move an existing catalog folder into the
selected one by clicking Add Existing to open
the Select an Item Dialog box. Navigate to the
catalog folder, click the radio button beside it,
and then click OK.
- Create a catalog folder that will be nested in
the selected catalog folder by clicking Add
New. The Details pane displays with empty
catalog folder properties that you should fill in
as described in Creating Catalog Folders.
208
Fixed Child
Categories
Lists the categories nested in the selected

category. Use the buttons beside this property
to:
- Replace one nested category with another by
clicking the Edit button to open the Select an
Item dialog box. Navigate to the category
and then click OK.
- Rearrange the position of a category in the
selected category by changing the number
Reorder.
- Remove a nested category from the selected
one by clicking the Delete button beside it. If
the removed category had only one parent, it is
- Move an existing category into the selected
category by clicking Add Existing to open the
Select an Item Dialog box. Navigate to the
category, click the radio button beside it, and
then click OK.
- Create a category that will be nested in the
selected category by clicking Add New. The
Fixed Child Products
In the Products tab for Categories
See Fixed Child Categories for a description,

substituting product for category as the type of
asset you are replacing, rearranging, removing,
moving, or creating.
209
Fixed Related
Categories
Lists a static grouping of categories related to

the selected category. All fixed child categories
must exist in the same catalog as the selected
category. Use the buttons beside this property
to:
- Replace one category with another by clicking
dialog box. Navigate to the category
and then click OK.
- Rearrange the position of a category in the
group by changing the number beside it. To
- Remove a category from the group by clicking
the Delete button beside it. If the removed
category had only one parent, the removed
category is now an orphan visible in the
Catalog Orphans view, not Catalog view.
- Move a category into the selected category by
Item Dialog box. Navigate to the category, click
- Create a category that will be part of this
related categories group, by clicking Add New.
The Details pane displays with empty category
210
Fixed Related Products
In the Cross-Sell tab for Product
Lists a static grouping of product related to the

selected category. Use the buttons beside this
property to:
- Replace one product with another by locating
a product in the list and clicking the Edit
button beside it in order to open the Select an
Item dialog box. Navigate to the replacement
product, click the radio button beside it, and
then click OK.
- Rearrange the position of a product in the
group by changing the number beside it. To
- Remove an existing product from the group
by clicking the Delete button beside it.
- Move a product into the group by clicking
box. Navigate to the product, click the radio
- Create a product that will be part of the
related product group by clicking Add New.
The Details pane displays with empty product
Creating Products.
Management Display Name
In the Basics tab for Products
Holds the name used for the product in the

Navigation pane of ATG Merchandising. The
name you provide here will not be visible on
your Web site. If you do not provide a
Management Display Name, one will be
generated for you.
211
Parent Categories for Catalog
Lists all parent categories for the selected

product. Use the buttons beside this property
to:
- Replace one parent category with another by
locating the category in the list, and then
clicking the Edit button beside it in order to
open the Select an Item dialog box. Navigate to
the replacement category, click the radio
button beside it, and then click OK. Update the
key as needed.
- Remove the selected product from a category
by click the Delete button beside the category.
If the product doesnt have other parents, it is
now an orphan visible in Catalog Orphans view,
not Catalog view.
- Add a category parent by clicking Add
Existing to open the Select an Item Dialog box.
Navigate to the category, click the radio button
beside it, and then click OK. In the Key column,
enter a label that identifies the usage.
- Create a category that will be a parent to the
selected product by clicking Add New. In the
Key text box, enter ID for the category that will
contain the selected product, and then click
Next. The Details pane displays empty
category properties that you should fill in as
described in Creating Categories.
212
Replacement Products
Lists products that may be advertised to

visitors when the selected product is out of
stock. Use the buttons beside this property to:
- Replace one product with another by clicking
the Edit button beside a product in order to
open the Select an Item dialog box. Navigate to
the product replacement, click the radio button
- Rearrange the position of a product in the list
by changing the number beside it. To preview
the new order, click Reorder.
- Remove a product from the list by clicking the
Delete button beside it.
- Add a product to the list by clicking Add
Existing to open the Select an Item dialog box.
Navigate to the product, click the radio button
- Create a new product that will be added to
the replacement list by clicking Add New. The
Details pane displays with empty product
Creating Products.
213
Root Categories
In the Basics tab for Catalogs
Lists categories that are direct children of the

catalog. A category nested two levels below
the catalog, for example, wouldnt display in
this list. Use the buttons beside this property
to:
- Replace one category with another by clicking
dialog box. Navigate to the replacement
category, click the radio button beside it, and
then click OK.
- Remove a category from the catalog by
clicking the Delete button beside it. If the
removed category had only one parent, it is
- Move a category into the selected catalog by
Item Dialog box. Navigate to the category, click
- Create a category that will be a child of the
selected catalog by clicking Add New. The
214
Sub Catalogs
Lists the names of catalogs nested anywhere in

the selected category, such as direct children
and nested descendants. Use the buttons
- Replace one catalog with another by locating
the catalog in the list, and then clicking the
Edit button beside it in order to open the
replacement catalog, click the radio button
beside it, and then click OK. If the catalog being
replaced doesnt have other parents, it is now
an orphan visible in Catalog Orphans view, not
Catalog view.
- Rearrange the position of a category nested in
a catalog by changing the number beside it. To
- Remove a catalog from the selected category
by clicking the Delete button beside the
catalog you want to remove. If the removed
catalog had only one parent, it is now an
orphan visible in the Catalog Orphans view, not
Catalog view.
- Move a catalog into the category by clicking
box. Navigate to the catalog, click the radio
- Create a catalog that will be a child of the
category by clicking Add New. The Details
pane displays with empty catalog properties
Catalogs.
215
Sub-Catalogs at Root
In the Basics tab for Catalogs
Lists the names of catalogs that are direct

children of the selected catalog. A catalog
nested two levels below the catalog, for
example, wouldnt display in this list. Use the
- Replace one catalog with another by clicking
dialog box. Navigate to the catalog
and then click OK. If the catalog being replaced
doesnt have other parents, it is now an orphan
visible in Catalog Orphans view, not Catalog
view.
- Remove a catalog nested in the selected one
by clicking the Delete button. If the removed
catalog had only one parent, it is now an
orphan visible in the Catalog Orphans view, not
Catalog view.
- Move a catalog into the selected catalog by
Item Dialog box. Navigate to the catalog, click
- Create a catalog that will be a child of the
selected catalog by clicking Add New. The
Details pane displays with empty catalog
Creating Catalogs.

The following table describes the additional properties provided by the Business Commerce module:
216
Description
Manufacturer
Holds the name of the manufacturer for the

product. Use the buttons beside this property
to:
- Add or replace a manufacturer by clicking the

Edit button in order to open the Select an Item
dialog box. View all manufacturers by clicking
Find. Navigate to the manufacturer you want to
use, click the radio button beside it, and then
click OK.
- Remove an existing manufacturer by clicking
the Clear button beside it.
- Add a new manufacturer and assign it the
selected product by clicking Create. The Details
pane displays with empty manufacturer name,
description, long description, and email
properties, which you should fill in, and then
click Create.
Manufacturer Part Number

Quantity

Unit of Measure
Holds the ID used by the manufacturer to

identify the SKU.
Holds the number of items contained in one
unit of the SKU.
Holds the type of measurement used for the
value in the Quantity property.

The following table describes the additional properties provided by the modules that support ATG
Search, core Commerce, and Content Administration.
Description
Allow subcategories to inherit
Indicates whether only the products and SKUs included in

facets associated with the selected category are nested in
that category directly (false) or may be nested its
descendant categories as well (true).
Facet tab for Categories
217
Inherit facets from parent categories

Inherited facets
Inherit global facets
Local facets
Indicates whether products and SKUs in the selected

category are included in facets defined in parent categories
(true) or excluded from them (false).
Holds the name of each facet inherited by the selected
category.
Indicates whether products and SKUs nested in the selected
category are included in global facets (true) or excluded
from them (false).
Holds the list of local facets associated with the selected
category. Use this property to:
- Create a new local facet and add it to the selected
category.
- Rearrange the position of a local facet in the selected
category.
- Delete a local facet, which disassociates the facet from the
category and deletes the facet.

The following table describes the additional properties provided by the modules that support ATG
Search, Business Commerce, and Content Administration.
Description
Allow subcatalogs and categories to inherit
Indicates whether only the products and SKUs

included in facets associated with the selected
catalog are nested in that catalog directly (false) or
may be nested its descendant catalogs and
categories as well (true).
Facets tab for Catalogs
Inherit facets from parent catalogs

Facet tab for Catalogs and Categories
Inherited facets
Facet tab for Catalogs
Indicates whether products and SKUs in the selected

item are included in local facets defined for parent
catalogs (true) or excluded from those facets
(false).
Holds the name of each facet inherited by the
selected catalog.
218
Inherit global facets

Facets tab for Catalogs
Local facets
Facet tab for Catalogs
Indicates whether products and SKUs nested in the

selected catalog are included in the global facets
(true) or excluded from them (false).
Holds the list of local facets nested in the selected
catalog. Use this property to:
- Create a new local facet and associate it with the
selected catalog.
- Rearrange the position of a local facet in the
selected catalog.
- Delete a local facet, which disassociates the facet
from the catalog and deletes the facet.
219
Index
A
about promotions, 98
ACC. See ATG Control Center
AccessControlServlet, 44
accounts, 43
activities, tailoring the UI. See default activity
adding assets to the Project tab, 18
administer commerce search, 18
administrative tasks, 9
assemblying and deploying an application, 32
changing deployment workflow, 42
configuring a purchased application, 39
configuring AccessControlServlet, 44
configuring an evaluation database, 26
configuring the user interface, 177
configuring workflows, 41
creating projects, 18
deploying projects, 20
destroying database tables, 35
importing data, 30
installing ATG Merchandising, 25
search configurations, 55
Search Merchandising views, 80
setting up user accounts and roles, 43
versioned Business Commerce tables, 28, 36
versioned core Commerce Search tables, 36
versioned core Commerce tables, 27, 37
versioned custom catalog Search tables, 29, 35
versioned custom catalogs tables, 27, 37
versioned Search tables, 29, 36
advancing from one task to another, 19
All Others dimension value, 51
application assembly, 32
application deployment, 32
apply to all, 121
asset types, 67
changing visible types in trees, 179
assets, 13
adding to Multi Edit tab, 117
adding to Project tab, 19
creating based on existing, 108
creating original, 90
deleting, 174
deploying, 20
editing in bulk, 85, 116
editing individually, 115
icons, 67
in Breadcrumb drop-down list, 86
linking, 109
locating, 71
moving, 111
property descriptions, 193
removing, 171
reverting changes, 19
searching for, 82
unlinking, 110
visible in Search tab, 185
assigning price lists, 140, 141
ATG Business Control Center, 9, 22, 61
ATG Control Center, 9, 22
ATG Merchandising
accessing, 61, 63
browsing, 63
configuring evaluation copy, 26
configuring purchased copy, 39
databases. See content administration databases
removing, 35
setup checklist, 39
terminology, 13
user interface, 61
ATG Merchandising user interface. See user interface
author task, 18, 19
B
base prices lists. See price lists
base search configurations, 16
creating, 102
inheriting settings from, 156
language, 56
view, 80
Base Search Configurations view, 80
basic pricing, 48
BCC. See ATG Business Control Center
Breadcrumb drop-down list, 86
Browse tab
Base Search Configurations view, 80
Catalog Orphans view, 72, 184
Catalog view, 71, 184, 188
Coupons view, 74, 184, 188
Facet view, 78
Media view, 75, 184
Price Lists and Folders view, 76, 184
Price Lists view, 76, 184
Promotions view, 73, 184, 188
Property Prioritization view, 80
Search Configurations Tree view, 79
Segment List view, 80
220
Index
visible views, 183

browsing ATG Merchandising, 63
buckets, 179
bulk editing. See multi edit
bulk prices, 140
buttons, 68
hiding/showing, 188
C
catalog folders, 14
creating, 90
deleting, 172
modifying, 115
moving, 112
parent optional, 14
removing, 171
Catalog Orphans view, 72, 184
Catalog view, 71, 184, 188
catalogs, 14
creating, 91
custom. See custom catalogs
modifying, 115
removing, 171
standard. See standard catalogs
standard vs. custom, 17
categories
creating, 92
modifying, 115
removing, 171
category facets, 144
commerce assets. See assets
configurable options
creating, 107
modifying, 115
configurable properties
creating, 106
modifying, 115
configurable SKUs
creating, 105
modifying, 115
configuring a development database, 31
configuring AccessControlServlet, 44
configuring an evaluation database, 26
configuring custom catalogs, 44
configuring secured repositories, 45
configuring the ATG Merchandising UI, 177
configuring workflows, 41
content administration databases, 15
configuring, 26, 31
deployment resources, 40
destroying tables, 35
content management, 13
coupons
accessing Coupons view, 74
creating, 98
modifying property values, 135
Coupons view, 74, 184, 188
creating
assets, 89
base search configurations, 102
catalog folders, 90
catalogs, 91
categories, 92
configurable properties, 106
configurable SKUs, 105
configuration options, 107
coupons, 98
facets, 103
media folders, 94
price list folders, 99, 101
price lists, 99, 100
products, 93
projects, 18
promotions, 96
search configuration folders, 59
SKU links, 106
SKUs, 105
versioned Business Commerce tables, 28
versioned core Commerce tables, 27
versioned custom catalog Search tables, 29
versioned custom catalogs tables, 27
versioned Search tables, 29
workflows, 177
creating assets based on existing assets, 108
creating media assets, 94
media-external, 96
media-internal-binary, 95
media-internal-text, 95
creating original assets, 90
custom catalogs, 14
assigning price lists to organizations, 141
configuring, 44
creating catalog folders, 90
creating catalogs, 91
creating versioned tables, 27
different from standard, 17
properties unique to, 206
customizing views, 178
D
databases, 15
configuring for development, 31
configuring for evaluation, 26
destroying tables, 35
importing content, 30
versioned Business Commerce tables, 28, 36
versioned core Commerce Search tables, 29, 36
versioned core Commerce tables, 27, 37
versioned custom catalog Search tables, 29, 35
versioned custom catalogs tables, 27, 37
versioned Search tables, 29, 36
221
Index
DCS-UI, 32
deactivating promotions, 175
default activity
Browse tab views, 183
default settings, 182
tabs, 182, 185
tags in a task configuration file, 181
view mapping, 186
default deployment workflow, 41
default task
Browse tab views, 188
buttons, 188
default settings, 187
tabs, 188, 189, 190
view mapping, 191
defining promotions, 127
for a particular asset, 128
defining search configurations, 155
defining selections, 149
delete project task action, 19
deleting
assets, 171, 174
base price lists, 173
Catalog Orphans view, 172
facets with nested facets, 174
media folders with children, 172
parents from a catalog, 172
promotions, 174
deleting search configuration rules, 164
deploy now or later task, 19
deploying assets in a project, 20
deployment
configuring resources, 40
workflows, 41
designing a site with multiple facets, 143
destination repository, 40
destroying database tables, 35
versioned Business Commerce tables, 36
versioned core Commerce Search database tables, 36
versioned core Commerce tables, 37
versioned custom catalog Search database tables, 35
versioned custom catalogs tables, 37
versioned Search database tables, 36
Details pane, 71
dimensions, 16, 49
All Others value, 51
language, 16, 56
segment, 16, 58
disabling search configuration rules, 164

duplicating assets, 108
Dynamic Search and Navigation. See facets
E
early staged workflow, 42
editCommerceAssets. See manage commerce assets
F
Facet view, 78
Faceting Property, 149
facets, 16, 21
category, 144
collaborative, 144
creating, 103
defining, 143
deleting, 174
examples, 143
excluding products, 147
Facet view, 78
Faceting Property, 149
general properties, 149
global vs. local, 21, 103
including products, 147
independent, 145
multiple, 143
name, 149
nested, 145, 154
removing, 171
selections, 149
finding what you need, 9
folders
catalog. See catalog folders
dynamic. See bucket
media. See media folders
price list. See price list folders
search configuration. See search configuration folders
222
Index
images. See media assets

importing required content, 30
installing ATG Merchandising, 25
Internet Explorer, 61
Merchandising. See ATG Merchandising

modifying asset property values, 115
modifying assets in bulk. See multi edit
modifying assets individually, 115
modules, 32, 33
moving, 111
catalog folders, 112
price list folders, 112
multi edit, 85, 116
apply to all, 121
list edit, 119
step edit, 117
Multi Edit tab, 85, 188, 190
multiple facets, 143
JBoss
JSP assets. See media assets
Navigation pane, 71
changing settings, 179
modifying an existing list view, 179
modifying an existing tree view, 178
nested facets, 154
deleting, 174
G
getting started, 25
global facets, 16, 78, 103, 145, 147
H
how deleting works, 171
L
labels, UI elements, 180
language, dimension, 56
linking, 15, 109
parent, 14
list edit, 119
list views, modifying, 179
local facets, 16, 78, 103, 145, 147
locating assets, 71
M
manage commerce assets workflow, 18, 41, 42, 61
media assets, 14
creating, 94
deleting, 172
deleting media assets with children, 172
Media view, 75
modifying, 115
parents required, 14
removing, 171
media folders, 14
creating, 94
deleting, 172
modifying, 115
parent optional, 14
removing, 171
Media view, 75, 184
media-external assets, 14
creating, 96
media-internal-binary assets, 14
creating, 95
media-internal-text assets, 14
creating, 95
O
organizations, 141
organizing assets, 89
orphans, 15
deleting, 172
linking to parents, 109
parents, 14
unlinking, 110
overview of ATG Merchandising, 13
P
parents, 14
deleting, 172
linking, 109
orphans, 15
unlinking, 110
prerequisites, 25
previewing pages, 124
price list folders
creating, 101
moving, 112
removing, 171
price lists, 15, 48
assigning to users, 140
base price lists, 15
creating, 100
defining, 137
deleting, 173
different from basic pricing, 48
providing prices, 138
removing, 171
223
Index
views, 76, 184

volume pricing, 140
Price Lists and Folders view, 76, 184
Price Lists view, 76, 184
pricing, basic vs. lists, 48
product catalogs. See catalogs
products
creating, 93
modifying, 115
providing prices for price lists, 138
removing, 171
Project tab, 19, 84, 188, 189
projects, 17
accessing, 64
adding assets, 19
administer commerce search workflow, 18
creating, 18
deployment, 20
manage commerce assets workflow, 18
Project tab, 84
reverting asset changes, 19
tasks, 18
using to access ATG Merchandising, 61
workflows, 15
promotions
active dates, 128
building discount rules, 127
creating, 96
deactivating, 175
defining, 127
deleting, 174
implementing, 98
item discount for a specific asset, 128
Promotions view, 73, 184
Promotions view, 73, 184, 188
properties
base versioned Commerce, 193
custom catalogs only, 206
facets, 217, 218
managing in the Property Prioritization tab, 55
modifying values, 115
Prioritization tab set up view, 80
standard catalogs only, 204
undoing value changes, 124
property groups, 116
importing examples, 30
property prioritization in search configurations, 165
Property Prioritization tab
managing properties, 55
Property Prioritization view, 80

property value ranking in search configurations, 166
publishing user, 43
R
ready for review task action, 19
redirection rules, 156
reject task action, 19
removing
assets, 171
ATG Merchandising, 35
repository
destination, 40
source, 40
target, 40
resource bundles, 180
task configuration file, 182, 184
result exclusion rules, 156
result positoning rules, 156
reverting asset changes, 19
review content task, 19
roles, 43
running ATG Merchandising, 32
S
creating, 59
deleting, 59
language, 56
moving, 112
order, 52
segment, 58
view, 79
search configurations, 16, 22
copying settings, 168
creating, 102
defining, 155
disabling or deleting rules, 164
inherited property prioritizations, 169
inherited rules, 164
inheriting settings, 156
language, 56
moving, 112
order, 52
properties in the Property Prioritization tab, 55
property prioritization, 165
property value ranking, 166
redirection rules, 156
result exclusion rules, 156
result positioning rules, 156
rule order, 157
segment, 58
view, 79
search configurations tree, 48
administration, 55
design, 49
language significance, 54
order of contents, 52
types, 49
224
Index
Search Configurations Tree view, 79

Search Merchandising, 22, 48
administration, 55
views, 79, 80
Search tab, 82, 185
secured repositories, 45
Segment List view, 80
segments
dimension, 58
view, 80
selections, 16, 149
ordering, 154
types, 150, 151, 153
setting up
a purchased copy of ATG Merchandising, 39
an evaluation copy of ATG Merchandising, 26
Internet Explorer, 61
user accounts and roles, 43
SKU links
creating, 106
modifying, 115
SKUs
creating, 105
modifying, 115
providing prices for price lists, 138
removing, 171
SOLID database, 26
source repository, 40
specifying a selection sort order, 154
SQL repositories, 14
standard catalogs, 14
different from custom, 17
standard workflow, 42
startup modules, 32
step edit, 117
subcatalogs. See catalogs
T
tabs
Browse, 183
hiding/showing, 182, 188
Multi Edit, 85, 117
ordering, 182, 188
Project, 84, 189
Search, 82, 185
visible to activities, 182
visible to tasks, 188
tailoring the UI for specific workflows, tasks, and
activities, 180
target repository, 40
task actions, 19
delete project, 19
ready for review, 19
reject, 19
task configuration file, 180
anatomy, 181
default activity, 182

default task, 187
resource bundles, 180, 182, 184
tags, 181
view mapping, 186, 191
tasks, 18
advancing, 19
assigning, 64
author, 18, 19
deploy now or later, 19
review content, 19
tailoring UI, 180
terminology, 13
third-party application servers, 32
tiered prices, 140
tree view
changing bucket size, 179
changing visible asset types, 179
U
undoing property value changes, 124
unlinking, 110
orphan, 15
parent, 14
user accounts, 43
user interface, 61, 180
accessing, 61
configuring, 177
custom catalog differences, 17
customizing views, 178
other than Merchandising UI, 22
resource bundles, 180
users
assigning price lists, 140
of this guide, 9
publishing, 43
roles, 43
using and defining price lists, 137
using dynamic selection, 151
using guided selection ranges, 153
using one selection for each faceting property value, 150
using projects, 17
using specified selections, 153
V
versioned
assets, 8
databases, 15, 26
view mapping
default activity, 186
default task, 191
imported data, 30
task configuration file, 186, 191
views
Base Search Configurations, 80
Catalog, 71
Catalog Orphans, 72
225
Index
Coupons, 74
customizing, 178
Facet, 78
hiding/showing, 183
Media, 75
ordering, 183
Price Lists, 76
Price Lists and Folders, 76
Promotions, 73
Property Prioritization, 80
Search Configurations Tree, 79
secured repositories, 47
Segment List, 80
visible to activities, 183
volume pricing
bulk prices, 140
tiered prices, 140
W
WebLogic
workflows, 15, 18, 41
administer commerce search, 18
changing deployment workflow, 42
creating, 177
default deployment, 41
early staged, 42
manage commerce assets, 18, 41, 42
standard, 42
tailoring UI, 180
tasks, 18
working on tasks, 18
226
Index

Atg Merchandising User Guide

Încărcat de

Informații document

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

Atg Merchandising User Guide

Încărcat de

Drepturi de autor:

Formate disponibile

atg

Merchandising User Guide

ATG Merchandising User Guide

ATG Merchandising User Guide

Users of this Guide

Overview of ATG Merchandising

Configuring ATG Merchandising

ATG Merchandising User Guide

Using the ATG Merchandising User Interface

Setting Up Internet Explorer

ATG Merchandising User Guide

Creating and Organizing Assets

Creating Original Assets

Modifying and Previewing the Properties of Assets in a Catalog115

10 Using and Defining Price Lists

ATG Merchandising User Guide

Providing Price Lists to Users

12 Defining Search Configurations

14 Customizing the ATG Merchandising User Interface

ATG Merchandising User Guide

Working with Resource Bundles

Appendix: Asset Properties

ATG Merchandising User Guide

ATG Merchandising User Guide

Users of this Guide

Finding What You Need

ATG Merchandising User Guide

Developing catalogs and their

Covered in several chapters

Accessing ATG Merchandising

See the Using the ATG

Conceptual information about

See the ATG Content

Description of the ATG Business

See the ATG Content

Accessing ATG Business Control

Business Users, Site

See the Accessing the ATG

Creating a catalog and

See the ATG Commerce

Working with all out-of the-box

Covered in several chapters

Tailoring the search results that

Business Users, Site

Covered in several chapters

Creating facets and defining

Covered in several chapters

ATG Merchandising User Guide

Developing JSPs that implement

See the Dynamic Search and

Page Developers, Programmers

See the ATG Commerce

Accessing ATG Control Center

Page Developers, Programmers

In the Windows Start menu,

Building JSPs that use

See the ATG Commerce Guide

Starting up ATG Merchandising

See the Running ATG

Installing database tables in

The process is outlined in the

Understanding and configuring

See the Search Merchandising

Customizing the ATG Business