Use this action to disable a scenario for all users who are passing through it when the action occurs. The action has the same effect as manually disabling a scenario through the ACC; for more information, refer to the ATG Personalization Guide for Business Users.
Example: On Dec 31, 2004 at 12:00:00 AM --– Disable Scenario
Scenario editor display name: Disable scenario
Action Registry Tag | Value |
|---|---|
action name |
|
configuration component |
|
action terminal | true |
action execution policy | collective |
action error response | delete |
This action has no parameters.
Note that this action disables only the scenario in which it occurs; you cannot disable a scenario from within another scenario.
The action does not disable the scenario itself, because this behavior requires making a change to the scenario’s definition file, which can be done only by the process editor server. Instead, the DisableScenario action sends an atg.dss.DisableProcess message on a SQL JMS topic to all global servers. The message is ignored by all servers except the process editor server, which makes the following changes to the scenario’s definition file:
The
enabledattribute is set to false.The
modification-timeattribute is set to the current time.The
last-modified-byattribute is set to the stringsystemto indicate that the scenario was disabled automatically rather than by an ACC user.The
modified-by-serverattribute is set to true. This setting allows the process update and process end messages sent by all servers in response to this action to include appropriate update and end code values.
