> For the complete documentation index, see [llms.txt](https://docs.avoautomation.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.avoautomation.com/avo-assure/create-and-execute-tests-with-design-studio/optimizer-beta/prompts/working-with-verified-prompts/verified-prompts-and-available-options.md).

# Verified Prompts and Available Options

This article describes how to run the verified prompts and manage their results. The following actions are available based on the selected prompt: 

* Replacing Static Waits
* Reassigning Artifacts
* Deleting Identified Items
* Updating Artifact Names
* Removing Duplicate Test Cases
* Running Prompts

## Replacing Static Waits

The Replace selected static waits option is available for the Contains Static Waits prompt. It replaces the static waits identified by the prompt with dynamic waits that wait for the required element to become visible. The updated wait is displayed in the test case where the element is used.

{% hint style="info" %}
**Note**: The **Contains Static Waits** verified prompt applies only to Web application types.
{% endhint %}

To replace all static waits, perform the following actions:

1. On the **Home** page, under **Projects**, select the required project.
2. Select **Design Studio** > **Optimizer**.
3. Select the **Contains Static Waits** prompt. The prompt result page opens.
4. Scroll to the result table and select the check box next to the items you want to replace.
5. Select **Replace selected static waits**. The **Replace selected static wait** confirmation dialog opens.

{% hint style="info" %}
**Note**: Select **Replace all static waits** to change all static waits at a time.
{% endhint %}

6. In the confirmation dialog, select **Replace selected static wait**. The applicable static waits are replaced in the Test Case.

![image](https://2174257472-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fk8QZzXZMIJSStKAzDSTu%2Fuploads%2FpGpMgCJ05VEIk03U5nBp%2Fimage?alt=media\&token=a9808343-e7bf-4d47-8ae1-380a5c544ee2)

## Reassigning Artifacts

The Bulk Reassign option is available for the Orphaned Artifacts prompt. It allows you to assign multiple artifacts without an active owner to a selected user at the same time. This helps you manage artifacts that need to be assigned to a different user.

To reassign the multiple artifacts, perform the following actions:

1. On the **Home** page, under **Projects**, select the required project.
2. Select **Design Studio** > **Optimizer**.
3. Select the **Orphaned artifacts** prompt. The prompt result page opens.
4. Scroll to the result table and select the check box next to the findings you want to reassign.
5. Select **Bulk Reassign**. The **Assign Artifact** dialog opens.
6. From **Assign To** drop drown, select the required user.
7. Select **Assign** to allocate the artifact to the user. The selected findings are assigned to the selected user.

![image](https://2174257472-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fk8QZzXZMIJSStKAzDSTu%2Fuploads%2FOJ2BmdSdSTDh26ADBtc7%2Fimage?alt=media\&token=ddbbca99-8e22-4fd2-857e-fe9b0e71b43b)

## Deleting Identified Items

The Delete selected option is available for the Empty Artifacts, Unexecuted Test Cases, Stalled Artifacts, and Project-wide Reference Gaps prompts. It allows you to delete selected items identified by the prompt. 

To delete selected findings, perform the following actions:

1. On the **Home** page, under **Projects**, select the required project.
2. Select **Design Studio** > **Optimizer**.
3. Select the required prompt (For example, Empty Artifacts). The prompt result page opens.
4. Scroll to the result table and select the check box next to the findings you want to delete.
5. Select **Delete selected**. The **Delete selected** confirmation dialog opens.
6. Select **Delete**. The selected item is removed from the list.

{% hint style="info" %}
**Note**: 

* Select **Delete all** to remove all findings at a time.
* Deletion is permanent. Optimizer does not restore deleted items. You must review the items before confirming the deletion.
  {% endhint %}

![image](https://2174257472-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fk8QZzXZMIJSStKAzDSTu%2Fuploads%2FsfW0IUn9o9unzl73M9er%2Fimage?alt=media\&token=420a7b0c-38a2-43da-9f07-33ebdf5181b5)

## Updating Artifact Names

The Suggest and rename option is available for the Non-compliant Names prompt. It allows you to review and update the names of selected project artifacts based on the suggested names. You can also add text before or after the suggested names.

{% hint style="info" %}
**Note**: The steps are the same for other artifacts, such as **Test Case** and **Execution Lists**.
{% endhint %}

To update the name of artifacts, perform the following actions:

1. On the **Home** page, under **Projects**, select the required project.
2. Select **Design Studio** > **Optimizer**.
3. Select the **Non-compliant names** prompt. The prompt result page opens.
4. Scroll to the result table and select the check box next to the findings you want to rename.
5. Select **Suggest and rename**. The **Rename element repositories** dialog opens.
6. Review the suggested names in the table.
   * **Artifact Name**: Displays the current name of the Element Repository.
   * **Suggested name**: Displays the suggested name for the Element Repository.
   * **Invalid reason**: Displays why the current name does not follow the recommended naming convention.
   * **Project Name**: Displays the project associated with the Element Repository.
   * **Assigned To**: Displays the user assigned to the Element Repository.
   * **Status**: Displays the current status of the Element Repository.
7. Select **Add text** to add text to the suggested names.
8. Enter the text you want to add.
9. Select **Before** or **After** to add the text before or after the suggested name.
10. Review the updated names in the **Suggested name** column.
11. Select **Confirm** to apply the new names. The selected Element Repositories are renamed with the updated names.

{% hint style="info" %}
**Note**:

* The dialog box displays the number of selected Element Repositories at the bottom of the table.
* Review the **Suggested name** and **Invalid reason** columns before confirming the new names.
  {% endhint %}

![](https://2174257472-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fk8QZzXZMIJSStKAzDSTu%2Fuploads%2FhQLXfoC42Uic9v28jqfX%2Funknown.png?alt=media\&token=73dd34c4-62e1-4ff8-94a6-553ff029d627)

## Removing Duplicate Test Cases

The Remove test case from execution list option is available for the Duplicated execution entries prompt. It allows you to remove duplicate test case entries from the same Execution List. This helps remove redundant test case executions without affecting test coverage.

To remove a duplicate test case from an Execution List, perform the following actions:

1. On the **Home** page, under **Projects**, select the required project.
2. Select **Design Studio** > **Optimizer**.
3. Select the **Duplicated execution entries** prompt. The prompt result page opens.
4. Scroll to the result table and select the check box next to the duplicate test case entries you want to remove.
5. Select **Remove test case from execution list**. The confirmation dialog opens.
6. In the confirmation dialog, select **Remove test case from execution list**. The selected duplicate test case entries are removed from the **Execution List**.

![image](https://2174257472-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fk8QZzXZMIJSStKAzDSTu%2Fuploads%2FNC2S6aTxHIvwntBkye6z%2Fimage?alt=media\&token=e455bb80-2cf9-4fcb-82b8-daabcf97fd09)

## Running Prompts

The Run option allows you to run any prompt and update its results based on the latest project data.

To run a prompt, perform the following actions:

1. On the **Home** page, under **Projects**, select the required project.
2. Select **Design Studio** > **Optimizer**.
3. Select the required prompt. The prompt result page opens.
4. Select **Run** to execute the prompt.
5. After the prompt execution is complete, review the changes in the findings.

{% hint style="info" %}
**Note**:

* You can also run a prompt from the **Optimizer** page by selecting the prompt and **Run Selected**.
* Select **Run All** to run all prompts under a category.
* If the prompt is not run in the last 24 hours, run it again before performing any action.
  {% endhint %}

![image](https://2174257472-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fk8QZzXZMIJSStKAzDSTu%2Fuploads%2FcgE50kqe7kP5v24EmqGh%2Fimage?alt=media\&token=bee61279-85ca-4b51-95a9-2918bf4a917b)


---

# 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://docs.avoautomation.com/avo-assure/create-and-execute-tests-with-design-studio/optimizer-beta/prompts/working-with-verified-prompts/verified-prompts-and-available-options.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.