Input documents¶
An input document defines a file the case must provide: an attachment the person working the task uploads before continuing.
Fields¶
| Field | Rule |
|---|---|
| Title | Up to 200 characters; stops at the limit with Character limit reached |
| Description | Up to 500 characters; the field resizes when you drag its corner |
| Allowed types | The extensions the step accepts, for example only PDF |
| Maximum size | The size limit per file for the step |
| Versioning | Whether uploading a file with the same name creates a new version |
The title and description limits are enforced as you type, so a long title cannot be saved half-cut.
Attach it to a step¶
An input document does nothing until a task uses it:
- Open the task and choose Steps.
- Drag the input document from Available to Assigned.
- Order it relative to the forms in the same task.
At run time the step shows the documents already uploaded, then the upload controls, with the allowed types and maximum size visible above them.
What the person sees¶
- Attach documents opens the upload panel next to the uploaded list.
- Add files accepts several files at once, each with its own comment.
- Add folder takes a folder and its subfolders.
- Files outside the allowed types or above the size limit are marked and skipped, and the upload button counts only the valid ones.
The case side of this flow is described in Uploading documents.
Why the limits matter¶
The step validates before sending, but the server validates again. A file that passes the step and fails on the server stays in the list with the error so it can be retried; the other files of the same batch are not discarded.
Related¶
- Output documents — files the process generates.
- Task properties — assigning the document to a step.
- Uploading documents — the case experience.