ecoDMS icon

ecoDMS

ecoDMS-Integration für n8n

Klassifikation → Dokument-Klassifikation aktualisieren

AI-generated

Overview

This node operation updates the classification of a document in the ecoDMS system. It is useful for scenarios where document metadata or classification attributes need to be modified, such as updating document type, revision, status, or folder placement. For example, after reviewing a document, a user might update its classification attributes to reflect changes in its status or categorization.

Use Case Examples

  1. Updating the classification attributes of a document after a revision.
  2. Changing the folder or status of a document based on new information.

Properties

Name Meaning
Dokument-ID The ID of the document whose classification is to be updated. This ID can be obtained via the 'Retrieve Document Information' operation.
Klassifikations-ID (clDocId) The classification ID of the document, also retrievable via the 'Retrieve Document Information' operation.
Klassifikationsattribute The classification attributes in JSON format. Important: The 'revision' must match the current value from documentInfo. Mandatory fields include docart, folder, status, and bemerkung (remark).
Bearbeitungsrollen (editRoles) Comma-separated list of roles allowed to EDIT the document (e.g., 'r_ecodms,Elite'). Important: This list must not contain any roles that are also in the readRoles list.
Leserollen (readRoles) Comma-separated list of roles allowed to ONLY READ the document (e.g., 'ecoSIMSUSER,Gast'). Important: This list must not contain any roles that are also in the editRoles list.

Output

JSON

  • success - Indicates whether the classification update was successful.
  • updatedClassification - The updated classification details of the document after the operation.

Dependencies

  • Requires ecoDMS API credentials including server URL and authentication token.

Troubleshooting

  • Ensure the server URL is configured in the credentials; otherwise, the node will throw an error indicating the server URL is missing.
  • Verify that the 'revision' field in the classification attributes matches the current revision of the document to avoid update conflicts.
  • Make sure that roles listed in 'editRoles' and 'readRoles' do not overlap, as this will cause permission conflicts.

Discussion