> For the complete documentation index, see [llms.txt](https://docs.besmart.software/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.besmart.software/design-data-management-and-exchange/classification-system/value-pattern.md).
# Value Pattern
There are four types of scripts – {0}, {1}, {2} and {3} – to help you create combined values. You can use scripts within any word combinations. Simply write {0} and a tool will add the index value of only the class selected in the tree to your chosen property value.
**{0}** – adds the index value of the class selected in the tree.
**{1}** – adds the class name selected in the tree.
**{2}** – adds a number to the last value. This lets you auto-number elements by increasing the previous number by +1.
**{3}** – adds the current date and time.
**Some examples of how it works:**
Script: **{0} – Hello world**
Result: **23-17 13 15 23 – Hello world**
Script: **{0}-{1}**
Result: **23-17 13 15 23-Wood Casement Windows**
Script: **{1}**
Result: **Wood Casement Windows**
Script: **%%%{0}-{1}**
Result: **%%%23-17 13 15 23-Wood Casement**
**Windows**
Script: **Hello{0}**
Result: **Hello23-17 13 15 23**
Script: **Hello{0}world**
Result: **Hello23-17 13 15 23world**
Script: **Hello {0} world**
Result: **Hello 23-17 13 15 23 world**
To fix the number of digits in the numbering script {2}, specify the number of digits with a :, the letter D and the number.
Here is an example of auto-numbering with three digits.
Script: **{2:D3}**
Result: **001, 002, … , 010, 011, … , 100, 101, …**
And here is an example of a class title and auto-numbering with two digits.
Script: **{1}-{2:D2}**
Result: **Wood Casement Windows**-01, **Wood Casement Windows**-02, … , **Wood Casement Windows**-10, **Wood**
**Casement Windows**-11, … , **Wood Casement Windows**-99, **Wood Casement Windows**-100, **Wood Casement Windows**-
101, …
---
# 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://docs.besmart.software/design-data-management-and-exchange/classification-system/value-pattern.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.
