This section describes the default event elements you can insert into a scenario segment (see Creating a Scenario: Basic Steps in the ATG Personalization Guide for Business Users).
Scenario event elements are triggered when the Scenario Manager component receives events sent as Dynamo Message System messages. The description of each event element below includes the name of the message that triggers the event and the component or part of the system that is responsible for sending the message. The optional parameters that appear in the scenario editor for a specific event correspond to the properties of the message that represents that event, including properties inherited from any parent classes. For example, the parameters that you can select in the scenario editor to further define the Logs In event are the properties associated with the DPSMessageSource component. For more information, refer to the Dynamo Message System chapter in the ATG Platform Programming Guide.
All scenario events have corresponding entries in the Dynamo Message System registry. In addition, the scenarioManager.xml file contains a scenario event registry, which serves to identify the events that you want to associate with scenarios (in contrast to, for example, events that are associated with workflows in ATG Content Administration). The event registry defines various configuration settings for each scenario event, including the message context, which determines whether an event is individual (in other words, it applies to individual users passing through the scenario, such as a PageVisits event) or global (it applies to all users, such as a Startup event).
Note that for compatibility with ATG products before version 6.0, the event registry in the scenarioManager.xml file is turned off by default, and the event information in the Dynamo Message System registry is used instead. To use the scenarioManager.xml event registry, set the useEventRegistry property to true in the ScenarioManager component.
For more information on both the Dynamo Message System registry and the event registry, refer to Adding Custom Events, Actions, and Conditions to Scenarios.
Scenario events can be collective (they affect or are triggered by everyone progressing through the scenario) or individual (they affect or are triggered only by individual users).
Many scenario events are site aware, meaning they can be configured to apply to specific Web sites in an ATG environment that manages more than one site.
The remaining sections of this chapter describe the default collective and individual scenario events available with the Scenarios module.
Collective events:
GSAInvalidation Event Individual events:
