Typically after you create a category in your catalog you then add products to the category.Â The simple way to do that in ATG eCommerce is to use the ACC and add products to the child products property of the category.Â However there is another way.
In the ATG Commerce Guide to Setting Up a Store documentation you can see in the Viewing the Product Catalog section that a category can have child products but also child product groups.
Child product groups are actually content groups which are described in the Creating Content Groups chapter of the ATG Personalization Guide for Business Users.
Though the documentation shows a content group composed of features you can easily create a content group using the ProductCatalog as a content source and product as a content type.
To create a content group follow the steps in the ATG documentation for Creating New Content Groups except use an item from the ProductCatalog when specifying the Content Type.Â Then create the targeting rules for this Content Group.Â Now you can specify this group in the Child products (group) property of a category.
Sometimes you will find that you cannot create or duplicate scenarios.Â You keep clicking on the grayed out New Scenario button and right-clicking on scenarios you want to duplicate but nothing happens.
Fortunately the solution is rather simple and is alluded to in the ATG Personalization Programming Guide â€“ Configuring the Process Editor Server.
First you create a scenarioManager.xml file in your /home/localconfig/atg/scenario directory like the following.
Next you replace foobar:8850 with the value of /atg/dynamo/service/ServerName.serverName.Â You may want to configure the serverName value to something you want because sometimes it might change if for example when you connect via VPN.
Then you restart ATG and reconnect or restart the ACC and you should be able to create and duplicate scenarios.
(Note that when you create the workflowProcessManager.xml file in your /home/localconfig/atg/epub/workflow/process directory it can have the exact same contents as the scenarioManager.xml file.)