Overview

Requirements document uploads are limited by file size and MIME type to ensure parse performance and storage efficiency. Typical maximum is 10MB per file on project create or requirements update.

Who should read this

QA engineers, SREs, platform teams, and developers operating Zof Console and APIs.

When to use this workflow

Onboarding new team members to Zof terminology and workflows
Authoring internal runbooks aligned with Console labels
Designing CI/CD or webhook integrations against documented behavior

Step-by-step procedure

Prepare document

Export requirements as PDF or DOCX under size limit.

Remove embedded media if size exceeds threshold.

Upload in wizard

Projects → Create → Requirements step → drag and drop or browse.

Confirm extraction preview before continuing.

Key concepts

Supported types: PDF, DOC, DOCX, PNG, JPG as enforced at upload time.
Size limit: 10MB default; split large documents or upload summaries if rejected.

Best practices

Validate changes in staging before applying release gates to production.
Include run IDs and timestamps when escalating issues to support or auditors.
Align internal runbook terminology with Zof Console UI labels for clarity.

Common issues

Upload rejected: Check file size and extension; convert unsupported formats to PDF.
Slow parse: Large image-heavy PDFs may delay requirement extraction; prefer text-native documents.