Actions33
- Archiv Actions
- Dokument Actions
- Dokument herunterladen
- Dokument mit Klassifikation herunterladen
- Dokumentversion herunterladen
- Dokumentinformationen abrufen
- Dokument hochladen
- Dokument mit PDF hochladen
- PDF in Inbox hochladen
- Datei hochladen
- Templates für Datei abrufen
- Duplizierungscheck durchführen
- Version mit PDF hinzufügen
- Version hinzufügen
- Klassifikation mit Template-Erkennung abrufen
- Dokumenttyp Actions
- Klassifikation Actions
- Suche Actions
- Ordner Actions
- Lizenz Actions
Klassifikation → Inbox-Dokument klassifizieren
AI-generatedOverview
This node operation classifies an inbox document within the ecoDMS system. It is useful for organizing and categorizing documents that have been uploaded to the inbox, enabling better document management and retrieval. For example, users can classify a newly uploaded document by specifying its classification attributes, roles for editing and reading, and optionally update an existing classification by providing its classification ID.
Use Case Examples
- Classify a newly uploaded inbox document by providing its document ID, classification attributes, and roles.
- Update an existing classification of an inbox document by specifying the classification ID and new classification attributes.
Properties
| Name | Meaning |
|---|---|
| Inbox-Dokument-ID | The ID of the inbox document to classify, obtained from the uploadFileToInbox API. |
| Klassifikations-ID (clDocId) | Use -1 for a new classification. For updates, use the existing classification ID obtained from the getInboxClassifications API. |
| Klassifikationsattribute | The classification attributes in JSON format. Mandatory fields include docart, folder, and bemerkung. These attributes can be retrieved via the classifyAttributes API. |
| Bearbeitungsrollen (editRoles) | Comma-separated list of roles allowed to edit the document. Important: Roles here must not overlap with read roles. |
| Leserollen (readRoles) | Comma-separated list of roles allowed to only read the document. Important: Roles here must not overlap with edit roles. |
Output
JSON
clDocId- The classification document ID after classification.status- The status of the classification operation, indicating success or failure.
Dependencies
- Requires ecoDMS API credentials including server URL for authentication and access.
Troubleshooting
- Ensure the server URL is configured in the credentials; otherwise, the node will throw an error indicating the server URL is not configured.
- Verify that the classification attributes JSON includes all mandatory fields (docart, folder, bemerkung) to avoid classification errors.
- Avoid overlapping roles between editRoles and readRoles to prevent permission conflicts.