> For the complete documentation index, see [llms.txt](https://support.docstudio.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.docstudio.com/user/scenarios/managing-scenarios/how-to-manage-a-scenario.md).

# How to Manage a Scenario

This document explains how to edit, clone, and delete scenarios and scenario steps.

### Scenario edit form

<figure><img src="https://2962383972-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FoqUiFHjwtCCGSaEDqbXb%2Fuploads%2FqVBqoFYTMgbvaAEk3jj2%2Fimage.png?alt=media&amp;token=8dd0abcd-9f60-478c-813a-49a008d5f60d" alt=""><figcaption></figcaption></figure>

1. Source and destination UUIDs.
2. The condition for the step.
3. Condition XSLT field (required if **Condition** is enabled).
4. Action buttons on the step form:

* **Save step** ![](https://2962383972-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FoqUiFHjwtCCGSaEDqbXb%2Fuploads%2FkMgjQeGRIlInIRX2zOUc%2Fimage.png?alt=media\&token=d79c43f9-2498-4760-8172-4b1365ce02eb) button. Available in edit mode. Disabled if the step form is invalid.
* **Delete step** <img src="https://2962383972-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FoqUiFHjwtCCGSaEDqbXb%2Fuploads%2FZqACiL72RPLSdSyMBCqW%2Fimage.png?alt=media&amp;token=44ccbdab-c310-4c64-8c3f-90c5385ada90" alt="" data-size="line"> button. The first step can’t be deleted.
* **Edit step** <img src="https://2962383972-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FoqUiFHjwtCCGSaEDqbXb%2Fuploads%2FWCjPrmyEEYuxmRlJ2Bvp%2Fimage.png?alt=media&amp;token=d1872792-438b-4042-8c16-9650e26616f7" alt="" data-size="line"> button. Switches the step to edit mode.

5. Action buttons in the scenario form:

* **Delete scenario** <img src="https://2962383972-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FoqUiFHjwtCCGSaEDqbXb%2Fuploads%2Fcxpwahxolr7rmOIM1n9S%2Fimage.png?alt=media&amp;token=3b891ebe-c481-4071-9751-61698a86797f" alt="" data-size="line"> button
* **Clone scenario** <img src="https://2962383972-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FoqUiFHjwtCCGSaEDqbXb%2Fuploads%2FYdlFet1nrqyJccOOSzVd%2Fimage.png?alt=media&amp;token=e80e11b4-c15b-4b3e-b100-edfd431d85d1" alt="" data-size="line"> button
* **Save scenario** <img src="https://2962383972-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FoqUiFHjwtCCGSaEDqbXb%2Fuploads%2FaYWutfqz8MF8cHr07T25%2Fimage.png?alt=media&amp;token=ceef3230-4e24-44f4-9d6c-63b120a8f174" alt="" data-size="line"> button

### How to move a scenario to a folder

1. Open **Scenarios**.
2. Click the **Scenario menu** button next to the required scenario.
3. Select **Move**.
4. Select the destination folder.
5. Click **Move**.

After the scenario is moved, it no longer appears on the main scenarios screen. Open the selected folder to find and run it.

### How to add a scenario to Favorites

Click the **Favorite** icon on the required scenario. The scenario appears in the **Favorites** category.

To remove the scenario from **Favorites**, click the icon again.

### How to edit a scenario

1. Open the scenario list <img src="https://2962383972-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FoqUiFHjwtCCGSaEDqbXb%2Fuploads%2Fuu78vWgUoerXEvEamIkQ%2Fimage.png?alt=media&amp;token=28ba4395-1512-4ce1-b098-8503119b0943" alt="" data-size="line">.
2. Click the **Scenario menu** <img src="https://2962383972-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FoqUiFHjwtCCGSaEDqbXb%2Fuploads%2FtmZ9Fx2kTrJMk3Tmratw%2Fimage.png?alt=media&amp;token=5fa39b61-3db9-4f37-8e13-50c516ee967d" alt="" data-size="line"> button.
3. Select the **Edit** option from the list.
4. Make your changes and save the scenario.

#### How to edit a scenario step

1. Click the **Edit step** <img src="https://2962383972-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FoqUiFHjwtCCGSaEDqbXb%2Fuploads%2FWCjPrmyEEYuxmRlJ2Bvp%2Fimage.png?alt=media&amp;token=d1872792-438b-4042-8c16-9650e26616f7" alt="" data-size="line"> button on the step you want to edit.
2. Make your changes.
3. Click the **Save step** ![](https://2962383972-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FoqUiFHjwtCCGSaEDqbXb%2Fuploads%2FkMgjQeGRIlInIRX2zOUc%2Fimage.png?alt=media\&token=d79c43f9-2498-4760-8172-4b1365ce02eb) button in the upper-right corner of the step.
4. Click the **Save scenario** <img src="https://2962383972-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FoqUiFHjwtCCGSaEDqbXb%2Fuploads%2FaYWutfqz8MF8cHr07T25%2Fimage.png?alt=media&amp;token=ceef3230-4e24-44f4-9d6c-63b120a8f174" alt="" data-size="line"> button.

### How to clone a scenario

1. Open the scenario list <img src="https://2962383972-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FoqUiFHjwtCCGSaEDqbXb%2Fuploads%2Fuu78vWgUoerXEvEamIkQ%2Fimage.png?alt=media&amp;token=28ba4395-1512-4ce1-b098-8503119b0943" alt="" data-size="line">.
2. Click the **Scenario menu** <img src="https://2962383972-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FoqUiFHjwtCCGSaEDqbXb%2Fuploads%2FtmZ9Fx2kTrJMk3Tmratw%2Fimage.png?alt=media&amp;token=5fa39b61-3db9-4f37-8e13-50c516ee967d" alt="" data-size="line"> button.
3. Select the **Clone** option from the list.

{% hint style="info" %}
When a scenario is cloned, you receive a notification. The cloned scenario appears in the list.
{% endhint %}

You can also clone a scenario using the <img src="https://2962383972-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FoqUiFHjwtCCGSaEDqbXb%2Fuploads%2FYdlFet1nrqyJccOOSzVd%2Fimage.png?alt=media&amp;token=e80e11b4-c15b-4b3e-b100-edfd431d85d1" alt="" data-size="line"> button, inside the editing form of a specific scenario.

### How to delete a scenario

1. Open the scenario list <img src="https://2962383972-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FoqUiFHjwtCCGSaEDqbXb%2Fuploads%2Fuu78vWgUoerXEvEamIkQ%2Fimage.png?alt=media&amp;token=28ba4395-1512-4ce1-b098-8503119b0943" alt="" data-size="line">.
2. Click the **Scenario menu** <img src="https://2962383972-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FoqUiFHjwtCCGSaEDqbXb%2Fuploads%2FtmZ9Fx2kTrJMk3Tmratw%2Fimage.png?alt=media&amp;token=5fa39b61-3db9-4f37-8e13-50c516ee967d" alt="" data-size="line"> button.
3. Select the **Delete** option from the list.

{% hint style="info" %}
When a scenario is deleted, you receive a notification. The scenario disappears from the list.
{% endhint %}

You can also delete a scenario using the <img src="https://2962383972-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FoqUiFHjwtCCGSaEDqbXb%2Fuploads%2Fcxpwahxolr7rmOIM1n9S%2Fimage.png?alt=media&amp;token=3b891ebe-c481-4071-9751-61698a86797f" alt="" data-size="line"> button inside the editing form of a specific scenario.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://support.docstudio.com/user/scenarios/managing-scenarios/how-to-manage-a-scenario.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
