Actions26
- Archiv Actions
- Dokument Actions
- Dokument herunterladen
- Dokument mit Klassifikation herunterladen
- Dokumentversion herunterladen
- Dokumentinformationen abrufen
- Dokument hochladen
- Dokument mit PDF 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
Overview
This node integrates with the ecoDMS document management system to add a new version of an existing document, including uploading both the original file and its PDF version. It is useful in scenarios where documents are regularly updated or revised, and each revision needs to be archived as a separate version within ecoDMS. For example, legal teams updating contracts or project managers revising specifications can use this node to maintain version history while ensuring that both the original and PDF formats are stored.
Properties
| Name | Meaning |
|---|---|
| Dokument-ID | The ID of the document to which a new version will be added. |
| Version fixieren | If enabled, no further versions can be added to this document after archiving (locks the version). |
| Originaldatei | The name of the binary property containing the original file to upload as the new version. |
| PDF-Datei | The name of the binary property containing the PDF file to upload alongside the original file. |
Output
The node outputs JSON data representing the result of adding the new document version. This typically includes metadata about the newly created version such as its ID, status, timestamps, and possibly links or references to the stored files. If the operation involves binary data (the original and PDF files), these are uploaded but not outputted by the node; only metadata about the operation is returned.
Dependencies
- Requires an active connection to an ecoDMS server.
- Needs credentials configured with the ecoDMS API URL and authentication token.
- The node expects binary input data for both the original file and its PDF version under specified property names.
- No additional external services are required beyond ecoDMS itself.
Troubleshooting
- Missing Server URL: If the server URL is not configured in the credentials, the node throws an error stating "Server-URL ist nicht konfiguriert. Bitte in den Anmeldedaten angeben." Ensure the ecoDMS API URL is correctly set in the credential configuration.
- Invalid Document ID: Providing a non-existent or incorrect document ID will likely cause the operation to fail. Verify the document ID before running the node.
- Binary Data Issues: If the specified binary properties for the original or PDF files do not exist or are empty, the node will fail to upload the files. Confirm that the input data contains the correct binary properties.
- Version Locking: Enabling the "Version fixieren" option prevents further versions from being added. Use this carefully to avoid locking documents prematurely.
- General Errors: Other errors during processing are wrapped and reported with a generic message "Fehler bei der Verarbeitung". Check the detailed error message for specifics.
Links and References
- ecoDMS Official Website
- ecoDMS Documentation
- n8n Documentation on Working with Binary Data