Upload Documents from a Workflow Form

Before you start

• Decide which file field, if any, is the workflow's Main document.
• Use a stable variable name that downstream nodes can reference.
• Prepare a non-sensitive test file within the current upload limits.
• For a Public form, confirm that the file type is allowed by the stricter public-form policy.

What happens to an uploaded file

A native RAPTIX workflow form can collect files from a Manual Start field. RAPTIX validates and persists accepted attachments with the intended workflow context before it requests the workflow engine to start the run. The form shows success only after the engine accepts that run.

The saved document is associated with:

• the workflow instance;
• the form field name;
• the entity identifier;
• the Applications workspace, application, and page scope when available; and
• the submitting member or public-form context.

If the form has no usable Entity field, RAPTIX generates a stable entity identifier for the run so the document is not left ungrouped.

Add a file field to a form

1. Open the workflow in Flow Builder.
2. Open its Start node and select Trigger Manually.
3. Under Manual form fields, select Add field.
4. Enter a stable variable name and a user-facing label.
5. Set Field type to File upload.
6. Keep Show in form enabled.
7. Enable Required if the workflow must not start without the file.
8. Optionally enable Main document for the primary file used by the process.
9. Enable Expose as app, choose Private or Public access, and select Save Start Properties.

The form is available at the generated tenant-relative /f/:token link and appears under Runnable workflows in its Applications scope.

A Python Script node can read a visible file field through input_files["fieldName"]. Other node types use their own workflow-data mapping. For example, configure an Email node's attachment field with the matching workflow input key; do not assume that every node exposes a global input_files namespace.

Submit a file

1. Open the runnable form from Applications or its share link.
2. Select a file for each required file field.
3. Complete the remaining required fields and consent option, if present.
4. For a Public form, complete the verification challenge.
5. Select Submit once and wait for the success message or configured redirect.

A successful response means the workflow engine accepted the run. Open the workflow detail and Documents views to verify the stored attachment.

Upload limits

The current native form runner enforces these limits:

• 8 MB per file;
• 20 MB total file data per submission; and
• no more than 5 files across the submission.

Public forms additionally restrict file types. Common PDF, Office document, image, plain-text, and CSV formats are accepted. Archives, executables, HTML, SVG, and other unsafe carriers are rejected. A file extension alone does not override server validation.

Main document and entity field

Only one visible File upload field should be marked Main document. Use that flag for the document that represents the process record, such as the invoice being approved.

An Entity field must be a scalar field such as text, number, date, or a single selection. File and checkbox-group fields cannot be entity fields. RAPTIX uses the entity value to group documents and workflow activity around the same business record.

Troubleshooting

The form rejects the file before submission

Check its size. For Public forms, also confirm that its type is supported and that the actual file content matches the declared type.

The workflow starts but the file is not where expected

Confirm that the file field is visible, has a stable variable name, and belongs to the published Start-node form. Check the workflow instance and entity identifier when searching Documents.

The form no longer appears in Applications

Confirm that Expose as app is enabled, the share link has not been revoked, and the workflow is active.

This is an App Builder page, not a native form

App Builder file widgets use the Enterprise connector deployment. Follow Connect an App Builder Page to a Workflow and redeploy after changing file widgets.