> For the complete documentation index, see [llms.txt](https://docs.docbits.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.docbits.com/administration-and-setup/settings/global-settings/document-types/regex.md).

# Regex

Regular expressions describe text patterns for values such as invoice numbers, dates and amounts. Patterns and document origins must match the relevant document layout.

## Management availability

The former direct Regex link on the document-type card is not available in the current interface. Check with your administrator which configuration path is supported in your version before changing patterns.

## Edit and test a pattern

1. Record the existing pattern and the expected matches.
2. Prepare representative input text and examples that should not match.
3. Change the pattern and compare its actual matches with the expected values.
4. Apply the change to the intended configuration only after testing it successfully.

See [Editing and saving Regex patterns](https://docs.docbits.com/administration-and-setup/settings/global-settings/document-types/regex/editing-and-saving-regex-patterns.md).


---

# 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.docbits.com/administration-and-setup/settings/global-settings/document-types/regex.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.
