How do I search documents by their content, not just the file name?
Use a full-text search backend that indexes document text, including OCR output for scans. FormKiQ supports optional Typesense in Core and a commercial OpenSearch extension. Choose the documented search operations for that backend, then apply supported metadata constraints. Content indexing, metadata search, and filename browsing are different capabilities with different readiness and query behavior.
Choose and populate an index
Inventory file formats and document volume before selecting a backend. Digital text and scanned content need different extraction paths. Configure actions so text is available before indexing, and inspect failed or skipped processing rather than assuming every stored document is already indexed.
Use the backend-specific request shape from the search guide. Combining full-text and metadata constraints depends on the installed backend and query operation; do not translate a business filter directly into an invented API field.
Validate results and freshness
Test a phrase found only in file content. Then add an actual metadata constraint, such as document type, using a supported query. Check positive matches, near misses, and an ordinary user's access boundary.
Define acceptable indexing delay and monitor backlog, throttling, and failures. Include changes, deletion, and reindexing in the operating plan. Selecting OpenSearch also adds capacity and storage costs beyond the serverless document APIs.
Edition and configuration
Optional Typesense is supported in Core. Enhanced Full-Text Search is a selected Advanced/Enterprise extension using OpenSearch; OCR provider and processor entitlements are separate.