In a scenario, a Condition element follows and further qualifies an Event element, essentially adding an “if” statement to the Event element. The options that appear for the condition vary according to the event that the condition follows. For example, after a “visits page in folder /shoes” Event element, you could have a Condition element that specifies the exact page: “if page is /shoes/hikingboots.jsp.

This section describes the Condition elements provided with Core Commerce for use in scenarios. These commerce Condition elements are in addition to those provided with the Scenarios module. For information about scenarios, how to use Condition elements in scenarios, and non-commerce Condition elements, refer to the Creating Scenarios chapter of the Personalization Guide for Business Users.

If the Condition elements provided with Core Commerce do not meet all of your requirements, your application developers can create custom ones. Custom Condition elements appear in the ATG Control Center, and you can use them as you would use any standard Condition element.

Note for developers: For information about creating custom Condition elements, refer to the Adding Custom Events, Actions, and Conditions to Scenarios chapter in the Personalization Programming Guide. If you need to extend the Scenario module’s grammar for use with custom Core Commerce elements, also refer to the Commerce-Related Grammar Configuration section of the Configuring the ATG Expression Editor chapter in the same guide.

The Condition elements provided with Core Commerce are described in the sections that follow.

Copyright © 1997, 2015 Oracle and/or its affiliates. All rights reserved. Legal Notices