SAVES ANY FILE TO THE SERVER¶
Uploads and persists any file to the d3VIEW server as a named attachment, optionally tagging it and associating it with a project. Use this worker whenever a workflow needs to durably store a file artifact so it can be referenced or retrieved later by its attachment ID.
When to use¶
Tagged: attachment, file, persist, save, storage, upload, user.
Inputs¶
| Label | ID | Type | Default | Required | Description |
|---|---|---|---|---|---|
| Attachment To Save | attachment_file | file | — | ✓ | The file to be saved to the server; accepts any file type/format — this is the primary payload of the worker. |
| Name | name | text | — | ✓ | Human-readable name assigned to the stored attachment; used for display and lookup within the platform. |
| Tags | tags | text | — | Optional comma-separated labels to categorise the attachment for filtering and search; leave blank if no tagging is needed. | |
| Description | description | textarea | — | Optional free-text description of the attachment’s contents or purpose; leave blank if not required. | |
| Project ID | project_id | remote_lookup | — | Optional project to associate the attachment with, selected via remote lookup; defaults to null (no project association). |
Outputs¶
| Label | ID | Type | Description |
|---|---|---|---|
| Saved Attachment | attachment_id | integer | Integer primary key of the newly saved attachment record in the d3VIEW database; use this ID in downstream workers to reference or retrieve the file. |
Disciplines¶
- data.io.file
- platform.workflow
Auto-generated from platform schema. Worker id: attachment_save. Schema hash: 0ebc236bc77e. Hand-curated docs in workerexamples/ override this page when present.