# Scenario Detail

In the scenario detail definition screen, you create a list of steps that make up the scenario.

## step

A step is a unit task that is arranged in the order of execution of the scenario. The name of each step (name) is the name used to access context data managed throughout the entire lifecycle of the scenario. The steps that make up the scenario are executed sequentially by the scenario engine, and the execution order can be specifically altered by flow control tasks.

## flow control task

- end
- goto
- switch (switch-goto)
- switch-range (switch-range-goto)
- throw

## properties

- name
  - The name of the scenario step
- description
  - A brief description of the scenario step
- result
  - Whether to include it in the scenario (instance) execution result
- skip
  - Whether to include it in the scenario execution
- log
  - Whether to log the execution result
- connection
  - Set if it's a connection-based scenario. If no connection is set, you can choose one of the common tasks of the scenario engine.
- task
  - If a connection is set, you can set connection-based tasks. If no connection is set, you can choose one of the common tasks of the scenario engine.
- parameter
  - Set parameters relevant to task configuration.

## operations

- add step
- remove step
- sequence move up / down
- save
- delete