> For the complete documentation index, see [llms.txt](https://help.besmart.software/older-26.0.0/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.besmart.software/older-26.0.0/commands-overview/holixa-t4i/advanced-settings/validate-document-on-save.md).

# Validate Document On Save

`Holixa T4I -> Holixa T4I -> Advanced settings -> Auto iProperties -> Validate Document On Save`

On invoking the Save command, a check can be performed whether the document being saved conforms to preset rules. The activation of the individual validation checks can be set in Advanced settings.

<figure><img src="/files/hNiyebXwSJzmPMj8U3Sb" alt=""><figcaption><p>On Save document validation settings</p></figcaption></figure>

If at least one of the validation checks fails, the save process is terminated, and the issue description is listed in a dialog box.

<figure><img src="/files/W7cFfUL0PjhcMpUbGEMJ" alt=""><figcaption><p>Example of the On Save validation error message </p></figcaption></figure>

## Virtual Components in Assembly

The assembly must not contain virtual components. If they are present, the save command is canceled.

<figure><img src="/files/1UAwxfJZ8Ha2VDctarjn" alt=""><figcaption><p>Virtual component in the assembly</p></figcaption></figure>

## Invalid Units of Measurement

If there is a problem with units in BOM, the assembly cannot be saved.

## Whitespace Before or After the Part Number

The iProperty *Part number* must not start or end with spaces, otherwise, the document cannot be saved. This rule applies not only to assemblies but also to parts.

<figure><img src="/files/hS7t4DpHT0bTuwOtIKMK" alt=""><figcaption><p>White space before the part number</p></figcaption></figure>


---

# 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://help.besmart.software/older-26.0.0/commands-overview/holixa-t4i/advanced-settings/validate-document-on-save.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.