> 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/fields/best-practices-3.md). # Best practices ## Here are best practices for field configuration in a document processing system, emphasizing the importance of understanding the document workflow and data requirements. ### **Understanding the document workflow:** * Analyze your document workflow thoroughly to identify the different phases and steps a document goes through, from capture to processing to storage or release. * Identify the specific data that needs to be captured, reviewed, processed, or extracted at each step of the workflow. ### **Identify key data points:** * Determine the key data that is critical to your business process or analysis. * Prioritize fields according to their importance to the business process or analysis to ensure they are captured and processed correctly. ### **Match fields to data requirements:** * Match field properties to specific data requirements, including their type (text, date, numeric, etc.), validation rules, and any required properties such as required or read-only. * Also consider security requirements, privacy regulations, and legal requirements when configuring field properties. ### **Consider flexibility and extensibility:** * Design the fields to be flexible and extensible to accommodate future customizations or changes in document workflow or data requirements. * Make sure the configuration of the fields allows new data points or changed requirements to be easily and efficiently incorporated. ### **Test and validate:** * Perform extensive testing to ensure that the configured fields work correctly and produce the expected results. * Validate the field configuration by processing a large number of documents and verifying that the data captured meets the requirements. By understanding the document workflow and data requirements and applying best practices in field configuration, you can ensure that your document processing system functions efficiently and accurately. This will help improve the quality of your data, optimize workflow, and increase the overall performance of your business. --- # 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://docs.docbits.com/administration-and-setup/settings/global-settings/document-types/fields/best-practices-3.md?ask=&goal= ``` `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.