> For the complete documentation index, see [llms.txt](https://help.novacuraflow.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.novacuraflow.com/clients/mobile-clients/scanning.md). # Scanning See supported scanning options [here](/system-requirements.md#clients). The Flow clients support scanning into the text input, the numeric input, and in the grid, the text and numeric input in the detailed view if the fields are editable. Scanning is also supported to filter in list selection, and list multi-selection. A barcode icon indicates where scanning is available. Click on the barcode icon to scan manually. When using a zebra scanner, or similar, the focus is automatically set in control so the user does not have to click on the screen to scan. To connect a Zebra Bluetooth scanner see [Zebra Scanners](/clients/mobile-clients.md#external-scanners). --- # 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.novacuraflow.com/clients/mobile-clients/scanning.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.