> 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-1/arm-features/version-control/ez-commits/automatic-field-population-in-ez-commit-new-ui.md).

# Automatic Field Population in EZ-Commit (New UI)

**Product:** AutoRABIT ARM\
**Module:** Version Control – EZ-Commit\
**Availability:** New UI

### Overview

AutoRABIT ARM has enhanced the **EZ-Commit workflow** to automatically populate known values and suggest relevant information, reducing repetitive manual entry and simplifying commit creation.

With this enhancement, ARM automatically fills certain fields based on the logged-in user, selected Salesforce org, and repository configuration.

### What's New?

#### 1. Automatically Populated Fields

ARM automatically populates the following fields when the required information is available:

* **Reviewer Email:** Defaults to the logged-in user's email address.
* **Salesforce Org Author:** Automatically selects the logged-in user's mapped Salesforce org account, when available.
* **Parent Branch:** Defaults to the repository's configured default branch when creating a new branch.
* **Credentials:** Automatically selects the available credential when the user has only one credential.

#### 2. Suggested Values

ARM also suggests meaningful values for the following fields:

* **Commit Label:** Suggested based on the selected Salesforce org, branch, and date.
* **Commit Comment:** Suggested based on the selected metadata components.
* **Branch Display Name:** Suggested based on the linked work item or the user's name and date.

Users can accept these suggestions or modify them according to their requirements.

#### 3. Salesforce Org User Population

The **Salesforce Org User** field under **My Profile > Org Registration** is automatically populated using the username configured under **Org Settings > Details > Username**.

### How It Works

1. Navigate to **Version Control > EZ-Commit** in the New UI.
2. Start a new EZ-Commit operation and select the required Salesforce org.

<figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2FhphGWBt1O7i7G9ii3doc%2Fimage.png?alt=media&amp;token=d85265bd-6fbd-4f2a-a6fa-2902dd673840" alt=""><figcaption></figcaption></figure>

3. Review the automatically populated author information and other available values.
4. When creating a new branch, review the default Parent Branch, Credentials, and suggested Branch Display Name.

<figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2F7ttXwNjEo0TujfF00pEU%2Fimage.png?alt=media&amp;token=c3dcced4-9850-4c01-9241-f892a7570810" alt=""><figcaption></figcaption></figure>

5. Review the suggested Commit Label, Commit Comment, and Reviewer Email.

<figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2FSAeoRflDrVAKNsV4VuMH%2FScreenshot%202026-11-06%20at%2023.02.13.png?alt=media&amp;token=90b26687-da3f-4640-b21f-6b8cfd11a540" alt=""><figcaption></figcaption></figure>

6. Modify any values if needed and continue with the existing EZ-Commit workflow.

### Important Notes

* All automatically populated and suggested values remain **editable**.
* Fields are populated only when ARM can identify the appropriate information. Otherwise, they remain empty for manual selection.
* Existing saved configurations and previously created commits are not affected.
* Previously selected values for Salesforce org, repository, branch, components, and checkbox options are not automatically remembered.
* This enhancement is available in the **New UI**.

### Benefits

* Reduces repetitive manual entry during commit creation.
* Speeds up branch creation and commit configuration.
* Encourages consistent and meaningful commit labels and comments.
* Allows users to retain full control over automatically populated values.


---

# 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://knowledgebase.autorabit.com/product-guides/arm-1/arm-features/version-control/ez-commits/automatic-field-population-in-ez-commit-new-ui.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.
