> 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/required-field-validation-in-ez-commit-new-ui.md).

# Required Field Validation in EZ-Commit (New UI)

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

### Overview

AutoRABIT ARM has enhanced the **Create EZ-Commit workflow** with improved required-field validation, making it easier to identify and correct missing information before proceeding.

With this enhancement, the **Next** and **Submit** buttons remain enabled, and ARM displays clear inline validation messages when users attempt to proceed without completing required fields.

### What's New?

#### 1. Improved Required Field Validation

* The **Next** and **Submit** buttons remain enabled even when required fields are incomplete.
* Clicking these buttons highlights all missing required fields and displays error messages directly below them.
* ARM automatically scrolls to and focuses on the first missing required field.
* Validation messages disappear as users provide valid information.
* Users can proceed to the next step only after completing the required fields.

#### 2. Validation Across EZ-Commit Steps

<figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2F5wFOUcAskl5hpS1nNDNq%2Fimage.png?alt=media&amp;token=14088b02-3df4-4775-8f70-28d68693eac2" alt=""><figcaption></figcaption></figure>

**Step 1 – New Commit**

ARM validates required fields such as:

* Salesforce Org and Salesforce Org Author
* Repository and Branch
* Components and Manageable States
* Additional fields such as Package Directory, Package Manifest, Commit Template, Labels, and ALM details when applicable

**Step 2 – Metadata Selection**

If users click **Next** without selecting any metadata, ARM displays a validation message and automatically scrolls to the metadata selection area.

**Step 4 – Submit for Validation / Commit / PR**

Clicking **Submit** validates the required fields based on the selected operation, including Commit Comments, Commit Labels, Reviewer Emails, Validation Options, and other applicable settings.

#### 3. Improved Navigation Feedback

When users attempt to access a step that is unavailable because required information is missing, a tooltip explains what needs to be completed before proceeding.

### How It Works

1. Navigate to **Version Control > EZ-Commit** in the New UI.
2. Start a new EZ-Commit operation.
3. Click **Next** to proceed.
4. If required information is missing, ARM highlights the fields and displays inline error messages.
5. Complete the highlighted fields. The corresponding validation messages disappear automatically.
6. Continue through the workflow and click **Submit** to complete the operation.

### Important Notes

* Validation messages appear directly below the relevant fields instead of displaying a general notification.
* ARM automatically scrolls to the first missing required field, including fields outside the visible screen area.
* Required fields may vary depending on the selected component type, fetch method, and operation.
* Existing validation behavior for fields that already validate during user interaction remains unchanged.
* The existing behavior for large metadata selections (more than 50 files) in the optional Review Artifact step remains unchanged.
* This enhancement is available only in the **ARM New UI**.

### Benefits

* Quickly identifies missing required information.
* Reduces confusion caused by disabled navigation buttons.
* Simplifies navigation through multi-step EZ-Commit workflows.
* Provides a smoother and more intuitive commit experience.


---

# 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/required-field-validation-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.
