> For the complete documentation index, see [llms.txt](https://help.besmart.software/t4i/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/t4i/commands-overview/be.smart-t4i/edit-settings/auto-iproperties/automatic-update-of-iproperties.md).
# Automatic update of iProperties
## Workflow overview
On tabs File, Physical, Drawing, and Sheet metal, select the desired iProperties that should be automatically updated in a document.
{% hint style="warning" %}
If an iProperty is missing in a *Custom iProperty* section of the document, it is necessary to check the option *Create property if needed (or just update existing)* in the bottom left corner of the settings window).
{% endhint %}
{% hint style="info" %}
Only document-relevant iProperties will be created/updated in the document. It means that e.g. sheet metal properties will not be created/updated in the assembly file.
{% endhint %}
The iProperties will be automatically created after saving the document.
### Workflow example
Given the specific settings for the assembly file depicted in the images above, four iProperties were automatically added to the document: *Filename*, *LastSaveDate*, *LastSavedBy*, and *Mass*.
IProperties added to the assembly file
#### Workflow showcase
Setting up of automatic iProperties for the assembly file
---
# 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://help.besmart.software/t4i/commands-overview/be.smart-t4i/edit-settings/auto-iproperties/automatic-update-of-iproperties.md?ask=&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.
