# Scenario

In the Scenario Definition screen, you can manage scenarios to be operated by the system (create/modify/delete/test).

## Properties

- Name
  - Specify the name of the scenario.
  - The name must be unique.
- Description
- Schedule [schedule](./crontab-editor.md)
- Timezone
  - Set the base timezone for when the schedule is to be executed.
- Required Privilege
  - Set the required privileges to execute the scenario.
- Activation Flag
  - Automatically specify whether it starts when the application starts.
- Iteration Scope
  - Specifies the domain scope for sequential scenario execution across multiple domains.
  - **SELF**: Execute the scenario only on the current domain.
  - **CHILDREN**: Execute the scenario only on child domains of the current domain.
  - **SELF & CHILDREN**: Execute the scenario on both the current domain and its child domains.
  - This feature is only applied to StartScenario operations and does not affect RunScenario operations.
  - Scenarios are executed sequentially across the specified domains, ensuring proper order and dependency management.
- TTL(Time To Live)
  - stores the scenario's results in cache and maintains it for the set TTL seconds.
  - if TTL is set greater than 0, the scenario's results will be stored in cache each time it is run. (RunScenario, StartScenario)
  - the cache key is a combination of the scenario ID + domain + scenario call parameter object, recorded by creating a hash key from the call parameter object.
  - if the scenario is run with RunScenario, it first checks for a valid cache, and if one exists, it returns the cached results without actually running the scenario.
  - if the scenario is run with StartScenario, it runs the scenario regardless of the cache status and updates the cache with the results.
- Progress (Information displayed only during monitoring)
  - (Current step number / Total number of steps in the scenario) %
  - Based on the main scenario, server scenarios are calculated as a single step.
- Round (Information displayed only during monitoring)
  - Indicates the current number of repetitions in case of a recurring scenario.
- Message (Information displayed only during monitoring)
  - Message related to the final state of the scenario instance.

## Operations

- Start Monitoring
  - Navigate to the [Integration Monitoring](./integration-monitor.md) screen.
- Copy Scenario
  - Copy the selected scenario.
- Save Scenario
  - Save changes to the scenario.
  - Running scenarios cannot be modified.
- Delete Scenario
  - Delete the selected scenario.
  - Running scenarios cannot be deleted.