When business managers create scenarios in the ACC, they build the scenarios from a range of elements that include events and actions. Events are instances of site visitor behavior that the business manager wants the scenario to watch for; for example, he or she can create a scenario that watches for a visitor to register at the site or to go to a specific page. “Registers” and “Visits page” are both examples of scenario events. Actions, on the other hand, are instances of system behavior - often what the system does in response to an event. For example, a scenario might watch for visitors to register, and then send an e-mail. “Send E-mail” is an example of a scenario action. Conditions are filters that qualify the previous event element in a scenario; for example, you could follow the event “Views any item” with the condition “Browser’s type is Netscape Navigator.”

If the events, actions, and conditions that come with the Scenarios module do not meet your requirements, you can add your own. This section explains the process of creating custom elements so that they appear in the ACC for your business managers to use:

Note: As described in this chapter, scenario events are instances of JMS messages, and the procedure for creating a custom event therefore involves editing various files that configure the sending and receiving of messages. The examples in this chapter assume your application uses SQL JMS as the JMS provider. For information on the code to add to these files if you use other JMS providers (for example, for applications running on IBM WebSphere), refer to Dynamo Messaging System in the ATG Platform Programming Guide.