> For the complete documentation index, see [llms.txt](https://knowledgebase.autorabit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledgebase.autorabit.com/product-guides/arm/arm-features/environment-provisioning/unsupported-metadata-templates/account-teams/sortalphabetically.md).

# SortAlphabetically

The **SortAlphabetically** template automatically reorders all picklist values alphabetically within Salesforce metadata configuration.

## Steps to Create the SortAlphabetically Template

1. Log in to your AutoRABIT account.
2. Navigate to the **Env. Pro.** module.
3. Click **Create New Template**.
4. Select the **Create Unsupported Metadata Template** tab.
5. Provide a **template name** and a **short description**.
6. Select the **SortAlphabetically** checkbox under **Account Teams**.
7. Click **Add**.
8. On the next screen:
   * A **Test Case Name** will be auto-generated by default.
   * Click **Add** to define your custom test data.
   * Provide a name for the test case.
   * Select the **Sort Alphabetically** checkbox to enable alphabetical sorting.
   * Click **Save** to confirm the configuration.
9. Click **Save** again to store the template.
10. You will be redirected to the **Environment Provisioning History** screen.
11. Click **Run** to execute the template on your target org.
12. Choose the **destination org** from the dropdown and provide **email address(es)** for notifications.
13. In **Post Deployment Steps**, select the test cases created.
14. Visit the **View History** page to access a detailed summary report of the deployment.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://knowledgebase.autorabit.com/product-guides/arm/arm-features/environment-provisioning/unsupported-metadata-templates/account-teams/sortalphabetically.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.